Rippling REST API access for reading workers, companies, departments, and work locations for a connected Rippling account.
Rippling REST API access for reading workers, companies, departments, and work locations for a connected Rippling account. Use when an agent needs employee or org data from Rippling. Connects with a Rippling API key (entered once on the Pipedream-hosted screen, not OAuth); Pipedream stores and injects it, so Lava holds no key.5 example endpoints available through Lava’s AI Gateway. See the Rippling API docs for full documentation.
This provider requires your own credentials — connect your API key or OAuth account before use.
This is a catch-all provider — any valid URL under https://rest.ripplingapis.com is supported. Rippling REST API. Base https://rest.ripplingapis.com. Resources are root-level plural collections with no version prefix: /workers (list), /workers/{id} (one), /companies, /departments, /work-locations, /users. Pagination is cursor-based: limit and cursor, and the response carries a next_link URL to follow. Pin the version with an optional Rippling-Api-Version: YYYY-MM-DD header. The connected key’s permissions scope what is returned; fields you lack access to come back under __meta.redacted_fields rather than erroring. Auth (the API key) is brokered by Pipedream, do not send an Authorization header. This provider is read-only: only GET requests are supported. The endpoints below are curated examples.
