API Reference
Using the API
A small REST surface over one workspace: accounts, posts, post stats and comments. JSON in, JSON out, bearer token on every call.
Base URL
text
https://app.echoia.io/api/v1Endpoints
| Method | Path | Scope |
|---|---|---|
GET | /accounts | read |
GET | /posts | read |
POST | /posts | write |
GET | /posts/{id}/stats | read |
GET | /comments | read |
POST | /comments/reply | engage |
Conventions
- Send
Content-Type: application/jsonon every write. - Timestamps are ISO 8601 in UTC, both in and out.
- List endpoints take
limit, clamped to 50. Asking for more is not an error, you simply get 50. - Every response is an object — never a bare array — so fields can be added without breaking clients.
Everything is workspace-scoped
Ids from another workspace return
404. No endpoint accepts a workspace parameter; the token decides.Platform identifiers
Wherever a platform is named, it is one of these lowercase strings:
text
instagram facebook youtube linkedin x
tiktok threads bluesky pinterest google_businessVersioning
The version lives in the path. Within v1 we add fields and endpoints but do not remove or repurpose existing ones — so treat unknown fields as forward compatible rather than as errors.
Accounts
List connected accounts and their follower counts.
Posts
Create drafts, schedule, publish, and list what exists.
Was this page helpful?