Skip to main content

Requests and pagination

Base URL​

https://api.socialchamp.com/v1/rest

Send your token in Authorization: Bearer YOUR_TOKEN. For JSON bodies, also send Content-Type: application/json.

Dates and IDs​

Use an ISO 8601 timestamp with a timezone, such as 2030-01-15T10:00:00Z. Z means UTC. For scheduling, choose a future time.

Use IDs returned by the API. A channel is a connected social account; a workspace groups channels and content. Do not substitute an account ID for a channel ID.

Read another page of posts​

GET /v1/rest/posts?limit=25

Example response:

{
  "data": [],
  "paging": {"nextCursor": null, "hasMore": false}
}

If paging.hasMore is true, send the returned paging.nextCursor as the next request's cursor parameter. Keep the same filters. Treat the cursor as an opaque value: URL-encode it, but do not edit it.

Post lists default to 25 items and accept a limit from 1 to 100. Approval lists use start and limit instead; their limit is 1–50. Other lists do not all support pagination. Check the endpoint's parameters.

Send deletion filters in the body​

DELETE /posts, DELETE /queue, and DELETE /posts/{postId}/labels read a JSON body. Query-string filters are not used by these operations. See Preview and delete posts.

Retry carefully​

The public REST API does not provide an Idempotency-Key guarantee. Repeating a create request can create another post, even when you send the same key.

After a timeout or partial failure, check the response and your scheduled posts before retrying. See Responses and retries.

Last updated on