Automation for builders, when the API ships.
We are planning a RESTful API with auth patterns aligned to your tenant model—follow the roadmap for availability.
Every serious platform needs an API for the long tail. Core’s coming API aims to expose the same permission boundaries technicians trust in the UI—without ad-hoc SQL exports.
API
Keys, scopes, predictable resources
GET /v1/tickets?status=new { "data": [ { "id": "tk_...", "title": "..." } ] }
Roadmap
Coming soon with clear expectations.
No silent promises. The registry marks API integration as coming soon until endpoints and docs are production ready.
Tenant-scoped auth. Design assumes OAuth or API keys mapped to tenants—not global god keys.
POST /v1/tickets 201 Created
Coming soon with clear expectations.
Use cases
Webhooks and automations today; API tomorrow.
Bridge the gap. Until REST is GA, many teams use automations and outbound webhooks for integration.
Custom reporting. Future read APIs should complement built-in reporting instead of replacing it.
- Per-tenant keys
- Rate limits
- Audit log of calls
Webhooks and automations today; API tomorrow.
Safety
Rate limits and audit from day one.
Abuse resistance. Public APIs need throttles; Core will document limits with each release.
Observability. Expect request logging aligned to compliance needs.
Rate limits and audit from day one.
Frequently asked questions
Ready to try Core?
Start a free trial or talk to us about rolling out API Integration with your team.