Authentication
Owners and admins create API keys in Settings. The complete secret appears once. ClipPush stores only its hash.
curl -H "Authorization: Bearer $CLIPPUSH_API_KEY" \
https://clippush.app/api/v1/meFirst upload
- 01
Reserve the upload
POST the filename, content type and byte size to /uploads with an Idempotency-Key header. - 02
Transfer the file
Upload the video to the short-lived URL returned by ClipPush. - 03
Finalise the upload
GET the upload resource so ClipPush can verify the transferred file and return its current state. - 04
Create the release
POST the upload ID, publish mode, copy and connected destination IDs to /posts.
curl -X POST https://clippush.app/api/v1/uploads \
-H "Authorization: Bearer $CLIPPUSH_API_KEY" \
-H "Idempotency-Key: 7e97b64d-39b4-4b54-b44d-a1c61f23fd75" \
-H "Content-Type: application/json" \
-d '{"filename":"clip.mp4","content_type":"video/mp4","size_bytes":123456}'Endpoints
| GET /me | Confirm workspace, scopes, plan and quota |
|---|---|
| GET /connections | List connected social accounts |
| POST /uploads | Reserve a secure video upload |
| GET /uploads/{id} | Finalise and inspect an upload |
| POST /posts | Create a draft, scheduled or immediate post |
| GET /posts | List posts with cursor pagination |
| GET /posts/{id} | Read one post and its delivery jobs |
| PATCH /posts/{id} | Edit or reschedule an unpublished post |
| DELETE /posts/{id} | Cancel a draft or scheduled post |
Download the OpenAPI 3.1 document for request schemas and response details.
Conventions and limits
- Fields use
snake_case. IDs are UUIDs and timestamps are ISO 8601 with a timezone. - List responses use cursor pagination through
pagination.next_cursor. - Errors return
{ status, code, message, details? }. Switch on the code, not the message. - Keys are rate limited to 60 calls per minute and have plan-based monthly quotas.
- Creation requests retain idempotency results for 24 hours. The same key with a different body returns 409.