coldos
API key

The key never leaves your browser. Saved keys are stored in this browser's localStorage so paste-once-run-anywhere works across the portal.

POST/v1/callscalls:write

Log a manual call

Records a manually-dialed call. For Twilio-bridged outbound calls, the bridge writes the row server-side — you do not need to call this.

Run a request

POST/v1/calls

POSThttps://coldos.justgotwyrd.com/api/v1/calls

Paste an API key in the bar at the top of the page to enable Execute.

Parameters

Body parameters

  • contact_iduuidrequired

    Contact called.

  • directionstringrequired

    outbound / inbound.

    outboundinbound
  • outcomestringrequired

    Call outcome.

  • duration_secondsintegeroptional

    Talk time. Defaults to 0 if missed.

  • notesstringoptional

    Free-form operator notes.

  • occurred_atiso8601optional

    When the call happened. Defaults to `now()`.

Responses

  • 400Invalid request — see `error.message`.
  • 401Missing or invalid API key.
  • 403Authenticated, but the key lacks the required scope.
  • 404The referenced resource does not exist or is not visible to your key.
  • 429Rate limit exceeded — see `Retry-After`.
  • 500Unexpected server error. Safe to retry with idempotency-key.

Code samples

curl -X POST "https://coldos.justgotwyrd.com/api/v1/calls" \
  -H "Authorization: Bearer $COLD_OS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
      "contact_id": "c2a8a93a-2f1c-4c5b-8f3d-9c1e3a8b5d12",
      "direction": "outbound",
      "outcome": "connected",
      "duration_seconds": 134,
      "notes": "Confirmed Tuesday 4 PM IST."
    }'
Response · 200
{
  "id": "01HZS5K1M2N3P4Q5R6S7T8U9V0",
  "contact_id": "c2a8a93a-2f1c-4c5b-8f3d-9c1e3a8b5d12",
  "direction": "outbound",
  "to_number": "+919555516408",
  "from_number": "+18005551234",
  "outcome": "connected",
  "duration_seconds": 134,
  "notes": "Confirmed Tuesday 4 PM IST. Sending calendar invite.",
  "recording_url": null,
  "twilio_call_sid": "CA09a8b7c6d5e4f3a2b1c0d9e8f7a6b5c4",
  "occurred_at": "2026-05-01T15:42:00.000+05:30"
}

Was this page helpful?

Your vote stays in this browser. We'll use it to prioritise rewrites.