AdminConsole
API reference/InTouch Telematics
DELETEstatefullegacy-source evidencev2-0-0 · compare 2

Deletes An Alarm Config

/alarm/{id}

A set of powerful telematics APIs which users can use to get all the data related to their devices such as live location,trails,alarms etc. These telematics APIs are powered by MapmyIndia's own INTOUCH platform. MapmyIndia InTouch easily integrates into existing cloud services via our tracking & telematics APIs. The API & SDK libraries provide powerful, efficient and accurate positioning for the IoT devices on InTouch applications for Android, iOS and the web. You can find out more about Intouch at http://mapmyindia.com/intouch

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.

Version-aware contract

Compare before changing adapters

This is the v2-0-0 declaration and the highest version-labelled source evidence. “Preferred” does not prove provider support or semantic compatibility.

Open field-level comparison and migration checklist
Request target

Call the operation

DELETEhttps://intouch.mapmyindia.com/iot/api/alarm/1
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey roleretire
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
idrequired
pathinteger

id of the alarm config which you want to delete

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
DELETERequest inputs
1 editable · 0 protected
Generated in eight languages
Environment-backed credentials
DELETEhttps://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 DELETE \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/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.

DELETE /alarm/{id}
curl --request DELETE \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/1' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Success and failure behavior

Responses

200

OK - successful operation

204

No Content Found

400

Bad Request - Invalid ID supplied or invalid data type.

401

Unauthorized Request. Access to API is forbidden.

404

URL Not Found

stateful integration

Operate it safely

retire

This operation removes or retires state. Confirm ownership, dependent resources, audit retention, and recovery behavior before execution.

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/alarm.yaml
SHA-256
9789c0e53eba5ec44918ca8aade24d4b856aaade5c692109943d1e262fb2545a
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.