AdminConsole
API reference/InTouch Telematics
POSTstatefullegacy-source evidencev1-0-0 · compare 2

Update A Geofence.

/geofence/{id}

This API helps to update a particular geofence.

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 v1-0-0 declaration and a retained alternative source generation. “Preferred” does not prove provider support or semantic compatibility.

Open field-level comparison and migration checklist
Request target

Call the operation

POSThttps://intouch.mapmyindia.com/iot/api/geofence/1
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey rolecommand
Content typesapplication/form-data
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
idrequired
pathinteger

geofence id.

1
Request body

Body schema

FieldTypeDescriptionExample
name
string

Name of the geofence.

market
buffer
integer

Buffer is nothing but radius in meters. If passed then by default the system will create a circle geofence. If buffer is not passed then by default the system will create a 'point' type geofence with radius as 50 meters

1000
geometry
string

This is a geoJSON string. You can pass here either 'Point' or 'Polygon'. Point is used for circular geofence, and Polygon is used for a multiple point polygon geofence

28.612964,77.229463
Request body example
{
  "name": "market",
  "buffer": 1000,
  "geometry": {
    "type": "Point",
    "coordinates": [
      77.2334,
      28.7676
    ]
  }
}
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/geofence/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/geofence/1' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_INTOUCH_TOKEN}" \
  --header "Content-Type: application/form-data" \
  --data-raw '{"name":"market","buffer":1000,"geometry":{"type":"Point","coordinates":[77.2334,28.7676]}}'

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 /geofence/{id}
curl --request POST \
  --url 'https://intouch.mapmyindia.com/iot/api/geofence/1' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "market",
  "buffer": 1000,
  "geometry": {
    "type": "Point",
    "coordinates": [
      77.2334,
      28.7676
    ]
  }
}'
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.

404

Not Found - 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.