Reo.dev Write API: Reo Write Add Telemetry Aggregate

Send a pre-counted product telemetry total for an IP or domain to Reo.dev.

Tool ID: reo_write_add_telemetry_aggregate

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_aggregate',
  {
    "payload": {
      "mode": "DOMAIN",
      "source": "TELEMETRY",
      "activity_type": "example",
      "count": 123,
      "event_at": 123,
      "product_id": "product_123"
    }
  },
);

console.log(result.toolResponse.raw);

CLI

deepline run reo_write_add_telemetry_aggregate --input '{
  "payload": {
    "mode": "DOMAIN",
    "source": "TELEMETRY",
    "activity_type": "example",
    "count": 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_aggregate --json for the latest machine-readable contract.

Input reference

Overview Sends a pre-aggregated usage count (e.g. 1,250 events) for one IP or domain. There’s no user ID, so Reo maps usage at the domain level and then to the company. Use this for anonymous telemetry where you only have counts. ### Path Parameters None. ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | API key wrong or missing | `{"response_code":400,"response":"Authentication Failure","status":"failure"}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | mode | `DOMAIN` | Count is for a whole IP or domain. Reo maps it to the Account | | source | `TELEMETRY` | Telemetry event data | ### Things to Note - Use Single Events when you send one event at a time. Use this API when you only have pre-counted totals. - Only `DOMAIN` mode is supported for telemetry. `USER` mode is for Add Custom Product Data only. - There are no `user_id` or `user_id_type` 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