Skip to content

Clear in-progress call-tracking rows (debug-only)

POST
/v1/ns/{nsid}/flush-call-status
curl --request POST \
--url https://example.com/v1/ns/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/flush-call-status \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "call": "example" }'

Clears the in-progress call-tracking rows (live_calls, live_call_detail, and active-call counters) for the namespace. The call field is either a single call ULID or the literal "all".

Debug-only: these rows normally TTL out on their own. Use this to clear a known-stuck call that would otherwise block cascade delete until the TTL expires — it is not a day-to-day operation. A single-ULID flush does not adjust the active-call counters (the counter sweeper reconciles them); "all" clears them outright.

nsid
required
string format: uuid

Namespace UUID

Media typeapplication/json
object
call
required

A call ULID, or the literal “all”.

string
Examplegenerated
{
"call": "example"
}

Rows flushed

Media typeapplication/json
object
success
required
boolean
nsid
required
string
target
required

The requested target (“all” or a call ULID).

string
flushed
required

Best-effort count of calls flushed (1 for a single ULID; 0 for “all”).

integer
Examplegenerated
{
"success": true,
"nsid": "example",
"target": "example",
"flushed": 1
}

Error response

Media typeapplication/problem+json

RFC 7807 Problem Details

object
type

Problem type slug URI

string
title
string
status
integer
detail
string
key
additional properties
any
Examplegenerated
{
"type": "example",
"title": "example",
"status": 1,
"detail": "example"
}