AdminConsole
API reference/InTouch Telematics
POSTstatefullegacy-source evidence

This API will create a group.

/groups

Based on the input parameters provided to this POST group API, a new group will get created for a single or multiple devices

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

POSThttps://intouch.mapmyindia.com/iot/api/groups?name=example
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey rolecommand
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
namerequired
querystring

This the name of the group which you want to create.

example
deviceId
queryarray<number>

These are the IDs of the devices which you want to have in this group. You can pass a single device id or a set of multiple ids separated by comma.

["1009,6765,8798"]
colorCode
querystring

This the color code(in hex format) which you want to associated with the group.

#24545
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
POSTRequest inputs
3 editable · 0 protected
Generated in eight languages
Environment-backed credentials
POSThttps://intouch.mapmyindia.com/iot/api/groups?name=example&deviceId=%5B%221009%2C6765%2C8798%22%5D&colorCode=%2324545
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request POST \
  --url 'https://intouch.mapmyindia.com/iot/api/groups?name=example&deviceId=%5B%221009%2C6765%2C8798%22%5D&colorCode=%2324545' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_INTOUCH_TOKEN}"

Credential-safe by constructionSet MAPPLS_INTOUCH_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 /groups
curl --request POST \
  --url 'https://intouch.mapmyindia.com/iot/api/groups?name=example' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Success and failure behavior

Responses

201

Created

203

Device Not Found or invalid device id

400

Bad Request - Invalid ID supplied or invalid data type.

401

Unauthorized Request. Access to API is forbidden.

404

Not Found - URL Not Found

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
contenthub/dochub/mapmyindia-intouch-rest-apis/custom/group.json
SHA-256
669b74b917e37baa2cafdb2411c242905e2b6d41de32726767a387c1838ea87d
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.