- Previous: GET /v1/entity/search/who/bynearest
- Up: Central Index API
- Next: GET /v1/location/context
GET /v1/location
HTTP Method: GET
Path: /v1/location
Authentication: API Key required
Description: Fetch details of a location by supplying its unique identifier.
Parameters:
parameter | type | description | required |
location_id | string | The unqiue identifier of thelocation to fetch e.g. GBN33RD | yes |
Sample Response:
{ "success": true, "msg": "ok", "data": { "_id": "GBN33RD", "_rev": "2-e039b1fbff704d784ccebd0df4bb4718", "name": "N3 3RD", "formal_name": "N3 3RD", "latitude": 51.59379959106445, "longitude": -0.1938209980726242, "resolution": "postalcode", "country": "gb", "population": 0, "description": "", "timezone": "Europe/London", "parent_town": [ "GB14648" ], "parent_county": [], "parent_province": [ "GB41673" ], "parent_neighbourhood": [ "GB12332" ], "parent_region": [ "GB13660" ], "parent_district": [ "GB41717" ], "postalcode": [], "language": "en", "type": "postal" } }
If the API had been asked to fetch a non-existent location, then you will see this response:
{ "success": false, "msg": "Unable to return some requested documents", "data": { "missing": true, "errors": [ "location_id GB33RD is missing" ] } }
- Previous: GET /v1/entity/search/who/bynearest
- Up: Central Index API
- Next: GET /v1/location/context
Docs Navigation
- Introduction
- Getting Started
- Using IODocs
- Responses
- Creating a sample request
- Sample Libraries
- Central Index API
- What data do we store in an entity?
- GET /v1/advertiser/updated
- GET /v1/autocomplete/category
- GET /v1/autocomplete/keyword
- GET /v1/autocomplete/location
- GET /v1/entity
- GET /v1/entity/advertisers
- GET /v1/entity/advertisers/inventorycheck
- GET /v1/entity/by_supplier_id
- GET /v1/entity/search/keyword/bynearest
- GET /v1/entity/search/what
- GET /v1/entity/search/what/bylocation
- GET /v1/entity/search/what/byboundingbox
- GET /v1/entity/search/what/bynearest
- GET /v1/entity/search/who
- GET /v1/entity/search/who/bylocation
- GET /v1/entity/search/who/byboundingbox
- GET /v1/entity/search/who/bynearest
- GET /v1/location
- GET /v1/location/context
- GET /v1/lookup/category
- GET /v1/match/byphone
- GET /v1/stats/entity/by_date
- GET /v1/syndication_log/by_entity_id
- GET /v1/token/add
- GET /v1/token/report
- GET /v1/token/claim
- GET /v1/token/message
- GET /v1/tools/docs
- GET /v1/user/by_email
- PUT /v1/business
- PUT /v1/business/json
- PUT /v1/entityserve
- POST /v1/entity/advertiser/cancel
- POST /v1/entity/advertiser/create
- POST /v1/entity/advertiser/renew
- POST /v1/entity/advertiser/upsell
- POST /v1/entity/category
- POST /v1/entity/claim
- POST /entity/claim/cancel
- POST /v1/entity/claim/reseller
- POST /v1/entity/description
- POST /v1/entity/document
- POST /v1/entity/email
- POST /v1/entity/fax
- POST /v1/entity/featured_message
- POST /v1/entity/geopoint
- POST /v1/entity/image
- POST /v1/entity/image/by_url
- POST /v1/entity/list
- POST /v1/entity/logo
- POST /v1/entity/logo/by_url
- POST /v1/entity/name
- POST /v1/entity/opening_times
- POST /v1/entity/payment_type
- POST /v1/entity/phone
- POST /v1/entity/postal_address
- POST /v1/entity/socialmedia
- POST /v1/entity/special_offer
- POST /v1/entity/tag
- POST /v1/entity/testimonial
- POST /v1/entity/video/youtube
- POST /v1/entity/website
- POST /v1/syndication/cancel
- POST /v1/syndication/create
- POST /v1/signal
- POST /v1/user
- DELETE /v1/entity/category
- DELETE /v1/entity/description
- DELETE /v1/entity/image
- DELETE /v1/entity/phone
- DELETE /v1/entity/logo
- DELETE /v1/entity/website
- syndication api