canonical: https://jentic.com/apis/thinger.io/thinger

# Thinger.io HTTP Devices API

API for sending data from HTTP devices to the Thinger.io IoT platform via device callbacks. The API exposes 1 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically send device callback data. Covers 1 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for iot and hardware only.

## Capabilities

- Send device callback data
- Manage iot data programmatically
- Integrate Thinger.io HTTP Devices API into automated workflows
- Query and filter Thinger.io HTTP Devices API records by parameters
- Monitor Thinger.io HTTP Devices API operational status and events

## Use cases

### IoT and Hardware Operations

Use the Thinger.io HTTP Devices API to perform iot operations programmatically. The API provides 1 endpoints covering core functionality including send device callback data.

Example prompt: Call POST `/users/{username}/devices/{deviceId}/callback/data` to send device callback data

### Data Retrieval and Monitoring

Query Thinger.io HTTP Devices API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Thinger.io HTTP Devices API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Thinger.io HTTP Devices API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'send device callback data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/users/{username}/devices/{deviceId}/callback/data` | Send device callback data |

## Key resources

- **Device Callback** — HTTP device callback endpoints for sending data to the platform

## Why Jentic

- **Setup:** Wiring the Thinger.io HTTP Devices API by hand means choosing between the JWT bearer header and the authorization query token, pointing at the right {server} host, and handling your own retries. Through Jentic you install once, import the Thinger.io HTTP Devices API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Thinger.io HTTP Devices API puts the username and device id in the URL path (`/users/{username}/devices/{deviceId}/callback/data`), so a rule can pin your agent to one device: it can send callback data for that device and nothing else. Every operation you credit it with stays inside that allowed set.
- **Credential handling:** Your Thinger.io token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send data from a device', and Jentic returns the matching Thinger.io operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Particle** — Alternative iot API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the Thinger.io HTTP Devices API use?

The Thinger.io HTTP Devices API uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I send device callback data with the Thinger.io HTTP Devices API?

Yes. Use the POST `/users/{username}/devices/{deviceId}/callback/data` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Thinger.io HTTP Devices API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I send device callback data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send device callback data'. Jentic returns the matching Thinger.io HTTP Devices API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Thinger.io HTTP Devices API have?

The Thinger.io HTTP Devices API exposes 1 endpoints covering device callback operations.

### Can I limit what my agent is allowed to do with the Thinger.io HTTP Devices API?

Yes. Because you run Jentic One self-hosted, your own rules decide which operations and credentials the agent may use. This API puts the username and device id directly in the path (POST `/users/{username}/devices/{deviceId}/callback/data`), so you can pin your agent to a single device and let it send callback data for that device and nothing else. Any operation you do not credit it with stays out of reach, and the stored token is injected only for the calls you have allowed.