Rippling (BYOK)

Rippling (BYOK) — connector documentation

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

What Rippling (BYOK) is for

Rippling (BYOK) lets an AI assistant read your own Rippling data through the Rippling API with a key you supply (Rippling API token). Read-only: 11 tools (list_companies, list_workers, get_worker, list_users, get_user, list_departments, list_teams, list_work_locations, list_leave_types, list_leave_balances, list_leave_requests). 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 rest.ripplingapis.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rippling. Rippling 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 Rippling company is my token for?"
• "Who are the active workers in Rippling?"
• "Show Rippling worker w1"
• "Who has a Rippling user account?"
• "Show Rippling user u1"
• "What departments does Rippling have?"

What it does

• list_companies: List the Rippling companies the token is bound to, with name, legal name, primary email and phone.
• list_workers: List workers (employment records) with title, status, dates, manager, department and work email. Contains personal employee data; Rippling hides fields the token's scopes do not allow.
• get_worker: Get one Rippling worker by id: title, status, dates, manager, department and work email. Contains personal employee data; Rippling hides fields the token's scopes do not allow.
• list_users: List Rippling users (people and login profiles) with display name, username, emails, timezone and active flag. Contains personal employee data; Rippling hides fields the token's scopes do not allow.
• get_user: Get one Rippling user by id. Contains personal employee data; Rippling hides fields the token's scopes do not allow.
• list_departments: List departments with name, parent and reference code.
• list_teams: List teams with name and parent team.
• list_work_locations: List work locations with name and address.
• list_leave_types: List leave types (vacation, sick and so on) with paid flag and description.
• list_leave_balances: List leave balances per worker and leave type, with balance excluding and including future requests. Contains personal employee data; Rippling hides fields the token's scopes do not allow.
• list_leave_requests: List leave requests with worker, dates, status (PENDING, APPROVED, REJECTED or CANCELED) and leave type. Contains personal employee data; Rippling hides fields the token's scopes do not allow.

BYOK key

You bring your own Rippling Rippling API token (https://developer.rippling.com/documentation/rest-api/essentials/api-tokens). 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 rest.ripplingapis.com 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://developer.rippling.com/documentation/rest-api (the API this connector calls, with a BYOK key)

Live from the Rippling API (rest.ripplingapis.com) with a BYOK key; documentation: https://developer.rippling.com/documentation/rest-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 Rippling. Rippling 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 Rippling account.

Built for: Worldwide. Languages: English.

Rippling (BYOK) — Privacy Policy

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

What Rippling (BYOK) is. Rippling (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Rippling data: Read your Rippling workforce data: companies, workers, users, departments, teams, work locations and leave types, balances and requests with your own API token. You bring your own Rippling Rippling API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Rippling 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 rest.ripplingapis.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Rippling 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 Rippling receives. The request we make on your behalf, including the key and the arguments, under Rippling's own terms and privacy policy. Rippling acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Rippling 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 Rippling 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. Rippling (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 Rippling at any time to end all access.

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

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

Rippling (BYOK) — Terms of Service

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

1. The Service. Rippling (BYOK) provides: Read your Rippling workforce data: companies, workers, users, departments, teams, work locations and leave types, balances and requests 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 Rippling credentials and only access data you are allowed to access. Rippling's terms apply to your use of Rippling; 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 Rippling. Rippling 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 Rippling returns, lightly trimmed; it may be incomplete, delayed or changed by Rippling. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Rippling 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 Rippling'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; Rippling 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 Rippling 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 Rippling 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-rippling

Rippling (BYOK) support

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

• MCP endpoint: https://byok-rippling.connectorbay.com/mcp
• REST API: https://byok-rippling.connectorbay.com/openapi.json
• Live status: https://byok-rippling.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. Rippling (BYOK) never asks for them.