Worksible API
A REST API on top of the same data layer that powers the Worksible OS application: organizations, freelancers, projects, contracts, invoices, payments, payouts and timesheets. Authenticate with an API key, scope it to what you need, integrate at your own pace.
The public REST API is included with every paid plan. Trial and Core plans don't ship API keys — upgrade from Settings → Billing when you're ready.
https://api.worksible.com/v1# All you need is an API key and the base URL.
curl https://api.worksible.com/v1/companies/me \
-H "Authorization: Bearer wsk_live_********_********"Design pillars
Four properties guide every decision we make about this surface, from the URL shape to the retry semantics. They're also the contract you can hold us to.
Predictable
Stable URLs, semver-style versioning, deprecation notices six months before any breaking change.
Observable
Every request is logged with method, path, status, latency, IP and user agent. Queryable from the dashboard.
Secure by default
Hashed-at-rest API keys, scope-gated endpoints, IP allowlists on Enterprise, automatic key expiry.
Idempotent writes
Mutating endpoints accept Idempotency-Key. Replays return the original response, never double-create.
Pick where to start
Quick start
Make your first call in three minutes.
Authentication
Keys, scopes, transports, security model.
Conventions
IDs, money, timestamps, pagination, filtering.
Rate limits
Per-plan windows, headers, throttle strategy.
Idempotency
Safe retries with Idempotency-Key.
Errors
Status codes, error shapes, retry semantics.
Webhooks
Push events to your systems. Roadmap.
API reference
Every endpoint, every field.
SDKs & tools
Official + community libraries, Postman.
Changelog
What shipped, what's deprecating.
Versioning policy
The current major version is v1. Within a major version, we add fields and endpoints freely; we never remove or rename them. Breaking changes get a new major version with a six-month deprecation window for the previous one.
- Additive only. New fields can appear in any response. Your client must ignore unknown fields.
- Deprecation surface. Endpoints scheduled for removal carry the
SunsetandDeprecationresponse headers (RFC 8594), and email goes out to every key's billing contact. - Changelog. Every change is documented in the changelog.
Need help?
Engineering questions go to developers@worksible.com. Production incidents page our on-call via status.worksible.com. Account questions stay with your CSM.