What authentication does the Kandio API use?

The API uses OAuth2 (passport scheme) with bearer tokens issued per organisation. Each request must include `Authorization: Bearer {token}` and the organisation slug in the path. Through Jentic, OAuth tokens are stored encrypted in the vault and injected at execution time so the agent never handles raw tokens.

Can I create a skills assessment for a candidate via the Kandio API?

Yes. POST /{organization}/tests/{test}/assessments creates an assessment tied to a specific test inside an organisation. The response includes the candidate invitation URL that you forward to the applicant. The same assessment ID is later used with GET /{organization}/assessments/{assessment} to fetch the scored result.

What are the rate limits for the Kandio API?

Kandio does not publish hard rate limits in the spec; in practice the platform expects integration-level traffic from ATS and job-site partners. If you exceed the platform's burst tolerance the API responds with HTTP 429. Contact info@kand.io to negotiate higher throughput for high-volume screening.

How do I subscribe to assessment completion events through Jentic?

Run `pip install jentic` and search Jentic for 'subscribe to Kandio assessment events'. Jentic returns the schema for the /webhooks endpoint; supply your callback URL and the event types you care about, and execute the call to register the subscription.

Can I list every test available to my Kandio organisation?

Yes. GET /{organization}/tests returns the tests configured for the organisation, including each test's skill area, duration, and difficulty. Use GET /skillareas first to discover the catalogue of skill areas before filtering tests.

Is the Kandio API free?

No - Kandio is a paid skills-testing marketplace and API access is bundled with platform subscriptions. The free Jentic tier covers the integration plumbing, but the underlying assessments are billed by Kandio per test or per seat.

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

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which Kandio operations and credentials the agent may use. Since Kandio puts the organization in the URL path, such as /{organization}/tests/{test}/assessments, you can pin the agent to a single organization so it only creates and reads assessments for that org and nothing else. You also choose exactly which operations it may call, so it stays on assessment creation and scoring unless you allow more, such as GET /{organization}/assessments or the /webhooks endpoints.