Report a finished meeting recording for metering [write]

Changed on

Books one charge for one recording, on the two bases the supplier charges us on. bot_seconds is how long the recorder held a seat — first to last status change, including time spent waiting to be admitted — billed at $1.00 per hour. recorded_seconds is what was actually captured, capture start to capture end, billed at $0.30 per hour; it is not a bot lifetime and not a running total for the meeting. Neither basis is derived from the other and both are required. The 60-second minimum applies to each basis separately, not to their sum. A report naming error_code zeroes the transcription basis but still owes the seat, because the supplier still charged for it; only a booking where neither basis ran costs nothing. The reporting account is the account charged. A recording is identified by meeting_id and bot_id together: reporting it again returns the booked terms with 200 and charges nothing further.

post/meeting-recordings

Request

  • Base URL
    https://api.agentsky.dev/v1
  • URL
    https://api.agentsky.dev/v1/meeting-recordings
  • Auth
    none declared

Request body

meeting_idstring required

The meeting, in the reporter's own namespace

bot_idstring required

The recorder instance that produced this recording

bot_secondsnumber required

Seconds the recorder held a seat, the wait included — the basis the seat charge bills on. 0 means it never ran. Over 86400 is refused rather than truncated

recorded_secondsnumber required

Seconds actually captured — the only basis transcription bills on. Not a bot lifetime; bot_seconds is that. Over 86400 is refused rather than truncated

error_codestring

Why this recording is not billable. Its presence alone forces a $0 receipt

session_idstring

A session to attribute the charge to; omit when the reporter has no session

Response

Already reported; the booked terms, unchanged

Changes