An open API. Use it however you want.

Open by default. No partner program required.

WorkTiles ships with a public REST API that anyone - your in-house team, your ERP partner, your accounting firm - can integrate against. No certified-integrator program, no marketplace fee, no "contact sales for API access."

Authentication is per-organization API keys with scoped permissions. Rate limits are sane. Endpoints are versioned. Documentation is published.

Two endpoints. Most of what you need.

We've kept the surface deliberately small while still covering the integrations finance teams ask for. The public API today gives you a way to push trial balance data in, and a way to send signals that create or update tasks, comments, and workflows.

• POST /api/import/trial-balance Push trial balance data for one or more periods directly into a reconciliation workflow. Same path the in-app HistoricalImportWizard uses - anything you can import in the UI, you can import via the API.
• POST /api/signals Send inbound signals that trigger actions in WorkTiles. Idempotent by design - safe to retry.

What you can drive from outside

• task.create Create a new task in any workflow.
• task.update Update task fields - title, description, owner, due date, custom fields.
• task.status.update Move a task between statuses. The same status transitions you have in the UI.
• task.comment.create Add a comment to a task. Useful for piping in events from your ERP, ticketing system, or chat tool.
• workflow.create-from-template Spin up a new workflow instance from a template - for new entities, new projects, or new audit cycles.

API keys with scopes. Rate limits per key.

Every organization can issue its own API keys, scoped to specific permissions (import:write, signals:send) so you can hand keys out without giving away the kingdom. Rate limits apply per key. All requests are logged with the key id, organization, and idempotency key, so you have a clean audit trail of every external call.

• Per-organization API keys Generate, rotate, and revoke from the WorkTiles admin UI.
• Scoped permissions Issue keys with only the scopes a given integration needs. Read-only or write-restricted keys are easy.
• Idempotency keys Every signal accepts an idempotency key - safe retries, no duplicate side effects.
• Per-key rate limits Sensible defaults out of the box. Higher limits available for heavy integrations on Enterprise.

What teams build with it

• Pull trial balance from your ERP A nightly job pulls the trial balance from Fortnox, Visma, NetSuite, Business Central - anything with an export - and pushes it into WorkTiles.
• Open tasks from your monitoring tools When a system flags an exception, fire a signal that creates a task in the right finance workflow.
• Sync with your project tracker Two-way sync of task status with Jira, Linear, or Asana for non-finance teams who need visibility.
• Spin up workflows on entity creation When you stand up a new entity in your group, fire workflow.create-from-template to get the standard close, audit, and compliance workflows in one shot.

Get an API key

API keys are managed inside the app, by org admins, in the API keys section. If you'd like a walkthrough or want us to help scope an integration, book a 30-minute call and we'll work through it.