> ## Documentation Index
> Fetch the complete documentation index at: https://www.zippendo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect WebrinQ

> Connect WebrinQ under Carriers with your API key, and book return pickups in Denmark where a WebrinQ driver collects the return at your customer's address.

**WebrinQ** collects returns in Denmark. You book a return in Zippendo, and a WebrinQ driver picks up the parcel at your customer's address and brings the label. WebrinQ only does returns: it does not deliver your orders. The fields that every carrier shares are on [Carrier credentials](https://www.zippendo.com/docs/how-to/carrier-credentials.md).

> [!NOTE]
>
> WebrinQ takes the return to the return address it holds for your company, not to the address on the shipment in Zippendo. To change where returns go, contact WebrinQ.

## Before you start

* A WebrinQ agreement, with an **API key** from WebrinQ. A key that starts with `wq_test_` books test returns on WebrinQ's test system. A key that starts with `wq_live_` books real pickups.
* If WebrinQ gave you one key for several companies, the **Company code** WebrinQ uses for this shop.

You can connect WebrinQ more than once, for example with a test key and a live key. Give each connection its own **Carrier name**. **Learn more** on the card opens [webrinq.com](https://webrinq.com/).

## Connect WebrinQ

**1. Open All carriers**

In the sidebar, click **Carriers**, then open the **All carriers** tab.

**2. Find WebrinQ**

On the **WebrinQ** card, click **Connect**.

**3. Fill in the form**

The **Connect carrier** window opens. Enter a **Carrier name** and your **API key**. **Company code** is under **Optional fields**.

**4. Connect the carrier**

Click **Connect**. You see "Carrier connected", and the carrier appears on the **My carriers** tab.

## Fields on the form

| Field | Required | What to enter |
| - | - | - |
| **Carrier name** | Yes | The name you see on **My carriers** and when you pick a carrier on a shipment. It starts as **WebrinQ**. |
| **Brand** | No | Shown only if your organization has [brands](https://www.zippendo.com/docs/how-to/create-a-brand.md). The form says: "Only this brand can use this carrier." Leave it empty to let every brand use it. |
| **API key** | Yes | Copy it exactly as WebrinQ sent it. The form says: "The API key WebrinQ gave you. A key starting with wq\_test\_ books test returns on WebrinQ's test system, and a key starting with wq\_live\_ books real pickups." |
| **Company code** | No | The form says: "Only if WebrinQ gave you one key for several companies: the company code WebrinQ uses for this shop, for example example-shop-0000. Leave it empty otherwise." |

WebrinQ has no **Test mode** switch: the key decides. A `wq_test_` key always books test returns, and a `wq_live_` key always books real pickups. See [Test mode](https://www.zippendo.com/docs/how-to/sandbox-mode.md).

**Connect** does nothing until **Carrier name** and **API key** have a value. When you click **Connect** or **Save**, Zippendo checks the details with WebrinQ before it saves them:

* WebrinQ must accept the **API key**.
* If the key books for several companies, the **Company code** must be one of them.
* WebrinQ must have finished setting up the company for returns.

If a check fails, the carrier is not saved, and you see the reason. If WebrinQ cannot be reached, Zippendo saves the details without the check, and a mistake shows up the first time you send a return.

## After you connect

WebrinQ has one product, **WebrinQ Return pickup**, which you use on a return shipment. To create one, see [Inbound and returns](https://www.zippendo.com/docs/how-to/inbound-and-returns.md).

* **Where:** your customer's address must be in Denmark. Your customer is the sender of the return.
* **Phone number:** your customer's mobile number is required. WebrinQ uses it to arrange the pickup. The email address is optional.
* **Parcels:** up to 50 parcels per return, each with its weight.
* **Pickup day:** WebrinQ chooses it. You cannot pick a date. Once the return is sent, the shipment shows the expected pickup day, and the tracking shows it too.
* **Label:** the driver brings the label, so the return has no label to print or send to your customer.
* **Driver note:** under **Extra details for the carrier**, a note for the driver, for example which bell to ring. Up to 200 characters.

Returns with WebrinQ are not created automatically. Book each one yourself.

### Tracking

The return's tracking number is the return number WebrinQ gives it, for example `RTN-2026-00042`. Every parcel in the return shares it. Zippendo fetches the status from WebrinQ about once an hour. There is nothing to set up. The tracking shows when the driver has collected the return, and when WebrinQ reports that it was not collected or was cancelled. See [Carrier tracking webhooks](https://www.zippendo.com/docs/how-to/tracking-webhooks.md).

WebrinQ is not available under **Pickups**: each return is already a pickup.

### Cancel a return

Open the sent return and click **Cancel shipment**, then confirm. WebrinQ answers later, so you see **Cancellation sent to the carrier. Its answer shows in the tracking.** The return stays **Sent**, and the tracking shows when WebrinQ has cancelled it. If the driver has already collected the parcel, WebrinQ refuses, and nothing changes. See [Hold, cancel, or delete a shipment](https://www.zippendo.com/docs/how-to/hold-cancel-and-delete-shipments.md).

## Change or remove the connection

To change it, open **Carriers** → **My carriers** and click **Edit carrier** on the card. The **Edit carrier** page has two sections:

* **General**: **Carrier name**, and **Brand** if your organization has brands.
* **Carrier settings**: **API key** and **Company code**.

Click **Save**. You see "Carrier updated".

To remove it, click **Delete** on the same page, type the carrier name in capital letters, and click **Delete**. Shipping rules that use this carrier are deleted with it. Returns you already booked keep their return numbers.

## Common problems

| What you see | What to do |
| - | - |
| "Couldn't connect the carrier. Try again." | Check that every required field has a value, then try again. |
| "The carrier rejected your login details. Update the carrier credentials under Carriers." when you connect | WebrinQ does not accept the **API key**. Copy it again from WebrinQ. |
| "The carrier's settings are incomplete or not valid. Check them under Carriers." when you connect | WebrinQ's reason is shown under the message: the **Company code** is missing or not one of the key's companies, or WebrinQ has not finished setting up your company. Enter the code WebrinQ named, or contact WebrinQ. |
| "The carrier rejected your login details. Update the carrier credentials under Carriers." when you send | WebrinQ does not accept the **API key**. Copy it again from WebrinQ and fix it on **Edit carrier**. |
| "The carrier's settings are incomplete or not valid. Check them under Carriers." | The **API key** does not start with `wq_test_` or `wq_live_`, the **Company code** is missing or wrong, or WebrinQ has not finished setting up your company, for example its return address. The shipment shows WebrinQ's reason. Contact WebrinQ if the settings look right. |
| "Some options for this carrier product are missing or not valid. Check the shipment's services and options, then try again." | A detail of the return is missing or not accepted: often your customer's mobile number, a parcel without a weight, a name or address that is too long, or a postcode WebrinQ does not know. The shipment shows the reason. Fix it and send again. |
| "The selected carrier product does not ship between these countries. Choose a different product." | Your customer's address is outside Denmark. WebrinQ collects in Denmark only. |
| "WebrinQ couldn't book the return pickup." | WebrinQ refused the return for another reason. The shipment shows WebrinQ's reason. |
| "The carrier did not respond. Try again in a moment." | WebrinQ is busy, or your company has reached its daily number of returns. Nothing was booked. Send again later. |
| "The connection to the carrier was lost before it answered. Zippendo has no confirmation that the shipment was created, so check with the carrier before sending again." | Send the return again without changing it. If WebrinQ did book it, it answers with the same return number, and no second pickup is booked. |
| "WebrinQ answered the booking, but its reply could not be read. Check with WebrinQ before sending the shipment again." | WebrinQ most likely booked the return. Check with WebrinQ before you send it again. |
| "The carrier refused to cancel the shipment, for example because the parcel has already been collected." | WebrinQ did not cancel the return, most often because the driver has collected it. The return goes ahead. |

More help: [Carrier authentication failures](https://www.zippendo.com/docs/knowledge-base/carrier-authentication-failures.md).

## Related

* [Connect a carrier or integration](https://www.zippendo.com/docs/how-to/connect-index.md)
* [Carrier credentials](https://www.zippendo.com/docs/how-to/carrier-credentials.md)
* [Test mode](https://www.zippendo.com/docs/how-to/sandbox-mode.md)
* [Inbound and returns](https://www.zippendo.com/docs/how-to/inbound-and-returns.md)
* [Request a carrier integration](https://www.zippendo.com/docs/how-to/request-carrier-integration.md)
* [Carriers](https://www.zippendo.com/docs/tutorials/carriers.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.