GET Validates the query to be applied on a dataset.

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.

Request target

Call the operation

GEThttps://mgis-apiv2.mappls.com/dqv/query_validation?datasetNme=india&query=state+%3D+%27Delhi%27

Base URLhttps://mgis-apiv2.mappls.com/

Authenticationbearer

Journey roleobserve

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

datasetNmerequired

querystring

The dataset name of whose information has to be fetched.

india

queryrequired

querystring

Query to be applied on the dataset. Mandatory if uniqueValue and summerizeValue parameter is not passed.

state = 'Delhi'

dataStoreName

querystring

Name of datastore where adaptor published.

adaptor

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

Generated in eight languages

Environment-backed credentials

GEThttps://mgis-apiv2.mappls.com/dqv/query_validation?datasetNme=india&query=state+%3D+%27Delhi%27&dataStoreName=adaptor

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/dqv/query_validation?datasetNme=india&query=state+%3D+%27Delhi%27&dataStoreName=adaptor' \
  --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 /dqv/query_validation

curl --request GET \
  --url 'https://mgis-apiv2.mappls.com/dqv/query_validation?datasetNme=india&query=state+%3D+%27Delhi%27' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Success and failure behavior

Responses

200

206

Impartial Content.

400

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

404

No data found in database.

422

Parameter missing

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

Displays the message wheather the query is valid or invalid.

Valid Query

data

object

No field description in the source contract.

example

Response example

{
  "code": "200",
  "success": true,
  "message": "Valid Query",
  "data": "example"
}

stateful integration

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.

Auditable source

Contract provenance

Source file: mappls-developer-platform/data/corpus/public-api-contracts/mapmyindia-mgis-apis/docs/v2/custom/dqv-apis.yml
SHA-256: 391a57c02f461cd4b27fba7b0ef8f838096a4cc16680bb2c6df225fbcf1fe427
Normalization: Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.
Source record: Open repository audit