API reference/InTouch Telematics
POSTstatefullegacy-source evidence

Create A New Geofence

/geofences

This API helps to create a new geofence

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.

Call the operation

POSThttps://intouch.mapmyindia.com/iot/api/geofences
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey rolecommand
Content typesapplication/form-data

Parameters

NameLocationTypeDescriptionExample
No explicit parameters are declared by the source operation.

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
    ]
  }
}

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
0 editable · 0 protected
This operation has no editable path or query parameters.
Generated in eight languages
Environment-backed credentials
POSThttps://intouch.mapmyindia.com/iot/api/geofences
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/geofences' \
  --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.

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

Responses

201

Created

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

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.

Contract provenance

Source file
contenthub/dochub/mapmyindia-intouch-rest-apis/custom/geofence.json
SHA-256
fc26724559038e8d114001105966c2bd30e35ac4f8c0a1644d9241eb4bd64425
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.