API reference/mGIS Analytics
GETstatefulexact public snapshotv2 · compare 2

fetches the attribute names.

/describeDataset

Fetches the attribute names of the dataset except geometry in response.

Exact public source snapshot

This operation is retained because its version-labelled public specification differs structurally from another generation. It is comparison evidence, not a promise of current support, compatibility, entitlement, or availability.

Compare before changing adapters

This is the v2 declaration and the highest version-labelled source evidence. “Preferred” does not prove provider support or semantic compatibility.

Open field-level comparison and migration checklist

Call the operation

GEThttps://mgis-apiv2.mappls.com/describeDataset?datasetNme=india
Base URLhttps://mgis-apiv2.mappls.com/
Authenticationbearer
Journey roleobserve
Content typesNo request body

Parameters

NameLocationTypeDescriptionExample
datasetNmerequired
querystring

Returns all attribute names except geometry against a dataset.

india
dataStoreName
querystring

Name of the dataStoreName in case of data adaptor.

india

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
2 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://mgis-apiv2.mappls.com/describeDataset?datasetNme=india&dataStoreName=india
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request GET \
  --url 'https://mgis-apiv2.mappls.com/describeDataset?datasetNme=india&dataStoreName=india' \
  --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 /describeDataset
curl --request GET \
  --url 'https://mgis-apiv2.mappls.com/describeDataset?datasetNme=india' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Responses

200

OK

400

Bad Request, User made an error while creating a valid request.

401

Unauthorized.

500

Internal server error.

200 response fields

FieldTypeDescriptionExample
code
string

Response code.

200
success
string

No field description in the source contract.

true
message
string

No field description in the source contract.

data
object

No field description in the source contract.

example
data.propertyList
array<object>

No field description in the source contract.

example
data.propertyList[].ColumnName
string

Name of Column

st_name
data.propertyList[].ColumnType
string

Data Type of ColumnName

string
Response example
{
  "code": "200",
  "success": true,
  "message": "",
  "data": {
    "propertyList": [
      {
        "ColumnName": "st_name",
        "ColumnType": "string"
      }
    ]
  }
}

Operate it safely

observe

This operation observes durable platform state. Preserve resource identifiers and account for pagination, delay, and eventual consistency.

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.Persist resource identifiers and apply commands exactly once in effect across retries and event replay.

Contract provenance

Source file
mappls-developer-platform/data/corpus/public-api-contracts/mapmyindia-mgis-apis/docs/v2/custom/describe-dataset-api.yml
SHA-256
ea4acadc9a13ed87bdc8f5b4a009cb6eebcc13efc93221a3103ac8f5ea70c9b6
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.