The Trabbly Social API
What the public API can do (read brands, posts, media and analytics, upload media, create drafts), who can use it and where the full reference is.
The Trabbly Social API lets your own tools read brands, posts, media and analytics, upload media and create drafts that go through your usual approvals. It is part of the Enterprise plan. Owners and admins create the tokens it uses.
The full developer guide, with examples you can copy, is in the app at Settings, API access, Developer guide. This article is a summary.
What it can and can't do
| It can | It never |
|---|---|
| List brands and their connected accounts | Approves a post |
| Read posts, each platform version, its status and approvals | Schedules a post |
| Create drafts and send them for review | Publishes a post |
| List, read and upload media | Changes connections, team or billing |
| Read analytics summaries, with the same numbers as the Analytics page |
A draft you create with intended_at is scheduled for that time only once it is approved and publishing is verified for the platform. The same checks as the composer apply: caption length per platform, media rules and platform settings.
Endpoints
All addresses start with your API address, shown under Settings, API access, For developers.
| Method and address | What it does |
|---|---|
| GET /me | This token, its organisation and brands |
| GET /brands | Brands |
| GET /brands/{id}/accounts | A brand's connected social accounts |
| GET /posts | Posts, newest first (filter by brand, status, platform, creation time; cursor paging) |
| GET /posts/{id} | One post |
| POST /brands/{id}/posts | Create a draft (optionally submit it for review) |
| GET /brands/{id}/media | A brand's media (cursor paging) |
| POST /brands/{id}/media | Upload a file in one request |
| POST /brands/{id}/media/uploads, PUT /media/uploads/{id}/chunks/{n}, POST /media/uploads/{id}/complete | Upload a large file in parts (4 MB each) |
| GET /media/{id} | One media item |
| GET /brands/{id}/analytics | Analytics summary for a period, compared with the period before |
Requests and answers are JSON, and times are in UTC (ISO 8601). Lists are paged with a cursor: when has_more is true, ask again with cursor set to the next_cursor you received. Uploads take JPEG, PNG, WebP and GIF images up to 30 MB, and MP4 and MOV videos up to 1 GB.
The complete reference, with every field, is the OpenAPI 3.1 file linked as OpenAPI file on the API access page. Most API tools (Postman, Insomnia, code generators) can import it.
Errors
Errors are JSON with a code for your code and a message for people.
| Status | Codes | Meaning |
|---|---|---|
| 401 | missing_token, invalid_token, token_revoked, token_expired, token_inactive |
No token, or it isn't recognised, was revoked, has expired, or stopped because its creator left or is no longer an owner or admin |
| 403 | insufficient_scope, forbidden, module_unavailable |
The token lacks the permission, its creator's role doesn't allow it, or the plan doesn't include the API |
| 404 | Not found, or this token can't see it | |
| 422 | Some fields aren't valid; errors lists them by field |
|
| 429 | Too many requests; wait for the seconds in Retry-After |
Rate limits
Each token can make a set number of requests a minute (120 by default; For developers on the API access page shows the current limit). Every answer carries X-RateLimit-Limit and X-RateLimit-Remaining.
Next steps
Was this article helpful?