Developers

API and webhooks.

A REST API for programmatic control of your ManageSM workspace, and webhooks for events you care about — that's the plan. Here's where things stand today.

Public API is not yet available. The core is designed to be API-first (every UI action goes through the same DAL that will back the API), but we haven't opened public endpoints yet. If you're a developer who needs one now, tell us your use case and we'll prioritise the endpoints you need first.

What's planned

REST API (v1)

RESTful endpoints scoped to a workspace. Bearer-token authentication (per-user or per-workspace tokens). JSON in, JSON out. Versioned via a URL prefix (/api/v1/...).

Planned resources:

/api/v1/workspaces — read your workspaces
/api/v1/brands — CRUD on brands
/api/v1/accounts — read connected social accounts, initiate reconnection
/api/v1/content — create and update drafts
/api/v1/schedule — schedule and reschedule posts
/api/v1/publish — publish immediately (respects approval rules)
/api/v1/metrics — pull engagement metrics for your published posts
/api/v1/media — upload assets to the media library
/api/v1/activity — query the workspace activity log

Webhooks

POST notifications to a URL you configure when a subscribed event happens. Signed with an HMAC-SHA256 header so you can verify authenticity. Automatic retry with exponential backoff on non-2xx responses. Delivery attempts logged for 30 days.

Planned events:

post.published — a scheduled post went live
post.failed — a scheduled post failed after all retries
approval.requested — a post entered your approval queue
approval.granted, approval.rejected
account.token_expired — an OAuth token needs reconnection
metric.updated — engagement numbers refreshed for a post

Zapier and Make

Both are on the list once the REST API opens. Community integrations welcome — we'll credit them in the docs.

What's available today

Two endpoints are already open, both internal:

GET /api/health — returns 200 OK with a small JSON body for uptime monitoring. Live on every deployment.
POST /api/cron/publish — internal cron endpoint that runs the publish sweep every 60 seconds. Requires a shared secret; not for external use.

Both are documented for completeness — neither is a substitute for a real integration API.

Timeline

The public API is planned for the release after the app-side redesign lands. Order of endpoints will be driven by real customer requests — if you need /publish before /schedule, we'll ship it in that order.

If you're building something integration-heavy on top of ManageSM, tell us now so we can factor it into the design.

Sign up for early access

Your use case — what would the API let you do that the UI doesn't?
The endpoints you need first.
Rough volume — reads/writes per day.

Early-access users get direct access to us during design, and their endpoints ship first.

Security notes for future integrators

Tokens will be scoped per-user or per-workspace. Workspace tokens will support fine-grained scopes (read-only, publish-only, etc.).
Rate-limited per token. Response headers will indicate remaining quota and reset time.
Webhook payloads signed with HMAC-SHA256. The signing secret is unique per webhook endpoint.
All requests must be TLS 1.2+ over HTTPS.