​

Inspect API payloads in Request Logs

​

Access and roles

​

Reading the table

• Timestamp — rendered in your own timezone.
• Method — GET, POST, PUT, PATCH, DELETE, color-coded (green GET → cyan POST → amber PUT/PATCH → red DELETE).
• Path — the route that was called.
• Status — the HTTP status code; 2xx green, 3xx cyan, 4xx amber, 5xx red.
• Latency — end-to-end request time in milliseconds.
• API key — the key that authenticated the call, masked.
• Size — response payload size.

​

Filtering

• Method — one of GET, POST, PUT, PATCH, DELETE.
• Status — pick a class: 2xx, 3xx, 4xx, or 5xx.
• Path — free text, debounced; matches route fragments such as /messages.
• API key — match by key prefix (for example dv_test_…) to isolate one integration.
• Request ID — paste a full request id to jump straight to that one call.

​

Inspect a payload

​

Live tail, exports, and pagination

• Live tail — the toggle in the header opens a streaming connection and prepends every request to the top of the table as it completes, for live debugging. It caps at the 500 most recent rows. The same stream is consumable from your own tooling over SSE (the sample below); the full endpoint reference lives at Log-tail API reference.
• Export — downloads the current filtered result set as CSV (timestamp, method, path, status, latency, masked key, size). The export walks the whole result, not just the loaded page, up to a 100,000-row cap; the toast reports if the cap truncated the file.
• Pagination — the table pages 50 rows at a time; Load more appends a page under your active filters without a full reload.

​

Consuming the live-tail stream yourself

curl -N -H "X-API-Key: dv_live_sk_your_key_here" \
  -H "Accept: text/event-stream" \
  -H "Origin: https://orbit.devotel.io" \
  -H "User-Agent: Mozilla/5.0 (SSE tail)" \
  "https://api.orbit.devotel.io/api/v1/logs/tail"

// npm install eventsource — the credential travels in the X-API-Key
// header, never in a query string (URLs land in proxy and access logs).
import { EventSource } from "eventsource";

const source = new EventSource("https://api.orbit.devotel.io/api/v1/logs/tail", {
  headers: { "X-API-Key": process.env.ORBIT_API_KEY },
});

source.addEventListener("log", (event) => {
  console.log(JSON.parse(event.data));
});

curl -N "https://api.orbit.devotel.io/api/v1/logs/tail?token=dv_live_sk_your_key_here"

// EventSource cannot set headers on browsers, so the credential travels
// as the token query parameter (a dv_ value; anything else is a JWT).
const source = new EventSource(
  `https://api.orbit.devotel.io/api/v1/logs/tail?token=${token}`,
  { withCredentials: true },
);

interface LogRow {
  method: string;
  path_pattern: string;
  status_code: number;
  duration_ms: number;
}

source.addEventListener("log", (event) => {
  const row = JSON.parse(event.data) as LogRow;
  if (row.status_code >= 400) {
    console.log(`${row.method} ${row.path_pattern} → ${row.status_code} (${row.duration_ms}ms)`);
  }
});

​

Where this page fits against other surfaces

• This page (Request Logs) — historical request inspection with full payloads, up to a year back.
• Live tail toggle / GET /logs/tail — the in-flight request stream, for live debugging only.
• Events firehose — a bounded, in-memory buffer of workspace events (message sent, agent run, contact updated) with about a 15-minute TTL. Not durable, not an audit log.
• Audit log — the durable trail of configuration changes (who changed what setting, when). It records actions, not request payloads.
• Delivery Logs — the downstream lifecycle of a message after the API accepted it.

​

Retention

​

When a key is no longer trusted

​

When the answer is an error code

• error.code — the machine-readable string the runbooks index on. Paste it into the Error Code Reference or ask the Troubleshooting hub how to classify it (pre-send gate, transient, deterministic validation).
• error.details — the field-level hint (which input failed, what it expected). For tenant-owned pre-send rejects this is where the fix lives.
• meta.docs_url — a redirect to /errors/<CODE>, which resolves to the per-code anchor on the Error Code Reference page. Use it when you would rather land there directly.

​

Frequently asked questions

​

The table is empty, but I know I made API calls

​

Why does the Avg Latency card show an em-dash?

​

Can I hand teammates a pre-filtered view?

​

See also

• API playground — build and run requests against the API from the dashboard, with generated curl/SDK code
• Developer Portal guide — try-it console, usage stats, key governance, webhook debugging
• Delivery Logs console — the downstream message lifecycle
• Log-tail API reference — consume the live request stream over SSE
• Operator observability map — which surface answers which question
• Per-domain data retention policy — scheduled purge windows you control
• Audit log — the durable configuration-change trail