Connect your loyalty program in Rippling HR without researching its API, registering in a developer program, and getting your application approved. We take care of authentication, secure credentials storage, and token refreshes so you don't have to.

Rippling HR

Returns the currently accessible company for the given token. Please note, the returned fields depend on the scopes that are enabled for your access token or API key.

GET Current Company

Returns a list of departments for the given company.

GET Departments

Retrieves the list of active employees. The fields retrieved depend on the employee scopes that you have access to for your access token or API key. The only guarenteeed fields include id, personalEmail, and roleState.
For optimal performance, ensure pagination is used via our limit and offset parameters. Pagination should be set to a maximum of 100.

GET Employees

Returns the list of work locations for a given company.

GET Work Locations

Returns the custom fields for the given company.

GET Custom Fields

Retrieves the list of teams for the company.

GET Teams

Retrieves the levels for the company. Levels are set positions for an organization, such as Manager, or Executive.

GET Levels

Retrieves the information for a single employee based on the scopes that your API key or access token have access to.

GET Employee

This endpoint is similar to the active employees endpoint, but instead, it includes both active and terminated employees.

For optimal performance, ensure pagination is used via our limit and offset parameters. Pagination should be set to a maximum of 100.

GET Employees (Including Terminated)

Retrieves basic information about the Rippling user whose access token you're using. This is generally used for the SSO flow.

GET Current User

Please note, the Groups endpoint requires an OAuth application (i.e. approved 3rd party partners), as the end point is intended for mapping third-party application “Groups” within Rippling organizations.

Lists the current third-party groups for an organization.

GET Groups

Creates a generic group, that can be associated within the third-party application.

POST Groups

Please note, the Groups endpoint requires an OAuth application (i.e. approved 3rd party partners), as the end point is intended for mapping third-party application “Groups” within Rippling organizations.

Using the PUT method, all of the group fields will be updated, even if the corresponding parameter is missing. If the PATCH method is used, and a param is missing, its value won’t be changed.

PUT Group

PATCH Group

Please note, the Groups endpoint requires an OAuth application (i.e. approved 3rd party partners), as the end point is intended for mapping third-party application “Groups” within Rippling organizations.

Deletes the specified group.

DELETE Group

Retrieves the current leave requests.The query can be filtered by a number of specific query parameters.

GET Leave Requests

Create a leave request. This endpoint is currently in alpha and should not be used by default. Only TILT managed requests can have a status other than PENDING.

POST Leave Request

Retrieves the current company leave types. The query can be filtered by managedBy field.

GET Company Leave Types

Retrieves the leave balances for employees

GET Leave Balances

Retrieves the leave balances for a given role. A role represents 1 employee. An employee can work at 1 and only 1 company.

GET Leave Balance

Returns a SAML IDP metadata file for the current app integration. Note that this endpoint is only accessible using a token associated with an app integration that has SAML enabled; otherwise it returns a 404 error.

Rippling's SAML Metadata is per customer app installation. It is not the same across all customers. It is not the same if the customer uninstalls and reinstalls your app. Any time a new app is installed, unique SAML Metadata will be generated specific to that app.

GET SAML Metadata

Pushes a candidate from an applicant tracking system directly into the Rippling onboarding flow. Please note, this endpoint is only available to applications integrating with OAuth2.0.

POST New Candidate

Retrieves the activity for a given company.

The most reliable method to ingest all activity from Rippling is to use a pagination cursor via the 'next' parameter. This will ensure that events are not skipped or duplicated due to the lack of timestamp precision.

The general sequence of steps to leverage the next parameter:

1. Issue an initial request using startDate with a value set to some date in the last 90 days
2. Retrieve the next page of events through the next value from the response data.
3. Issue the paginated request
4. Retrieve the next page of events through the next value from the response data
5. Pause and repeat the previous step


GET Company Activity

Approve or decline a leave request. Only pending requests can be processed (approved / declined). Only an admin or manager is capable of taking action on a request.

POST Process Leave Request

PATCH Leave Request

This endpoint can be hit to mark your app as installed in Rippling, if you aren't hitting Rippling's other endpoints on installation. The endpoint does not require any scopes.

Please note, hitting any other endpoint should mark your app as installed as well.

Mark App Installed

Seamlessly integrate loyalty with Rippling HR to streamline your business.

Integrate Rippling HR with White Label Loyalty

thumbnail_15.png

White Label Loyalty + Rippling HR integration

About Rippling HR

Similar Integrations

Okta

Greenhouse Harvest

Namely

Recruitee

Benefits of White Label Loyalty + Rippling HR

Integrate now!

Automate desired actions with Rippling HR