POST Rename an existing dataset on mGIS engine

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

POSThttps://mgis-api.mappls.com/rename/style?oldDatasetNme=example&newDatasetNme=example

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

Authenticationbearer

Journey rolecommand

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

oldDatasetNmerequired

querystring

old dataset Name.

example

newDatasetNmerequired

querystring

new dataset Name.

example

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

POSThttps://mgis-api.mappls.com/rename/style?oldDatasetNme=example&newDatasetNme=example

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request POST \
  --url 'https://mgis-api.mappls.com/rename/style?oldDatasetNme=example&newDatasetNme=example' \
  --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.

POST /rename/style

curl --request POST \
  --url 'https://mgis-api.mappls.com/rename/style?oldDatasetNme=example&newDatasetNme=example' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Success and failure behavior

Responses

200

400

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

500

Internal Server Error, the request caused an error in our systems.

200 response fields

FieldTypeDescriptionExample

message

string

If everything goes ok then user receives a message indicating that the layer has been published/modified with new Dataset Name on mGIS platform

New Layer has been successfuly renamed with new style name.

Response example

{
  "message": "New Layer has been successfuly renamed with new style name."
}

stateful integration

Operate it safely

command

This operation creates or triggers durable state. Supply an idempotency strategy and persist the returned identifier before continuing.

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/v1/custom/sat-apis.yml
SHA-256: 15348c512128c6a43cfaf8fb29f24a78551008d1ee356cb76baa85a2724a65a8
Normalization: Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.
Source record: Open repository audit