Get a WhatsApp message's media
Redirects to a short-lived URL for the media on a received WhatsApp message, or on one from the WhatsApp Business app on a number shared with it: sent from the app (origin: business_app_echo) or imported from its chat history (origin: history_sync). That media is stored because WhatsApp's own URL is not fetchable without our credentials; this endpoint is what the url on the message's image, video, audio, sticker or document points at. The bytes live in object storage and are served straight from there, so they never transit the API.
The response is a 302 whose Location is that pre-authorized storage URL, valid for 15 minutes; your client must follow redirects. The Authorization header must be absent from the request that fetches that URL: a client that attaches credentials centrally, at its transport, interceptor or middleware layer rather than per request, re-adds the header on every hop including the redirect, so the storage URL must be fetched with a client that carries none.
Media is kept for 30 days after the message is received, and the message itself is kept longer. A message older than that still lists its media's mime_type and caption, and this operation returns 410 once the bytes have expired. Other outbound messages have no media to serve.
Request
- Base URL: https://us1.platform.bird.com
- URL: https://us1.platform.bird.com/v1/whatsapp/messages/{message_id}/media/{media_id}
- Auth: one of:
- HTTP bearer
- API key in cookie bird_session
Headers
Workspace context for the request. Required for dashboard authentication and master keys. Workspace keys and access tokens already identify their workspace; send that workspace or omit the header. A different one is rejected.
Organization context for the request. Required for dashboard authentication. An API key or access token carries its own organization, so send either that organization or no header at all; a different one is rejected.
Changes
No recorded changes to this operation across all 3 revisions of this API.