Meeting BaaSMeeting BaaS
Meeting BaaS API v2Typescript SDKMCP ServersSpeaking BotsSelf HostingBring Your Own StorageMeeting BaaS API v1 (legacy)

API v2/POST

Retry callback

Retry sending the transcription callback for a bot.

You can override the callback configuration (URL, method, secret) if needed. Only works for bots that have completed or failed. The callback will be sent to the provided URL (or the bot's original callback URL if not overridden).

Callback Configuration: You can override the callback URL, HTTP method (POST or PUT), and secret in the request body. If not provided, the bot's original callback configuration will be used. The secret will be included in the x-mb-secret header for validation.

Status Requirements: The bot must be in completed or failed status and must have had transcription enabled. Bots without transcription or bots that are still in progress cannot have their callback retried. If the bot is in an invalid state, the request will fail with a 409 Conflict status.

Callback Payload: The callback payload will be identical to the original callback (either bot.completed or bot.failed event with transcription data). The payload format matches the webhook format.

Use Cases:

  • Callback delivery failed due to network issues
  • Callback endpoint was temporarily unavailable
  • Need to send callback to a different endpoint
  • Testing callback integration

Idempotency: This operation is idempotent. You can call it multiple times with the same or different configurations.

Returns 404 if the bot is not found, or 409 if the bot's status does not allow this operation or if no callback was configured.

POST
/v2/bots/{bot_id}/retry-callback

Authorization

ApiKeyAuth
x-meeting-baas-api-key<token>

Your Meeting BaaS API key. Get one from your account settings.

In: header

Path Parameters

bot_id*string

The UUID of the bot to retry the callback for.

This will recreate and resend the callback payload to the configured callback URL (or a custom URL if provided in the request body).

Match^([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)$
Formatuuid

Request Body

application/json

method?string

The HTTP method to use for the callback. Allowed values are 'POST' or 'PUT'.

Default"POST"
Value in"POST" | "PUT"
secret?|

To ensure that you can validate the callback, this secret will be added to the request in the 'x-mb-secret' header

Defaultnull
url*string

The URL to be called upon the completion or failure of the bot.

Formaturi

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://api.meetingbaas.com/v2/bots/497f6eca-6276-4993-bfeb-53cbbbba6f08/retry-callback"
{
  "data": {
    "message": "string"
  },
  "success": true
}
{
  "code": "string",
  "error": "string",
  "message": "string",
  "statusCode": 9007199254740991,
  "success": false
}
{
  "code": "string",
  "details": "string",
  "error": "string",
  "message": "string",
  "statusCode": 9007199254740991,
  "success": false
}
{
  "code": "string",
  "details": "string",
  "error": "string",
  "message": "string",
  "statusCode": 9007199254740991,
  "success": false
}
{
  "code": "string",
  "details": "string",
  "error": "string",
  "message": "string",
  "retryAfter": 9007199254740991,
  "statusCode": 9007199254740991,
  "success": false
}
{
  "code": "string",
  "details": "string",
  "error": "string",
  "message": "string",
  "statusCode": 9007199254740991,
  "success": false
}
Edit on GitHub