GET Gets the hardware 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/hardwareinfo

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

Authenticationbearer

Journey roleobserve

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

id

queryinteger

This is the physical device's ID, a non-mandatory parameter. If not passed then by default the API will return the hardware 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/hardwareinfo?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/hardwareinfo?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/hardwareinfo

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/devices/hardwareinfo' \
  --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 physical hardware device

1

data[].name

string

name of the physical hardware device

MMI314295

data[].deviceType

integer

type of device for eg; drivate, vt etc

868728030749458

data[].deviceTypeName

string

name of the type of device

drive mate pro

data[].trackingCode

string

tracking code/unique code number of the device

868728030749458

data[].deviceCode

string

another unique number, genrally same as tracking code

868728030749458

data[].active

boolean

true means device is active. false means device is not active

true

data[].mappedDeviceIds

array<number>

No field description in the source contract.

example

data[].odometerType

integer

0 - odometer not suported, 1- GPS based odometer(comes from the device), 2 - CAN based Odometer(comes from vehicle's CAN bus)

2

data[].installDate

number

timstamp when the device got installed

1581273000

data[].expiryDate

number

timestamp when the device will get expired

1600713000

Response example

{
  "data": [
    {
      "id": "1",
      "name": "MMI314295",
      "deviceType": "868728030749458",
      "deviceTypeName": "drive mate pro",
      "trackingCode": "868728030749458",
      "deviceCode": "868728030749458",
      "active": true,
      "mappedDeviceIds": [
        887876
      ]
    }
  ]
}

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