AdminConsole
API reference/InTouch Telematics
GETstatefullegacy-source evidence

Get all the activities done by devices w.r.t various geofences

/geofences/activities

This API helps to fetch the details of all the activities, such as geofence entry time, exit time etc, which devices perform w.r.t various geofences across a defined date/time range.

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

GEThttps://intouch.mapmyindia.com/iot/api/geofences/activities?deviceId=51777%2C89777&startTime=1700000000000&endTime=1700000000000
Base URLhttps://intouch.mapmyindia.com/iot/api
Authenticationbearer
Journey roleobserve
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
deviceIdrequired
querystring

id of the device(s) for which you want to fetch the geofence activities. For multiple devices, you can pass comma separated device ids as well in the query string.

51777,89777
geofenceId
querystring

id of the geofence(s) for which you want to fetch the geofence activities done by the device. For multiple geofences, you can pass comma separated geofence ids as well in the query string.

4543,8787
startTimerequired
querynumber

Value in timestamp. Start time from where you want to fetch the geofence activities

1700000000000
endTimerequired
querynumber

Value in timestamp. End time till where you want to fetch the geofence activities.

1700000000000
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
GETRequest inputs
4 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://intouch.mapmyindia.com/iot/api/geofences/activities?deviceId=51777%2C89777&geofenceId=4543%2C8787&startTime=1700000000000&endTime=1700000000000
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/geofences/activities?deviceId=51777%2C89777&geofenceId=4543%2C8787&startTime=1700000000000&endTime=1700000000000' \
  --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 /geofences/activities
curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/geofences/activities?deviceId=51777%2C89777&startTime=1700000000000&endTime=1700000000000' \
  --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[].entryLongitude
number

longitude where the particular device entered the geofence.

77.229463
data[].entryLatitude
number

latitude where the particular device entered the geofence.

28.612964
data[].exitLongitude
number

longitude where the particular device exited the geofence.

77.229463
data[].exitLatitude
number

latitude where the particular device exited the geofence.

28.612964
data[].entryTimestamp
number

time at which the device entered the particular geofence.

1700000000000
data[].exitTimestamp
number

time at which the device exited the particular geofence.

1700000000000
data[].geofenceName
string

name of the geofence

my geofence
data[].geofenceId
number

the id of the geofence where the activity took place

767676
data[].deviceId
number

the id of the device which is performing the activities w.r.t the geofence

87676
Response example
{
  "data": [
    {
      "entryLongitude": 28.8765,
      "entryLatitude": 56.8765,
      "exitLongitude": 38.8765,
      "exitLatitude": 46.8765,
      "entryTimestamp": 1580105880,
      "exitTimestamp": 1580105880,
      "geofenceName": "my geofence",
      "geofenceId": 767676
    }
  ]
}
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/geofence.json
SHA-256
fc26724559038e8d114001105966c2bd30e35ac4f8c0a1644d9241eb4bd64425
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.