GET Gets The List Of Alarm Config(s)

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.

Version-aware contract

Compare before changing adapters

This is the v1-0-0 declaration and a retained alternative source generation. “Preferred” does not prove provider support or semantic compatibility.

v1-0-0This reference v2-0-0Open exact reference

Open field-level comparison and migration checklist

Request target

Call the operation

GEThttps://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?startTime=1700000000000&endTime=1700000000000

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

Authenticationbearer

Journey roleobserve

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

deviceId

querystring

Not Mandatory field. This is the ID of the device for which the alarm log need to be fetched. You can pass single device ID or multiple device IDs separated by comma

1909,2545

alarmType

querystring

Not Mandatory field. This is the type of alarm for which the alarm log need to be fetched. You can pass single alarm type or multiple device IDs separated by comma. Type of alarm to create. Following are the alarm types & their corresponding IDs. IGNITION: 21, OVERSPEED: 22, UNPLUGGED: 23, PANIC: 24, GEOFENCE: 26, STOPPAGE: 27, IDLE: 28, TOWING: 29, GPRS CONNECTIVITY: 126, VEHICLE BATTERY: 129, MILEAGE: 133, GPS CONNECTIVITY: 146, DISTANCE COVERED: 151, INTERNAL BATTERY VOLTAGE:161

21,26

startTimerequired

querynumber

Mandatory field. This is start timestamp in seconds

1700000000000

endTimerequired

querynumber

Mandatory field. This is end timestamp in seconds

1700000000000

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

4 editable · 0 protected

deviceIdqueryNot Mandatory field. This is the ID of the device for which the alarm log need to be fetched. You can pass single device ID or multiple device IDs separated by commaalarmTypequeryNot Mandatory field. This is the type of alarm for which the alarm log need to be fetched. You can pass single alarm type or multiple device IDs separated by comma. Type of alarm to create. Following are the alarm types & their corresponding IDs. IGNITION: 21, OVERSPEED: 22, UNPLUGGED: 23, PANIC: 24, GEOFENCE: 26, STOPPAGE: 27, IDLE: 28, TOWING: 29, GPRS CONNECTIVITY: 126, VEHICLE BATTERY: 129, MILEAGE: 133, GPS CONNECTIVITY: 146, DISTANCE COVERED: 151, INTERNAL BATTERY VOLTAGE:161startTimerequiredqueryMandatory field. This is start timestamp in secondsendTimerequiredqueryMandatory field. This is end timestamp in seconds

Generated in eight languages

Environment-backed credentials

GET

https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000

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/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000' \
  --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 /alarm/alarmLog/

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?startTime=1700000000000&endTime=1700000000000' \
  --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[].deviceId

number

Will come only in case of /alarmLog GET API response

8989

data[].timestamp

number

Time at which the alert got generated

1700000000000

data[].latitude

number

No field description in the source contract.

28.612964

data[].longitude

number

No field description in the source contract.

77.229463

data[].address

string

Location address at which the alarm got generated

237, Okhla Industrial Estate Phase 3, New Delhi, Delhi. 19 m from Wipro BPO Corporate Office pin-110020

data[].alarmType

integer

Type of alarm to create. Following are the alarm types & their corresponding IDs. IGNITION: 21, OVERSPEED: 22, UNPLUGGED: 23, PANIC: 24, GEOFENCE: 26, STOPPAGE: 27, IDLE: 28, TOWING: 29, GPRS CONNECTIVITY: 126, VEHICLE BATTERY: 129, MILEAGE: 133, GPS CONNECTIVITY: 146, DISTANCE COVERED: 151, INTERNAL BATTERY VOLTAGE:161

28

data[].limit

integer

Alarm limit as set in the config. For example, if an overspeed alarm set on limit of 44 km/hr in the alarm config setting, then this attribute will return 44 km/hr

44

data[].duration

integer

Alarm duration limit as set in the alarm config section. For example, if duration of overspeed alarm is set as 20 secs, then the alarm will generate when the vehicle overspeeds for a duration of 20 secs

20

data[].actualLimit

integer

The actual data received from the device at that particular moment when the alarm got generated

57

data[].actualDuration

integer

Actual duration for which the device breached the alarm config limit

25

data[].severity

integer

0 - Low Severity. 1 - High Severity

1

data[].data

integer

Describes the state of the alarm. IGNITION(type = 21), 0: OFF & 1: ON. AC(type=25), 0: OFF, 1: ON. GEOFENCE(type=26), 1: Entry & Exit Geofence 2: Entry Geofence, 3: Leaving Geofence & 4: Long Stay In Geofence

1

data[].geofenceId

number

This is the ID of the geofence for which the alarm got generated. This will come only when the 'type' field return 26 i,e geofence.

987876

Response example

{
  "data": [
    {
      "deviceId": 8989,
      "timestamp": 1577589789,
      "latitude": 28.550962381896,
      "longitude": 77.26890675033,
      "address": "237, Okhla Industrial Estate Phase 3, New Delhi, Delhi. 19 m from Wipro BPO Corporate Office pin-110020",
      "alarmType": 28,
      "limit": 44,
      "duration": 20
    }
  ]
}

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/Intouch-Telematics-Swagger-25052020.json
SHA-256: 54637441ab0c8ea447e121ba33afbc464e714a3dbceec49d4b70dabe9778657f
Normalization: Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.
Source record: Open repository audit