Loxo (BYOK)

Loxo (BYOK) — connector documentation

• MCP endpoint: https://byok-loxo.connectorbay.com/mcp
• REST API: POST https://byok-loxo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-loxo.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Loxo Loxo API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-loxo.connectorbay.com/health · Tool schemas: https://byok-loxo.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-loxo · agent@connectorbay.com

What Loxo (BYOK) is for

Loxo (BYOK) lets an AI assistant read your own Loxo data through the Loxo API with a key you supply (Loxo API token). Read-only: 12 tools (list_jobs, get_job, list_companies, get_company, list_job_statuses, list_job_types, list_job_categories, list_seniority_levels, list_company_types, list_workflows, list_activity_types, list_agencies). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.loxo.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Loxo. Loxo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which published jobs does my Loxo agency have?"
• "Show me Loxo job 1234"
• "Which client companies are in my Loxo CRM?"
• "Show me Loxo company 55"
• "What job statuses does Loxo use?"
• "What job types does Loxo use?"

What it does

• list_jobs: Search and list jobs (recruiting searches, requisitions or openings). The query uses Lucene syntax, for example title:"account executive" AND company_name:acme. The answer is the object as Loxo returns it, shortened to fit.
• get_job: Get one job by ID with its details. The answer is the object as Loxo returns it, shortened to fit.
• list_companies: Search and list companies (clients, employers) in the Loxo CRM. Query uses Lucene syntax. Pages with a scroll cursor. The answer is the object as Loxo returns it, shortened to fit.
• get_company: Get one company by ID with its details. The answer is the object as Loxo returns it, shortened to fit.
• list_job_statuses: List the job statuses, such as open, closed or on hold. The answer is the object as Loxo returns it, shortened to fit.
• list_job_types: List the job types, such as full-time, contract or temporary. The answer is the object as Loxo returns it, shortened to fit.
• list_job_categories: List the job categories used to classify job openings. The answer is the object as Loxo returns it, shortened to fit.
• list_seniority_levels: List the seniority levels used for candidates and jobs. The answer is the object as Loxo returns it, shortened to fit.
• list_company_types: List the company types, such as client, vendor or competitor. The answer is the object as Loxo returns it, shortened to fit.
• list_workflows: List the agency workflows (the pipeline stage setups used for jobs). The answer is the object as Loxo returns it, shortened to fit.
• list_activity_types: List the activity types used to log calls, emails and meetings, optionally for one workflow. The answer is the object as Loxo returns it, shortened to fit.
• list_agencies: List the current agency and its active child agencies. The answer is the object as Loxo returns it, shortened to fit.

BYOK key

You bring your own Loxo Loxo API token (https://loxo.readme.io/reference/loxo-api). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to app.loxo.co over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://loxo.readme.io/reference/loxo-api (the API this connector calls, with a BYOK key)

Live from the Loxo API (app.loxo.co) with a BYOK key; documentation: https://loxo.readme.io/reference/loxo-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Loxo. Loxo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Loxo account.

Built for: Worldwide. Languages: English.

Loxo (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Loxo (BYOK) is. Loxo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Loxo data: Read your Loxo recruiting jobs, companies, job statuses and types, workflows and reference lists with your own API token. You bring your own Loxo Loxo API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Loxo call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to app.loxo.co, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Loxo rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Loxo receives. The request we make on your behalf, including the key and the arguments, under Loxo's own terms and privacy policy. Loxo acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Loxo gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Loxo data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Loxo (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Loxo at any time to end all access.

Children. Loxo (BYOK) is a general-audience service operated by the adult using the assistant, under Loxo's own age rules.

Changes. We will post changes here with a new effective date.

Loxo (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Loxo (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Loxo (BYOK) provides: Read your Loxo recruiting jobs, companies, job statuses and types, workflows and reference lists with your own API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Loxo credentials and only access data you are allowed to access. Loxo's terms apply to your use of Loxo; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Loxo. Loxo and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Loxo returns, lightly trimmed; it may be incomplete, delayed or changed by Loxo. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Loxo account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Loxo's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Loxo may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Loxo key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Loxo takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-loxo

Loxo (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-loxo.connectorbay.com/mcp
• REST API: https://byok-loxo.connectorbay.com/openapi.json
• Live status: https://byok-loxo.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Loxo (BYOK) never asks for them.