API reference/Core Maps, Search & Routing
GETstatelesslegacy-source evidence

Place Detail API

/apis/O2O/entity/{eLoc}

MapmyIndia eloc is a simple, standardized and precise pan-India digital address system. Every location has been assigned a unique digital address or an eLoc. Place Detail API can be used to extract the details of a place with the help of its eLoc i.e. a 6 digit code or a placeid. This APIs follow OAuth2 based security. To know more on how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: "{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.

Legacy contract evidence

This operation was normalized from a MapmyIndia-generation specification. Validate its current Mappls host, path, package entitlement, authentication generation, and commercial availability before production use.

Call the operation

GEThttps://explore.mapmyindia.com/apis/O2O/entity/MMI000
Base URLhttps://explore.mapmyindia.com
Authenticationoauth2 bearer
Journey rolerequest response
Content typesNo request body

Parameters

NameLocationTypeDescriptionExample
eLocrequired
pathstring

Six or Eight Digit unique code.

MMI000

Build your request in eight languages

Change source-backed examples once, validate required inputs, and copy the synchronized cURL, JavaScript, Python, Java, C#, Go, PHP, or Ruby request. Credentials remain environment references, and this page never sends a provider request.

Local request composerCode stays local · fixtures are explicit
GETRequest inputs
1 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://explore.mapmyindia.com/apis/O2O/entity/MMI000
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request GET \
  --url 'https://explore.mapmyindia.com/apis/O2O/entity/MMI000' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}"

Credential-safe by constructionSet MAPPLS_ACCESS_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Send a production-shaped request

Examples use environment-backed access tokens, explicit timeouts where supported, status checks, and JSON bodies derived from the source schema. Replace sample identifiers and coordinates with values from your application.

GET /apis/O2O/entity/{eLoc}
curl --request GET \
  --url 'https://explore.mapmyindia.com/apis/O2O/entity/MMI000' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Responses

200

This API is highly configurable API that enables to provision the required set of attributes to the user on the basis of their required use case. The default configuration with available with basic pay-as-you-go rates is that of General Details subtemplate.

204

Not found

400

Bad request

401

API access denied

403

Forbidden

500

Something went wrong

503

Internal server error

Response example
{
  "eloc": "3F45CB",
  "name": "The Lalit New Delhi",
  "address": "15, Barakhamba Avenue, Connaught Place, New Delhi, Delhi, 110001"
}

Operate it safely

request-response

This operation is evaluated independently from the request. Cache and retry according to its documented semantics.

Keep credentials and raw tokens out of source, client bundles, prompts, and logs.Record the operation ID, status, latency, retry count, and source contract version in traces.Classify 4xx responses before retrying; back off and add jitter for retryable 5xx or transport failures.Cache only when request inputs, authorization scope, and freshness requirements permit it.

Contract provenance

Source file
contenthub/dochub/mapmyindia-rest-api/docs/custom/placeDetail-adv.yml
SHA-256
569fa6048fd4bcd14e00e727de4863ec5aae3b9a8318097a7e2125d32572b1a2
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.