What authentication does the Karbon API use?

The API uses HTTP bearer tokens. Each request must include `Authorization: Bearer {token}` where the token is generated from the Karbon admin console. Through Jentic, tokens are encrypted in the vault and scoped per execution so the raw bearer never enters the agent's context.

Can I create a work item for a client engagement via the Karbon API?

Yes. POST /workItems creates a work item bound to a client organisation, and POST /tasks adds tasks under that work item. This is the standard flow for spinning up a tax-return or audit engagement programmatically at the start of the season.

What are the rate limits for the Karbon API?

Karbon enforces per-tenant throttling and returns HTTP 429 when bursts exceed the limit. The published guidance for v3 is to keep below ~10 requests per second per tenant - check the firm's Karbon plan if a heavier sync is needed and use server-side filtering on /timesheets to keep payloads small.

How do I add a meeting note to a client through Jentic?

Run `pip install jentic` and search Jentic for 'add a note to a Karbon client'. Jentic returns the schema for POST /notes; supply the organisation or contact ID and the note body, then execute to attach the note.

Can I list all open tasks assigned to a specific accountant?

Yes. GET /tasks supports filtering by assignee user ID and status, so you can return all incomplete tasks owned by a single accountant. Combine with GET /users to resolve names to IDs first.

Is the Karbon API included in every plan?

API access is available on Karbon's paid plans but not on the trial tier. Higher-volume integrations (full timesheet exports, large-firm syncs) may require a custom rate-limit arrangement with Karbon support.

Can I limit what my agent is allowed to do with the Karbon API?

Yes. Because Jentic One is self-hosted, you decide which Karbon operations and credentials your agent may use, and it can only call the endpoints you allow. Most Karbon writes post to collection endpoints such as /workItems, /tasks, and /notes, so you scope the agent by operation, for example letting it create notes without also granting contact creation on /contacts. An agent set up to file notes cannot create work items or read /timesheets unless you add those operations to its allowed set.