Emails

Request a send approval

Changed on

Holds a direct send, campaign send, or schedule for the account owner's approval in Migma and sends nothing. Migma checks the send as it would go out now and returns a summary with an approval link. The owner sends, schedules, or declines it on migma.ai; Migma checks it again then and refuses it if anything that decides who gets it, from whom, or when changed. Direct sends are marketing unless transactional is true, which is refused for tag and segment sends and needs a verified transactional sending identity. Requires API key with email:send (send_email) or campaign:write (campaign actions).

post/v1/send-approvals

Request

  • Base URL
    https://api.migma.ai
  • URL
    https://api.migma.ai/v1/send-approvals
  • Auth
    API key in header Authorization

Headers

Idempotency-Keystring

Optional key (max 100 chars) for safe retries. Same key + same body within 24h replays the original response (same status and body); same key + a different body returns 409 IDEMPOTENCY_CONFLICT. Scoped per API key.

Request body

OR
OR

Response

Approval created

successboolean required
errorstring nullable

Changes