AdminConsole
API reference/InTouch Telematics
POSTstatefullegacy-source evidence

POST API to close a trip.

/trips/{id}/close

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.

Request target

Call the operation

POSThttps://intouch.mapmyindia.com/iot/api/trips/1/close
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey rolecommand
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
idrequired
pathnumber

This the ID of the trip which you want to close.

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
POSTRequest inputs
1 editable · 0 protected
Generated in eight languages
Environment-backed credentials
POSThttps://intouch.mapmyindia.com/iot/api/trips/1/close
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/trips/1/close' \
  --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.

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

Responses

200

OK - successful operation

203

invalid param. For eg; if trip id is not correct.

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

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/trip.json
SHA-256
f475d06cfb9d7bafd8521d713749489be1b26d16de205007fd0b42eef06c254f
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.