AdminConsole
API reference/InTouch Telematics
GETstatefullegacy-source evidence

This API will get all the groups for a user.

/groups

Based on the passed token key, the API will return the list of all groups.

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

GEThttps://intouch.mapmyindia.com/iot/api/groups
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey roleobserve
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
id
querystring

This is the alarm's ID, a non-mandatory parameter. If not passed then by default the API will return the list of all alarm configurations in the account. You can pass single value or comma separated alarm IDs for multiple values.

23889,89876
deviceId
querystring

This is device ID. API will return data based on the configs set for the passed device IDs. You can pass a single device ID or comma seperated multiple device IDs.

24567,10018
alarmType
querystring

This is alarm type. API will return data based on the passed alarm types. You can pass a single alarm type or comma seperated multiple alarm types.

177,90
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
GETRequest inputs
3 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://intouch.mapmyindia.com/iot/api/groups?id=23889%2C89876&deviceId=24567%2C10018&alarmType=177%2C90
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/groups?id=23889%2C89876&deviceId=24567%2C10018&alarmType=177%2C90' \
  --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.

GET /groups
curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/groups' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Success and failure behavior

Responses

200

OK - successful operation

203

Device Not Found

400

Bad Request - Invalid ID supplied or invalid data type.

401

Unauthorized Request. Access to API is forbidden.

404

Not Found - URL Not Found

200 response fields

FieldTypeDescriptionExample
data
array<object>

No field description in the source contract.

example
data[].id
number

This is group ID

7656
data[].deviceId
array<number>

Device ID(s) which associated with the group.

[67700,8987]
data[].name
string

name of the group

my group
data[].createdOn
number

Time at which the group got created.

1567654565
data[].updatedOn
integer

Time at which the group got updated.

1567654565
data[].colorCode
string

color associated with the group

example
Response example
{
  "data": [
    {
      "id": 7656,
      "deviceId": [
        67700,
        8987
      ],
      "name": "my group",
      "createdOn": 1567654565,
      "updatedOn": 1567654565,
      "colorCode": "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
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.