Skip to main content
POST
Finish your wrap-up for a closed phone session
This action ends the authenticated teammate’s wrap-up only when it belongs to the supplied closed phone session. It does not close the session, save a code, hang up a call, or turn an unavailable agent online. An approved mini app can save the wrap-up code, close the session through Update a session, confirm that closure succeeded, and then call finishSessionWrapUp with the same session_id. If closure fails, keep the wrap-up active and let the teammate retry.
  • Requires agent-availability:write and a token bound to the acting teammate. A plain organization API key has no teammate identity and returns 403.
  • cleared: true means the matching wrap-up was cleared and the dashboard was notified.
  • cleared: false means no matching wrap-up was cleared: it may already have finished, belong to another session, or the supplied session may still be open. Do not interpret this as proof that the agent is available.
  • Repeated requests are safe. The call’s wrap-up identity is retained so a delayed call-end event does not reopen the same wrap-up window.
New calls still require the teammate’s normal availability, team eligibility, and calling connection. The existing I’m ready button continues to work independently.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
session_id
string<uuid>
required
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$

Response

Default Response

cleared
boolean
required