POST Updates An Alarm Config · Mappls Developers

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

POSThttps://intouch.mapmyindia.com/iot/api/alarm/1

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

Authenticationbearer

Journey rolecommand

Content typesapplication/form-data

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

idrequired

pathinteger

Mandatory field. This is the ID of the alarm config which needs to be updated.

1

Request body

Body schema

FieldTypeDescriptionExample

deviceId

array<number>

ID of the device for which the alarm config has to be updated. If there are multiple devices then you can pass them separated by comma.

[6678,9876]

type

integer

For Geofence(alarmType = 26), value of type are as follows: 2 - entry, 3 - Exit, 1 - Entry & Exit, 4 - long stay in geofence For ignition(alarmType = 21), types values are as follows: 1 - Both ON & OFF, 2 - Ignition On, 3 - Ignition Off, 5 - Day's First Ignition ON For mileage(alarmType = 133), value of type are as follows: 0 - Daily, 1 - Monthly For DIstance Covered(alarmType = 151), value of type are as follows: 1 - At Least, 2 - At Most

1

duration

integer

Only required in case of overspeed, stoppage, idle, towing, GPRS connectivity, vehicle battery, GPS connectivity, distance covered, internal battery alarm

11

limit

integer

Only required in case of overspeed, vehicle battery, mileage, distance covered, internal battery alarm

55

geofenceId

array<number>

Only required when alarmType is 26 (Geofence). You can pass a single geofence ID or multiple geofence IDs separated by comma

[23434,45454]

severity

integer

This basically defines the severity of the alarm. You can pass 0 for normal severity & 1 for high severity.

0

Request body example

{
  "deviceId": [
    6678,
    9876
  ],
  "type": 1,
  "duration": 11,
  "limit": 55,
  "geofenceId": [
    23434,
    45454
  ],
  "severity": 0
}

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

POSThttps://intouch.mapmyindia.com/iot/api/alarm/1

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/alarm/1' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_INTOUCH_TOKEN}" \
  --header "Content-Type: application/form-data" \
  --data-raw '{"deviceId":[6678,9876],"type":1,"duration":11,"limit":55,"geofenceId":[23434,45454],"severity":0}'

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 /alarm/{id}

curl --request POST \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/1' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "deviceId": [
    6678,
    9876
  ],
  "type": 1,
  "duration": 11,
  "limit": 55,
  "geofenceId": [
    23434,
    45454
  ],
  "severity": 0
}'

Success and failure behavior

Responses

200

OK - successful operation

400

Bad Request - Invalid ID supplied or invalid data type.

401

Unauthorized Request. Access to API is forbidden.

403

ID Not Found

404

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