GET Gets the basic info of devices.

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/devices/info

Base URLhttps://intouch.mapmyindia.com/iot/api

Authenticationbearer

Journey roleobserve

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

id

queryinteger

id of the device, a non-mandatory parameter. If not passed then by default the API will return the basic info of all active devices in the account.

1

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://intouch.mapmyindia.com/iot/api/devices/info?id=1

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/devices/info?id=1' \
  --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 /devices/info

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/devices/info' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Success and failure behavior

Responses

200

OK - successful operation

204

No content found

400

Bad Request - Invalid device ID supplied or device id is missing or invalid data type. For example, input attribute id is integer but string value gets passed.

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

integer

id of the device.

1

data[].name

string

name of the device.

my vehicle 1878

data[].type

integer

0 - car, 1 - person, 2 - asset, 3 - bike, 4 - bus, 5 - truck, 6 - tracktor.

2

data[].creationOn

number

the date when the device was created.

1585541181

data[].updationOn

number

date when device got updated

1585541181

data[].expiryDate

number

date when device will get expired

1585541181

data[].active

boolean

whether device is active or not

true

data[].registrationNumber

string

device's registraion number

DL03555

data[].manufacturer

string

device manufactured by

BMW

data[].model

string

device's model type

X3

data[].color

string

color of the device

example

data[].geofenceIds

array<number>

No field description in the source contract.

example

data[].tag

array<string>

No field description in the source contract.

example

data[].chasisNo

string

chasis number of the device.

EXASDSSSSADC

data[].initialOdometer

number

initial odometer reading.

0

Response example

{
  "data": [
    {
      "id": "1",
      "name": "my vehicle 1878",
      "type": 2,
      "creationOn": 1585541181,
      "updationOn": 1585541181,
      "expiryDate": 1585541181,
      "active": true,
      "registrationNumber": "DL03555"
    }
  ]
}

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/device.json
SHA-256: 58a17aea1fc8a386e467f0266fb5d92e52e148c709fbcb95565be5c0f25895a4
Normalization: Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.
Source record: Open repository audit