Skip to main content
Version: 2.0.0

TagoIO API

This page explains how to authenticate to the TagoIO API and which regional base URL to use. All HTTP requests must include exactly one valid token in the headers and must target the correct regional endpoint.

Authentication​

TagoIO uses token-based authentication. Include one (and only one) of the supported tokens in your HTTP headers depending on the scope of your request.

  • Device-Token: Use for device-scoped operations, such as sending or reading a device’s data. See the Device Token guide in Device-Token.
  • Profile-Token: Use for profile-level management (create devices, dashboards, users, etc.). See Profile-Token.
  • Network-Token: Use for custom Network Integrations when sending data via a Network. See Creating a Network Integration.

You should add the token to the request header using the token’s specific header key, or the generic Authorization header as documented in the API overview. For a broader discussion of token types and header usage, consult the API Overview.

Send exactly one of the headers below with every request.

Use for device data and device-scoped operations. Create it on the Device page.

curl -H "Device-Token: <your-device-token>" \
  https://api.us-e1.tago.io/status
info

Rate limits apply to all API requests. Plan accordingly and handle pagination/limits. See Rate Limits / Usage Policy.

Setting the API Endpoint Region​

Choose the API base URL based on your TagoIO account's region. Replace <region> in the base URL with your region.

  • United States East 1: https://api.us-e1.tago.io/
  • Europe West 1: https://api.eu-w1.tago.io/

Use the following pattern to construct your endpoint URLs based on the selected region:

https://api.<region>.tago.io/<path>

Examples:

  • Create a device (Profile-Token):
    POST https://api.us-e1.tago.io/device

  • Read device data (Device-Token):
    GET https://api.eu-w1.tago.io/data?variable=temperature&qty=100