Reo.dev Write API: Reo Write Add Telemetry Event

Send one product telemetry or call-home event, by IP or domain, to Reo.dev for a metric key configured in Reo.

Tool ID: reo_write_add_telemetry_event

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'reo_write_add_telemetry_event',
  {
    "payload": {
      "activity_type": "example",
      "source": "TELEMETRY",
      "event_id": "event_123",
      "event_at": 123,
      "product_id": "product_123"
    }
  },
);

console.log(result.toolResponse.raw);

CLI

deepline run reo_write_add_telemetry_event --input '{
  "payload": {
    "activity_type": "example",
    "source": "TELEMETRY",
    "event_id": "event_123",
    "event_at": 123,
    "product_id": "product_123"
  }
}'

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "response_code": "example",
    "response": "example",
    "status": "example"
  }
}

Use deepline describe reo_write_add_telemetry_event --json for the latest machine-readable contract.

Input reference

Overview Sends one product usage or call-home event to Reo. Reo resolves the IP or domain to a company and, if a user ID is sent, rolls usage up at the developer level before mapping it to their account. Events sent here show up in Get Account Activities and Get Developer Activities under the `PRODUCT_API` source. Use your Write API key (Settings → Configurations → API Keys → Product Usage API). Only Admins can see API keys. ### Path Parameters None. ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | API key wrong or missing | `{"response_code":400,"response":"Authentication Failure","status":"failure"}` | | 500 | Body not wrapped in a `payload` object | `{"timestamp":"...","status":500,"error":"Internal Server Error","path":"/api/product/usage"}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | source | `TELEMETRY` | Telemetry or call-home See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.payload`	`object`	Yes	—	Wrapper object. Every field sits inside it.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.response_code`	`string`	No	—	Status code, as a string.
`result.data.response`	`string`	No	—	Result message.
`result.data.status`	`string`	No	—	`success` or `failure`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation