Skip to main content
POST
Approve a meeting held for compliance review
Release the results of a meeting held for compliance review. When your organization holds results for review, a meeting’s summary and transcript are produced as usual but stay hidden from its owner, and no result email is sent, until a compliance viewer approves it. Approving releases them: the owner can see the summary and transcript, and the result email is sent. Use the booking UUID returned by the Meeting Agent API, not the meeting provider’s join ID. No request body is required for an organization API key.
The response confirms the approval was recorded. The result email is sent after the response, so it may arrive a short time later. A held meeting has review_status pending from the moment its recording starts. It can be approved once its recording has finished, that is, when its status is success. To list the meetings waiting for a decision, filter on both: GET /v1/meetings?status=success&review_status=pending. The user associated with your API key must have compliance-viewer access in the meeting owner’s organization, otherwise the request returns 403 MEETING_REVIEW_NOT_PERMITTED. A compliance viewer may approve their own meeting. Unknown meetings and meetings outside your organization return 404 MEETING_NOT_FOUND. A meeting that is not waiting for a decision returns 409 MEETING_NOT_REVIEWABLE: it was rejected, its results were already released, its recording has not finished successfully, or its content is past its retention period. Repeating an approval never sends the result email twice. If the response is lost, or the API returns 503 MEETING_REVIEW_UNAVAILABLE or 502 MEETING_REVIEW_FAIL, fetch the meeting using GET /v1/meetings/{meeting_id} before retrying. If its review_status is already approved, no further request is needed. Organization rate limits also apply (429). For platform API keys, supply the same organization_id, user_id, and user_email identity selectors used when booking, as query parameters. user_id is your external customer user identifier, not LinqAlpha’s internal user UUID.

Authorizations

X-API-KEY
string
header
required

Path Parameters

meeting_id
string<uuid>
required

Booking UUID returned by the Meeting Agent API, not the provider join ID.

Query Parameters

organization_id
string

Platform keys: organization selected when booking.

user_id
string

Platform keys: external customer user identifier selected when booking (not an internal UUID).

user_email
string

Platform keys: email for the selected customer user.

Response

Approval recorded; the results are being released.

error
any | null
required

Null on success.

payload
object
required