GET Get A Single Or Multiple Geofence(s).

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

GEThttps://intouch.mapmyindia.com/iot/api/geofence/1

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

Authenticationbearer

Journey roleobserve

Content typesNo request body

Path, query, and headers

Parameters

NameLocationTypeDescriptionExample

idrequired

pathinteger

geofence id. This path variable will take precedence even if multiple geofence ids are passed in the query param.

1

id

querystring

geofence id. Use this if you want to get details of specific multiple geofence IDs.

51777,89777

ignoreGeometry

queryboolean

Non mandatory field, boolean value to fetch geometry details.

28.612964,77.229463

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

GEThttps://intouch.mapmyindia.com/iot/api/geofence/1?id=51777%2C89777&ignoreGeometry=28.612964%2C77.229463

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/geofence/1?id=51777%2C89777&ignoreGeometry=28.612964%2C77.229463' \
  --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.

GET /geofence/{id}

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/geofence/1' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Success and failure behavior

Responses

200

OK - successful operation

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

200 response fields

FieldTypeDescriptionExample

data

array<object>

No field description in the source contract.

example

data[].id

number

Geofence ID

1

data[].name

string

name of the geofence.

market

data[].geometry

object

No field description in the source contract.

28.612964,77.229463

data[].geometry.type

string

This defines the type of geofence, it can be point or polygon.

Point

data[].geometry.coordinates

array<number>

No field description in the source contract.

28.612964,77.229463

data[].type

string

Depending on the type of geofence this value can be Circle(buffer > 50 meters), Polygon or Point(buffer = 50 mtrs)

Circle

data[].buffer

number

Radius(in meters) of a circlular geofence

65.76

data[].creationTime

number

timestamp, in seconds, at which the geofence was created.

1700000000000

data[].updationTime

number

timestamp, in seconds, at which the geofence was updated.

1700000000000

Response example

{
  "data": [
    {
      "id": "1",
      "name": "market",
      "geometry": {
        "type": "Point",
        "coordinates": [
          77.456,
          28.2345
        ]
      },
      "type": "Circle",
      "buffer": 65.76,
      "creationTime": "1",
      "updationTime": "1"
    }
  ]
}

stateful integration

Operate it safely

observe

This operation observes durable platform state. Preserve resource identifiers and account for pagination, delay, and eventual consistency.

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