Can HumDay connect to HERE Tracking?

Yes. HumDay reads HERE Tracking's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 205 operations are documented.

Do I need to write code to automate HERE Tracking?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your HERE Tracking account.

What can HumDay do in HERE Tracking?

93 of the 205 documented operations change something in HERE Tracking, and 112 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my HERE Tracking account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to HERE Tracking is held behind that approval.

Automate HERE Tracking

HumDay reads HERE Tracking’s own published API description and derives 205 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What HERE Tracking is

HERE Tracking is a cloud product designed to address location tracking problems for a wide range of Location IoT industry verticals. HERE Tracking also includes end-user mobile and web applications that can be used to demonstrate the product.

API host: tracking.api.here.com

What HumDay can do in HERE Tracking

93 documented operations change something in HERE Tracking. The 57 most useful are listed here.

POSTCreates a new data upload/largedata/v4
POSTGets a user access token/users/v2/login
POSTGets a renewed user access token/users/v2/refresh
POSTGets a project-scoped user access token/users/v2/tokenExchange
POSTCreates a rule/rules/v4
POSTCreates a sensor rule/sensors/v3
POSTCreates a geofence/geofences/v2
POSTCreates a location/locations/v4
POSTCreates a shipment/shipments/v4
PUTUpdates a notification channel/notifications/v3/registration/{channelId}
POSTCreates a connector/c2c/v4/connectors
POSTCreates a shipment plan/shipments/v4/plans
POSTIngests data and receives a shadow/v2/
POSTIngests data for a device and receives a shadow/v3/
POSTStarts bulk upload/bulkjobs/v4/deviceUploads
POSTCompletes data upload/largedata/v4/{dataId}
DELETEDeletes all the device traces and events/traces/v2/{trackingId}
DELETEDeletes all rules/rules/v4
POSTRequests a token for a registered device/v2/token
POSTIngests data for multiple devices/v3/batch
POSTStarts report creation/reports/v4
DELETEDeletes all sensor rules/sensors/v3
DELETEDeletes all geofences/geofences/v2
DELETEDeletes all locations/locations/v4
DELETEDeletes all shipments/shipments/v4
POSTStarts shipment report generation/shipment-reports/v4
POSTCreates licenses for multiple devices/registry/v2/{appId}/devices
PUTCreates multiple aliases for a device/aliases/v2/{trackingId}/batch
POSTCreates a license for a single physical device/registry/v2/{appId}/one-device
PUTCreates or updates metadata of a device or a shipment/metadata/v2/devices/{trackingId}
PATCHUpdates bulk upload job status/bulkjobs/v4/deviceUploads/{jobId}
PUTCreates or updates metadata of a geofence/metadata/v2/geofences/{geofenceId}
PUTCreates or updates metadata of a sensor rule/metadata/v2/sensorRules/{sensorRuleId}
POSTReceives external device update reports/c2c/v4/callback
POSTGets a batch of device shadows/shadows/v2/batch
DELETEDeletes all shipment plans/shipments/v4/plans
POSTChecks if a POI geofence training is possible with the given parameters/geofences/v2/trainingTest
DELETEUnregisters from all notifications/notifications/v3/registrations
POSTRegisters for notifications/notifications/v3/registrations
DELETEDeletes a rule/rules/v4/{ruleId}
PUTUpdates a single rule/rules/v4/{ruleId}
DELETEDeletes large data/largedata/v4/{dataId}
DELETEDeletes all aliases of a device/aliases/v2/{trackingId}
POSTAdds external devices to a connector/c2c/v4/connectors/{connectorId}/ext-devices
DELETEClears a device shadow/shadows/v2/{trackingId}
PUTUpdates a device shadow/shadows/v2/{trackingId}
DELETEUnclaims a device/registry/v2/{trackingId}
DELETEDeletes a geofence/geofences/v2/{geofenceId}
PUTUpdates a single geofence/geofences/v2/{geofenceId}
DELETEDeletes a location/locations/v4/{locationId}
PUTUpdates a location details/locations/v4/{locationId}
DELETEDeletes a sensor rule/sensors/v3/{sensorRuleId}
PUTUpdates a single sensor rule/sensors/v3/{sensorRuleId}
DELETEDeletes a shipment/shipments/v4/{shipmentId}
PATCHUpdates a shipment details/shipments/v4/{shipmentId}
POSTGets a batch of metadata of multiple devices or shipments/metadata/v2/devices/batch
POSTGets a batch of metadata of multiple geofences/metadata/v2/geofences/batch

What HumDay can read from HERE Tracking

These are the operations a schedule or a trigger can watch.

GETGets event history/events/v3
GETGets the event statuses/events/v3/statuses
GETGets a list user projects along with the license information/registry/v2/licenses
GETGets all registered notification channels/notifications/v3/registrations
GETGets event history for a device or a shipment/events/v3/{trackingId}
GETGets the number of devices and shipments in each event state/events/v3/statuses/deviceCounts
GETGets a list of drivers/c2c/v4/drivers
GETGets service health/users/v2/health
GETGets service health/events/v3/health
GETGets a single notification channel information/notifications/v3/registration/{channelId}
GETGets all devices claimed by a project/users/v2/devices
GETGets service version/users/v2/version
GETGets a list of connectors/c2c/v4/connectors
GETGets service version/events/v3/version
GETGets the bulk upload job IDs for a project/bulkjobs/v4/deviceUploads
GETGets all rules/rules/v4
GETGets service health/v2/health
GETGets service health/v3/health
GETGets all aliases/aliases/v2
GETGets all sensor rules/sensors/v3
GETGets all shadows/shadows/v4
GETGets service version/v2/version
GETGets service version/v3/version
GETGets all geofences/geofences/v2
GETGets all locations/locations/v4
GETGets all shipments/shipments/v4
GETGets the current timestamp/v2/timestamp
GETLists all the devices provisioned by a user/registry/v2/{appId}/devices
GETGets a number of device licenses provisioned by a user/registry/v2/{appId}/licenseCount
GETGets service health/c2c/v4/health
GETGets service version/c2c/v4/version
GETGets service health/rules/v4/health
GETGets service health/labels/v4/health
GETGets service version/rules/v4/version
GETGets service health/traces/v2/health
GETGets service health/aliases/v2/health
GETGets service version/labels/v4/version
GETGets service health/reports/v4/health
GETGets service health/sensors/v3/health
GETGets service health/shadows/v2/health
GETGets service version/traces/v2/version
GETGets service version/aliases/v2/version
GETGets service health/bulkjobs/v4/health

How automating HERE Tracking works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live HERE Tracking account.
Grant access, then go live. You approve the specific HERE Tracking operations it may use — and only those.

Popular HERE Tracking integrations

Connect HERE Tracking to the tools people pair it with most.