• Optimization
  • Navigation
  • Tracking
  • Maps
  • Places

Discover API

Introduction

This endpoint allows one to process a free-form text query for an address or place, and returns results in order of relevance.

Request Parameters

Loading..

Response Schema

Loading..

Examples

Lets create a basic discover request in San Francisco area

Sample API Request

1https://api.nextbillion.io/discover?key=<your_api_key>&at=37.78182,-122.45291&q=gas&limit=5&in=countryCode:USA,MEX

Sample API Response

1{
2 "items": [
3 {
4 "title": "Rc Gas",
5 "id": "vVvq8TGB9Abonb1SYADenw",
6 "address": {
7 "label": "Rc Gas, 376 Castro Street, San Francisco, CA 94114, United States",
8 "countryCode": "USA",
9 "countryName": "United States",
10 "stateCode": "CA",
11 "state": "California",
12 "county": "San Francisco",
13 "city": "San Francisco",
14 "street": "Castro Street",
15 "postalCode": "94114-1524",
16 "houseNumber": "376"
17 },
18 "scoring": {

API Query Limits

Nextbillion.ai allows a maximum rate limit of 2400 queries per minute or 40 queries/second for continuous requests.

API Error Codes

Response CodeDescriptionAdditional Notes
200Normal success case.
Normal success case
400Input validation failed.
There is a missing or an invalid parameter or a parameter with an invalid value type is added to the request.
401APIKEY not supplied or invalid.
This error occurs when the wrong API key is passed in the request or the key is missing altogether
403APIKEY is valid but does not have access to requested resources.
You might be querying for a geographical region which is not valid for your account, or requesting a service which is not enabled for you.
404Requested host/path not found.
This error occurs when a malformed hostname is used.
422Could not process the request.
Valid results could not be generated for the given parameters. Please modify the constraints/search query.
429Too many requests.
QPM or API request count quota reached
500Internal Service error.
There was an internal issue with NextBillion.ai services. You can reach out to [email protected] for an explanation.