Core resource
Media
Attach public URLs directly, upload files, or use resumable multipart uploads for large assets.
4
Endpoint summary
All operations in this resource, with the minimum accepted key scope.
Method & endpointPurposeScope
POST
/api/mediaIngest a URL, file, or start multipart upload
publishGET
/api/media/{id}Inspect validation and probe state
readPOST
/api/media/{id}/completeComplete a multipart upload
publishDELETE
/api/media/{id}/uploadAbort a pending multipart upload
publish01
Choose the simplest source
The create-post endpoint accepts media IDs, public HTTP(S) URLs, base64 data URLs, and multipart files. Use a media ID when the asset is large, reused, or needs validation before a scheduled publish.
02
Ingest a public URL
PostGate fetches the source asynchronously, detects its true MIME type, probes dimensions and duration, and prepares provider renditions.
Create media from URLPostGate API
curl -X POST https://postgate.studio/api/media \
-H "Authorization: Bearer $POSTGATE_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "https://cdn.example.com/demo.mp4", "filename": "demo.mp4" }'03
Use multipart for large files
Create an upload reservation with filename, MIME type, and byte count. Upload every part to its signed URL, then send the returned ETags to the completion endpoint. Abort pending reservations you no longer need.
Start multipart uploadPostGate API
curl -X POST https://postgate.studio/api/media \
-H "Authorization: Bearer $POSTGATE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"source": "upload",
"filename": "campaign.mp4",
"mime": "video/mp4",
"bytes": 52428800
}'04
Wait for ready
Media moves through
pending, uploaded, processing, and ready. A failed asset includes structured evidence under error. Scheduled posts revalidate the asset again at delivery time.