> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/rydership-formerly-whiplash.md).

# Rydership (formerly Whiplash)

Set up the RyderShip connector in Pandium using OAuth2 credentials so tenants can authenticate securely and sync inventory, order processing, and shipping data for e-commerce operations.

## **Connector Overview**

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcMXSnqmPqrf4s5qf3Cq2OeyfOFr92BG4eH-Cl8oXguUoejBaYOXImoPd-SNhjCIt9pbNZLgeYTCPDHyQSfyYeq8rdeB6_r5974mYhBTE-WSsQsdPFSEeoE2JBUPLL-8-uour93?key=XIy8122ZNqmu67sUe4Q2WNF3" alt="" width="188"><figcaption></figcaption></figure>

RyderShip (formerly Whiplash) is a cloud-based logistics platform designed to streamline inventory management, order processing, and shipping for e-commerce businesses, enhancing their operational efficiency and scalability.

## **Authentication Type**

Basic & OAuth

## **Webhook Supported**

Yes

## **Secrets**

* Basic
  * PAN\_SEC\_WHIPLASH-CLIENT\_ACCESS\_TOKEN
  * PAN\_SEC\_WHIPLASH-CLIENT\_CLIENT\_SECRET
  * PAN\_SEC\_WHIPLASH-CLIENT\_EXPIRES\_AT
  * PAN\_SEC\_WHIPLASH-CLIENT\_SCOPE
  * PAN\_SEC\_WHIPLASH-CLIENT\_TOKEN\_TYPE
  * PAN\_SEC\_WHIPLASH-CLIENT\_CLIENT\_ID
* OAuth
  * PAN\_SEC\_WHIPLASH\_ACCESS\_TOKEN
  * PAN\_SEC\_WHIPLASH\_REFRESH\_TOKEN
  * PAN\_SEC\_WHIPLASH\_API\_BASE\_URL
  * PAN\_SEC\_WHIPLASH\_CUSTOMER\_ID
  * PAN\_SEC\_WHIPLASH\_EXPIRES\_IN
  * PAN\_SEC\_WHIPLASH\_SCOPE

## **API Client Supported**

No

## **Requirements for Provisioning**

In order to provision your connector, the following RyderShip information must be gathered:

* Basic = No provisioning is required for this connector.
* Oauth
  * API Base URL
  * Client ID
  * Client Secret
  * Scope

To obtain the information required for setting up your RyderShip Connector, perform the following steps:

1. Submit a [V2 Access Request Form](https://help.whiplash.com/hc/en-us/articles/4416896728219-API-Access-Request-Form) to gain access to the Rydership API
2. Use the information provided to [Authenticate](https://help.whiplash.com/hc/en-us/articles/360050870691-Authentication-for-the-V2-API)

*If you need assistance accessing this information, please reach out to a RyderShip Customer Success Manager.*

## **How to Connect Your Integration**

Upon successfully creating a tenant, you will use the following information to connect to Visma:

* For Basic
  * API Base URL
  * Client ID
  * Client Secret
  * Scope
* For Oauth
  * Customer ID

## **API Resources**

For more information on how to utilize the RyderShip API, feel free to reference the following [documentation](https://help.whiplash.com/hc/en-us/categories/13378954544411-RyderShip-Application-Developers).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pandium.com/connectors/connectors-101/rydership-formerly-whiplash.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.