AdminConsole
API reference/Geo-Analytics Listing
GETstatelesslegacy-source evidence

List layer attributes or a layer bounding box

/listingapi

Returns documented attribute values or bbox for one Geo-Analytics layer. Supply addr, or supply geoboundtype together with geobound.

Build a requestGet credentials
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.

Request target

Call the operation

GEThttps://geoanalytics.mapmyindia.com/listingapi?api=district&get_attr=dst_id%2Cdst_nme%2Cstt_nme%2Cstt_id%2Cb_box
Base URLhttps://geoanalytics.mapmyindia.com
Authenticationbearer
Journey rolerequest response
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
geo_bound_type
querystring

Parent type; required with geobound when addr is absent.

stt_nme
geo_bound
querystring

Parent value; required with geoboundtype when addr is absent.

Haryana
addr
querystring

Comma-separated address; required when geoboundtype and geobound are absent.

Jhansi, Uttar Pradesh
apirequired
querystring

Layer name such as state, district, subdistrict, village, or pincode.

district
get_attrrequired
querystring

Comma-separated documented attributes or bbox.

dst_id,dst_nme,stt_nme,stt_id,b_box
Interactive, local, and credential-safe

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
5 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://geoanalytics.mapmyindia.com/listingapi?geo_bound_type=stt_nme&geo_bound=Haryana&addr=Jhansi%2C+Uttar+Pradesh&api=district&get_attr=dst_id%2Cdst_nme%2Cstt_nme%2Cstt_id%2Cb_box
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request GET \
  --url 'https://geoanalytics.mapmyindia.com/listingapi?geo_bound_type=stt_nme&geo_bound=Haryana&addr=Jhansi%2C+Uttar+Pradesh&api=district&get_attr=dst_id%2Cdst_nme%2Cstt_nme%2Cstt_id%2Cb_box' \
  --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.

Five language quickstarts

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 /listingapi
curl --request GET \
  --url 'https://geoanalytics.mapmyindia.com/listingapi?api=district&get_attr=dst_id%2Cdst_nme%2Cstt_nme%2Cstt_id%2Cb_box' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Success and failure behavior

Responses

200

Documented successful listing response.

400

Client-side request error documented by responseCode class.

500

Server-side error documented by responseCode class.

200 response fields

FieldTypeDescriptionExample
responseCoderequired
integer

No field description in the source contract.

200
versionrequired
string

No field description in the source contract.

1.0.0
total_feature_countrequired
integer

No field description in the source contract.

1
resultsrequired
object

No field description in the source contract.

example
results.api_name
string

No field description in the source contract.

district
results.attribute
string

No field description in the source contract.

dst_id
results.get_attr_values
array<object>

No field description in the source contract.

example
Response example
{
  "responseCode": 200,
  "version": "1.0.0",
  "total_feature_count": 1,
  "results": {
    "api_name": "district",
    "attribute": "dst_id",
    "get_attr_values": [
      "example"
    ]
  }
}
stateless integration

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.
Auditable source

Contract provenance

Source file
mappls-developer-platform/data/contracts/geoanalytics-listing.openapi.yml
SHA-256
e358eab2ef038c2d03df69920dd1789bdd188b5196b8cf8d780bfab7693eb6e3
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.