
Learn how to access and use the Population Explorer API with Pro or Enterprise accounts, including setup, requests, responses, best practices, and related guides.

PopEx API Access & Usage Guide
Population Explorer’s API allows analysts and decision-makers to pull demographic data directly into their own workflows. Instead of working exclusively inside the web application, you can programmatically query population totals, density, and age–sex breakdowns for any polygon you define. Each paid account comes with an API token and a monthly allowance of calls, making it simple to test small-scale analyses or integrate population data into larger automated pipelines. With straightforward request and response formats, the API is designed to be accessible to both technical teams and business users working with spatial datasets.
Prerequisites
A paid PopEx account (Pro or Enterprise).
An API token, visible in:
- In-app → Person icon (upper left) → Account & Billing
- Marketing site → My Account → Account InfoAn API tool of your choice (curl, Postman, Python, R, etc.).
Familiarity with JSON input/output.
Features
Direct programmatic access to Population Explorer datasets (LandScan 2016–2023, WorldPop 2024+).
Returns population totals, age/sex breakdowns, and demographic metrics.
Supports polygon queries — send your own geometries.
Provides quota management: 100 free calls/month included in all paid accounts (Pro, Enterprise); more available via direct purchase.
Instructions
Step 1: Locate your API token
In-app path: Person icon → Account & Billing
Marketing site path: My Account → Account Info
Step 2: Structure your request
Send an HTTP POST request. Required headers:
Step 3: Provide a polygon
Include a type: Polygon payload with coordinates. Coordinates must be in GeoJSON format (longitude, latitude).
Example Request
Example Response
Verification
Ensure your token is accepted (401 Unauthorized = invalid token).
Check that the quota field in the response matches your remaining calls.
Validate that population_data.sum equals the total population for your polygon.
Common Errors
401 Unauthorized: Invalid or missing API token.
403 Forbidden: Token belongs to an unpaid account.
403 Starter Plan: Starter accounts cannot use the API (upgrade to Pro or Enterprise).
429 Too Many Requests: Monthly quota exceeded (100 free calls); contact PopEx to purchase more.
400 Bad Request: Malformed polygon JSON.
Best Practices
Keep polygons as simple as possible to avoid timeouts.
Cache results if running repeated queries on the same area.
Monitor quota usage via the quota field in responses.
Upgrade or purchase additional calls if you expect heavy API usage.
Need More Help?
If you run into issues, please contact us.
Explore our latest thinking on franchise territory design, retail site selection, and the population data that powers smarter location decisions.

Aug 7, 2026
Daytime Differential: What It Is, and Why Your Retail Site Selection Strategy Needs It
What is Daytime Differential? The ratio of ambient to residential population for a site, and why site selection needs both types of data to make informed decisions.

Aug 7, 2026
Daytime Population of Europe's Million-Plus Cities, Ranked (2026)
Daytime vs. residential population, ranked across Europe's 43 million-plus cities. Some nearly double during the day; others barely hold half.

Jul 27, 2026
UK Postcode Districts Ranked by Ambient Population: Growth Leaders and Decliners (2016–2024)
This report ranks UK postcode districts by ambient population using LandScan data covering 2016 to 2024. Ambient population measures where people actually concentrate throughout the day, across employment, commuting, retail, logistics, and commercial activity, rather than simply where they sleep at night.
