Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.

What can my API key do?

The capabilities a key can have and who can create them.

A key can only do what it is allowed to do. That usually follows the permissions of the person who created it in that organization.

Capabilities

- Read jobs and company data - Apply or submit applications - Post jobs for your organization - Manage candidates and hiring pipeline data - Manage webhooks - Work with employees, surveys, or documents on the Business side

A forbidden (403) response means the key lacks that capability, and its message says which one. Some keys Worklittle sets up for partner apps can only search and apply: Business features answer BUSINESS_ACCESS_OFF.

Change what a key can do

On API keys, choose the key's Permissions (Full access, Jobs only, Custom, or No access). The sheet is the same as a custom role: Hiring, Candidates, Employees (including pay and benefits), Calendar, Surveys, Documents, Automations, API, Webhooks, Billing, and Organization. Above them, Jobs covers searching and applying to jobs and writing resumes. In a Personal workspace, Use your profile lets the key apply as you.

A key can only ever do what both the key and the person who made it may do right now. If their role changes, or they leave the organization, the key changes with them. The key's creator or an organization admin can change its permissions, never beyond their own role. Changes apply to the key's next request.

Who can create keys

Owners and people with enough edit access can create keys for the organization. A key from a limited role cannot perform owner-only actions.

If a developer needs more access, an owner can create the key or raise the teammate’s role. See Roles and permissions.

Full scope lists

See the scope tables in the Jobs API keys docs and Business API keys docs.