DOCS

Asendia labels

Create Asendia ePAQ labels on your own carrier account.

Connect your Asendia account to Zonos Dashboard and create Asendia ePAQ shipping labels directly from your shipments, on your own account and your own negotiated pricing.

This guide covers connecting the account, enabling the service levels you ship, and creating your first label.

1

Connect your Asendia account to Zonos

You will need six values from Asendia.

  1. Go to Zonos Dashboard -> Settings -> Rates.

  2. Click Add carrier.

  3. Select Asendia.

  4. Enter your Asendia account information as follows:

    1. Username - your Customer Engagement Portal username.
    2. Password - the password for that portal user.
    3. Client ID - your Asendia client ID.
    4. Client secret - your Asendia client secret.
    5. Access key - your Asendia tracking access key.
    6. Bearer token - your Asendia tracking bearer token.
  5. Click Save to finish.

Asendia issues all six values to your business and emails them to you directly. If you do not have them, contact your Asendia account representative and ask for your Customer Engagement Portal API credentials and your tracking credentials.

The first four create labels. The last two fetch tracking events - Asendia runs tracking as a separate service with its own credentials, so labels and tracking do not share a login.

Supported service levels 

Zonos can create labels for this Asendia product:

Service level↕Code↕
ePAQ Selectasendia.epaq_select

Not currently available:

  • ePAQ Standard (asendia.epaq_standard)
  • ePAQ Plus (asendia.epaq_plus)
  • ePAQ Elite (asendia.epaq_elite)
  • ePAQ Select Direct Access (asendia.epaq_select_direct_access)
  • Asendia Custom (asendia.custom)

These are disabled rather than offered, so they do not appear when you configure a shipping zone. Asendia confirmed in September 2026 that its API accepts ePAQ Select only - the others are rejected at booking with "The country or service entered is not available."

If you need one of them, contact your Asendia account representative first. Once Asendia enables it on their side we can turn it on for you.

Connect via API 

If you connect carrier accounts programmatically rather than through Dashboard, use the carrierAccountConnect mutation with the ASENDIA carrier code.

1{
2 "input": {
3 "carrierCode": "ASENDIA",
4 "rateType": "NEGOTIATED",
5 "credentials": [
6 {
7 "type": "USER_ID",
8 "value": "your_portal_username"
9 },
10 {
11 "type": "API_TOKEN",
12 "value": "your_portal_password"
13 },
14 {
15 "type": "API_KEY",
16 "value": "your_client_id"
17 },
18 {
19 "type": "API_PASSWORD",
20 "value": "your_client_secret"
21 },
22 {
23 "type": "ACCESS_KEY",
24 "value": "your_tracking_access_key"
25 },
26 {
27 "type": "BEARER_TOKEN",
28 "value": "your_tracking_bearer_token"
29 }
30 ]
31 }
32}

Asendia requires the following credential types:

  • USER_ID - your Customer Engagement Portal username
  • API_TOKEN - the password for that portal user
  • API_KEY - your Asendia client ID
  • API_PASSWORD - your Asendia client secret
  • ACCESS_KEY - your Asendia tracking access key
  • BEARER_TOKEN - your Asendia tracking bearer token

All six must come from the same Asendia account.

For the full mutation and response shape, see Connect via API. Connecting an Asendia account does not make a test rating call, so the mutation succeeds as long as the credential types are valid.

Next steps 

Book a demo

Was this page helpful?


Get support·Legal docs·© 2026 Zonos