Nexra
All connectors
Implemented
HR, recruitment & payroll
Rippling logo

Rippling

Read Rippling workers, users, departments, work locations, teams, levels, custom fields and leave balances; create and update departments and leave requests.

Use Rippling as the employee system of record for provisioning, org charts, leave and reporting flows.

Build a flow with RipplingProvider API documentation

Source actions

15

Destination actions

4

Data types

12

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

companies
  • List companies
    Source

    The company bound to the token.

    companies.list
custom fields
  • List custom fields
    Source

    Custom field definitions with type and options.

    custom_fields.list
departments
  • Create department
    Destination
    Not retried automatically
    Approval before production

    Creates a department, optionally under a parent.

    departments.create
  • List departments
    Source

    Departments with parent and reference code.

    departments.list
  • Update department
    Destination
    Provider duplicate protection
    Approval before production

    Renames or re-parents a department.

    departments.update
employment types
  • List employment types
    Source

    Employment types such as salaried full time or contractor.

    employment_types.list
leave balances
  • List leave balances
    Source

    Balances per worker and leave type, in minutes and days.

    leave_balances.list
leave requests
  • Create leave request
    Destination
    Not retried automatically
    Approval before production

    Submits a pending leave request for a worker.

    leave_requests.create
  • Get leave request
    Source

    One leave request by ID.

    leave_requests.get
  • List leave requests
    Source
    Incremental

    Leave requests with status, dates and reviewer.

    leave_requests.list
  • Update leave request
    Destination
    Provider duplicate protection
    Approval before production

    Changes the dates, times, reason or comments of a leave request.

    leave_requests.update
leave types
  • List leave types
    Source

    Leave types with paid flag.

    leave_types.list
levels
  • List levels
    Source

    Job levels with rank and track.

    levels.list
teams
  • List teams
    Source

    Teams with their parent team.

    teams.list
users
  • Get user
    Source

    One user by ID.

    users.get
  • List users
    Source
    Incremental

    People and login profiles: names, work email, locale and time zone.

    users.list
work locations
  • List work locations
    Source

    Work locations with address.

    work_locations.list
workers
  • Get worker
    Source

    One worker by ID.

    workers.get
  • List workers
    Source
    Incremental

    Employment records with status, title, manager, department, level and custom fields.

    workers.list

Authentication

Rippling API token (REST API v2)

Plans and access

Rippling customers; API tokens are created in Tools → Developer → API Tokens. A token sees the intersection of its scopes and its owner's permission profile; hidden fields return null and are listed in __meta.redacted_fields. Tokens are revoked when unused for 30 days or when the owner is terminated.

Test environment

Rippling does not offer a public sandbox for customer API tokens.

Rate limits

300 requests per IP per 10-second sliding window; over the limit every request gets HTTP 429 for 10 seconds.

Pagination

limit (max 100) and cursor, following the absolute next_link until it is null.

Provider events

Rippling in-product webhooks and App Shop partner webhooks for employee and leave events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Uses the v2 REST API on rest.ripplingapis.com; the legacy V1 platform API (/platform/api) is not used.
  • The token's own API version applies; no Rippling-Api-Version header is pinned.
  • Third-party groups (V1 /groups) are not implemented: they require a partner OAuth app, and v2 offers Supergroups instead.
  • Leave requests are created as PENDING so they follow Rippling's approval flow; approvals are not automated.
  • Null values can mean the token cannot see a field; check redactedFields.
  • Compensation, SSNs, dates of birth and home addresses are not mapped. Deletes are not implemented.

Developer reference

  1. Create the Rippling People Center Inc. credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Rippling, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Rippling People Center Inc. docsAPI referenceRippling People Center Inc. docsAuthenticationRippling People Center Inc. docsRate limitsRippling People Center Inc. docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/rippling and the Connections API.