POST Uploads and publishes the 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-apiv2.mappls.com/sat/saveDataset/file

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

Authenticationbearer

Journey rolecommand

Content typesmultipart/form-data

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

No explicit parameters are declared by the source operation.

Required body

Body schema

FieldTypeDescriptionExample

datasetNme

string

Name of the dataset that will be used while saving/appending/truncating [If not provided filename is taken as datasetNme]

test

filerequired

string

File that data contains data that needs to be published/appended [max size: 20 MB]

example

sheetName

string

Name of the sheet incase the file is one of the spreadsheet formats [If not provided first sheet of the document is taken by default]

example

lat

string

Name of the column containing latitude incase the file is one of the spreadsheet formats [If not provided 'Lat' is taken by default]

28.612964

lng

string

Name of the column containing longitude incase the file is one of the spreadsheet formats [If not provided 'Lng' is taken by default]

77.229463

appendStatus

string

If set to true, the file provided will be appended to pre-existing data within the dataset of name provided in datasetNme param [condition is that the data should exist / no need to set it to false in case of non-appending]

example

truncateStatus

string

If set to true, the file provided will be appended and pre-existing data within the dataset of name provided in datasetNme param will be truncated/deleted [condition is that the data provided should be of same structure OR should contain previous structure else there can be loss of information / no need to set it to false]

example

polygonfillcolor

string

hex color without '#' of the polygon/s

f2e824

polygonfillopacity

string

opacity of polygon/s ranging from 0-1

0.7

linestrokecolor

string

hex color without '#' of the line/s

2ce622

linestrokewidth

string

width of the line/s in pixels

2

linestrokeopacity

string

opacity of line/s ranging from 0-1

0.5

pointfillcolor

string

hex color without '#' of the point/s

2266e3

pointfillopacity

string

opacity of point/s ranging from 0-1

0.8

pointsize

string

size of point/s in pixels

10

Request body example

{
  "file": "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-apiv2.mappls.com/sat/saveDataset/file

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request POST \
  --url 'https://mgis-apiv2.mappls.com/sat/saveDataset/file' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}" \
  --header "Content-Type: multipart/form-data" \
  --data-raw '{"file":"example"}'

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 /sat/saveDataset/file

curl --request POST \
  --url 'https://mgis-apiv2.mappls.com/sat/saveDataset/file' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "file": "example"
}'

Success and failure behavior

Responses

200

400

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

401

Unauthorized.

500

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

200 response fields

FieldTypeDescriptionExample

code

string

Error code.

200

success

string

No field description in the source contract.

true

message

string

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

Layer 'LAYER_NAME' has been published/modified in workspace 'WORKSPACE_NAME'

data

unknown

No field description in the source contract.

{}

Response example

{
  "code": "200",
  "success": true,
  "message": "Layer 'LAYER_NAME' has been published/modified in workspace 'WORKSPACE_NAME'",
  "data": {}
}

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