POI API for Germany – location data via REST, GraphQL & bulk feed
Programmatic, real-time access to gas stations, EV chargers, supermarkets and more. Geo-query, custom crawling and webhooks – for teams that integrate location data directly.
- REST & GraphQL
- Geo-query: bounding box & radius
- Webhooks on changes
- Enterprise SLA & custom crawling
What is a POI API?
A POI API is a programming interface that lets applications query location data for points of interest – such as gas stations, EV chargers or supermarkets – in real time, instead of loading it as a static file.
poidatabase serves this data through REST and GraphQL endpoints with geo-queries, webhooks and optional custom crawling. You integrate current, categorized POI data straight into your backend – with no crawling infrastructure of your own.
Three steps to production
From API key to integration – with no data pipeline of your own.
- 1
Pick an endpoint
Choose the POI category and define your geo-query – bounding box, radius or brand.
- 2
Integrate
REST or GraphQL, documented fields, webhooks for changes. Libraries for common stacks.
- 3
Scale
Bulk export for analytics, custom crawling for extra fields, enterprise SLA for production.
Endpoints
POI endpoints with real location counts
Each category is its own endpoint with Germany-wide coverage. The numbers show the approximate count of retrievable locations (as of June 2026).
- Live endpoint, geo-query, brand filterGas stations≈ 14.000
- Real-time query, power, operatorEV charging points≈ 150.000
- Store endpoint, chain, catchmentSupermarkets≈ 38.000
- Location endpoint, address, contactPharmacies≈ 17.000
- Dining endpoint, cuisine, geo-queryRestaurants≈ 70.000
- ATM endpoint, operator, geo-queryATMs≈ 51.000
Use cases
What teams use the POI API for
One endpoint, many backends – from the map app to the location engine.
Navigation & routing
Routing backends query destinations and charging points live – with current availability and opening hours.
Geomarketing platforms
SaaS tools embed store networks and catchment areas via API instead of maintaining data by hand.
Location engines
Expansion and analytics tools compute competitive density and potential from live data.
Insurance & risk
Risk models enrich addresses with nearby POIs – via geo-query in seconds.
Why poidatabase
One integrable data source instead of a home-built pipeline.
- REST and GraphQL endpoints with documented fields
- Geo-query by bounding box, radius and attributes
- Webhooks on opening, closure and change
- Custom crawling for additional, project-specific fields
- Public location data only, no personal information (GDPR-friendly)
- EU hosting (Frankfurt), enterprise SLA and transparent limits
Frequently asked questions about the POI API
Short answers first – details below.
Which interfaces does the POI API offer?
poidatabase provides REST and GraphQL endpoints, plus bulk export and webhooks. All return the same documented fields, so you are free to choose between access methods.
How current is the API data?
The data is maintained continuously and fully reconciled monthly. In between, webhooks notify you of changes to the inventory.
Is usage GDPR-compliant?
Yes. The API serves only public location data about facilities with no personal information, so it is not subject to the personal-data provisions of the GDPR.
What is custom crawling?
Custom crawling extends an endpoint with project-specific fields we collect for you – such as fuel types, services or brand attributes beyond the standard dataset.
Is there a free API trial?
Yes. You get a trial key with limited requests to check endpoints, fields and response times before going to production.
Request an API key or ask a question
Tell us which endpoints and query volume you need – we'll set up a trial access for you.