Errors

Errors use RFC 9457 problem details with the application/problem+json content type and a stable machine-readable code.

{
  "type": "https://meetingize.com/docs/api/errors#insufficient_scope",
  "title": "Insufficient scope",
  "status": 403,
  "detail": "This endpoint requires the scope 'read:transcripts'.",
  "instance": "/api/v1/meetings/1b9e.../transcript",
  "code": "insufficient_scope",
  "request_id": "req_5f0c..."
}

Validation errors add errors: [{"field": "...", "message": "..."}].

Error codes

HTTP	code	What to do
400	invalid_request, validation_error, invalid_cursor	fix the request (see errors)
401	missing_credentials, invalid_api_key, invalid_token, api_key_revoked, api_key_expired	check the credential
402	insufficient_balance, spend_cap_reached	add credits, enable on-demand or raise the cap (billing)
403	insufficient_scope, api_disabled	use a credential with the right scope
404	not_found	the object does not exist or belongs to another account
405	method_not_allowed
409	transcript_not_ready, summary_not_ready	retry later or wait for the webhook
409	idempotency_key_in_use	the first request with this key is still running
413	file_too_large	files are limited to 2 GB
415	unsupported_media_type	send JSON or multipart as documented
422	idempotency_key_reused, invalid_audio, unprocessable
429	rate_limited, parallel_processing_limit	wait (Retry-After) and retry, see limits
500	internal_error	retry with backoff, contact support with the request_id

Rate limits and quotas

Request rate limits per plan and the parallel processing quota are described on the limits page.

Retry advice

• Retry 429 and 5xx with exponential backoff (for example 1 s, 2 s, 4 s… up to 1 minute), honoring Retry-After.
• Always send an Idempotency-Key on POST so retries are safe.
• Do not retry other 4xx without changing the request.