apihub places API

API ID 14930

Read-only HTTP API for Overture Maps places loaded into PostGIS. Search is a radius query around a WGS84 point. Results are ordered by distance ascending, then place id ascending. q is a

API Documentation

Endpoints

Request
Returns places inside `range_m` of (`lat`, `lon`), closest first. `total` is the full match count and ignores pagination. `items` contains at most one page. `next_cursor` is an opaque keyset cursor when another page exists, and `null` on the last page. Pass `next_cursor` back as `cursor` to resume after the last row of the previous page. The cursor encodes that row's distance and id. A cursor from a different search still parses, but the page boundary will not line up with the new filters. `limit` defaults to 20 and is clamped to 100. Both defaults are server configuration (`--default-page-size`, `--max-page-size`). A non-positive or non-integer `limit` is rejected. Values above the maximum are clamped, not rejected.
Endpoint ID: 39016
GET https://zylalabs.com/api/14930/apihub+places+api/39016/places
INPUT PARAMETERS

places — Endpoint Features

Object Description
cursor Optional Opaque cursor from a previous response's `next_cursor`. Unpadded URL-safe base64 of a JSON object `{"d": <distance_m>, "id": "<place id>"}`. Invalid base64 or a malformed payload is a 400 `invalid_cursor`. Omit this parameter for the first page.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

cursor
API EXAMPLE RESPONSE
JSON
{
    "total": 2,
    "items": [
        {
            "id": "08f1a2b3c4d5e6f7",
            "name": "Cafe Central",
            "category": "cafe",
            "brand_name": null,
            "address": "11000, RS, Belgrade, Stari Grad, Knez Mihailova",
            "latitude": 44.8176,
            "longitude": 20.4569,
            "distance_m": 42.5
        }
    ],
    "next_cursor": "eyJkIjo0Mi41LCJpZCI6IjA4ZjFhMmIzYzRkNWU2ZjcifQ"
}
Places — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14930/apihub+places+api/39016/places' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Same radius and text filters as `GET /api/places`, but returns every match in one response. `next_cursor` is always `null`. If `total` is greater than the server cap (default 5000, `--max-unpaginated-rows`), the server responds with 413 and no rows. Narrow `range_m`, add `q` or `category`, or use `GET /api/places`. `limit` and `cursor` are ignored on this endpoint.
Endpoint ID: 39017
GET https://zylalabs.com/api/14930/apihub+places+api/39017/all-places
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "total": 1,
    "items": [
        {
            "id": "08f1a2b3c4d5e6f7",
            "name": "Cafe Central",
            "category": "cafe",
            "brand_name": null,
            "address": "11000, RS, Belgrade, Stari Grad, Knez Mihailova",
            "latitude": 44.8176,
            "longitude": 20.4569,
            "distance_m": 42.5
        }
    ],
    "next_cursor": null
}
All-places — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14930/apihub+places+api/39017/all-places' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the apihub places API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Read-only HTTP API for Overture Maps places loaded into PostGIS. Search is a radius query around a WGS84 point. Results are ordered by distance ascending, then place id ascending. `q` is a case-insensitive substring match against place name or brand name. `category` is a case-insensitive substring match against the Overture `basic_category` value. `%` and `_` in those filters are matched literally. `GET /api/places` is cursor-paginated. `GET /api/places-all` returns every match and responds with 413 when the match count exceeds the server cap (default 5000). There is no account or API-key authentication. `/api/places`, `/api/places-all`, and `/mcp` are limited to 10 requests per second per client IP, with no extra burst. `/healthz` is not rate limited. CORS is permissive. `/mcp` is a [Model Context Protocol](https://modelcontextprotocol.io) Streamable HTTP endpoint (JSON responses), not a REST resource. It exposes one read-only tool, `search_places`, with the same filters and cursor pagination as `GET /api/places`. The server name is `apihub-places` and it does not geocode place names or user locations. This document describes the REST API only.

apihub places API FAQs

The `GET /api/places` endpoint returns a list of places within a specified radius, including details like place name, category, address, latitude, longitude, and distance from the query point. The `GET /api/places-all` endpoint returns all matching places without pagination, providing the same data structure.

Key fields in the response include `id` (unique identifier), `name` (place name), `category` (type of place), `brand_name` (if applicable), `address` (location details), `latitude`, `longitude`, and `distance_m` (distance from the query point).

The response data is structured in JSON format. It includes a `total` count of matches, an `items` array containing place details, and a `next_cursor` for pagination. Each item in the `items` array has fields like `id`, `name`, and `distance_m`.

Parameters for `GET /api/places` include `lat`, `lon` (for location), `range_m` (search radius), `q` (substring match for place or brand name), `category` (substring match for category), `limit` (number of results), and `cursor` (for pagination). The `GET /api/places-all` ignores `limit` and `cursor`.

Both endpoints provide information about places, including their names, categories, addresses, geographic coordinates, and distances from the specified location. The `GET /api/places` allows for filtered searches, while `GET /api/places-all` returns all matches.

Users can utilize the returned data to display nearby places based on user location, filter results by category or name, and paginate through results using the `next_cursor`. This is useful for applications like location-based services or travel guides.

Typical use cases include developing location-based applications, creating travel and tourism guides, enhancing local search functionalities, and integrating with mapping services to provide users with nearby places of interest.

Data accuracy is maintained through regular updates and quality checks, although specific sources and methods are not detailed. Users can expect reliable information based on the underlying Overture Maps data loaded into PostGIS.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs