Loxo Open API: authenticate and query Jobs, People, and Companies
domain: loxo.co · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm your Loxo account has an active Open API subscription (it's a paid feature) and that an admin has created a Bearer API key under Settings > API Keys.
Build request URLs as https://{domain}/api/{agency_slug}/{resource}, using the Agency Domain and Agency Slug Loxo Support provides for your account.
Send requests with header authorization: Bearer {API_KEY} and header accept: application/json.
GET /jobs, /people, or /companies (each supports a query parameter for keyword search) to retrieve lists, or GET /jobs/{id}, /people/{id} for a single record.
For write operations, POST /companies or /people to create records, and PUT /companies/{id} or /people/{id} to update them.
When posting a new Job, first call GET /compensation_types to get valid salary type values, since job[salary] and other mandatory fields will return 'Invalid parameters' if malformed.
Known gotchas
Calling unsupported legacy paths like /api/v1/people or /api/v1/jobs returns a 403 Forbidden — only the documented Open API endpoints under /api/{agency_slug}/... are valid.
Extra whitespace in the agency_slug or other URL parameters is a common, hard-to-spot cause of 403 errors — the correct fix is trimming stray leading/trailing spaces, not regenerating the API key.
Profiles sourced from 'Loxo Source' contain proprietary data and are deliberately limited to person_name, person_id, and custom_field in API responses — full profile data isn't returned for those records.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?