administrative-divisons-db
administrative-divisons-db
Get all administrative divisions of a country.
No authentication required
Check the docs depth and real endpoint shape before assuming production fit.
Start by accessing the API endpoints without authentication. Refer to the official repository for usage details.
Uptime · 30-day window
GitHub activity
About this API
The administrative-divisions-db API provides comprehensive data on the administrative divisions within countries, such as provinces, states, cities, and counties. It is useful for developers who need structured geographic data for applications involving location selection, validation, or display.
Because it requires no authentication, it is easy to integrate into projects without managing API keys or tokens. The data is sourced from an open repository, making it transparent and accessible for various use cases.
This API is relevant for building user interfaces that require accurate administrative boundaries, such as forms, maps, or geographic information systems. Its focus on administrative divisions makes it a specialized tool for geocoding and location-based services.
What you can build
- 1Display hierarchical administrative divisions of a country
- 2Generate location-based dropdown menus
- 3Validate user input for administrative regions
- 4Build geographic data visualizations
Strengths & limitations
Strengths
- No authentication required
- Covers all administrative divisions
- Open source data
Example request
curl https://github.com/kamikazechaser/administrative-divisions-db/<endpoint>Getting started
Start by accessing the API endpoints without authentication. Refer to the official repository for usage details.
FAQ
Do I need an API key to use this API?+
No, this API does not require any authentication or API key.
What kind of data does the API return?+
It returns data about administrative divisions such as provinces, states, cities, and counties.
Can I use this API directly from a browser?+
Yes, since no authentication is required, it can be accessed directly from client-side code if CORS policies allow.
Is HTTPS required to access the API?+
While not explicitly stated, using HTTPS is recommended for security.
Technical details
- Auth type
- none
- Pricing
- free
- Protocols
- REST
- Response time
- 313 ms