Connect ShippingEasy: verify your API credentials

Copy your API Key and API Secret from the same ShippingEasy API Credentials page, paste them into Integration, and run the signed test — this connection verifies credentials only.

The ShippingEasy connector verifies your ShippingEasy API credentials in Integration. You fill in an API Key and an API Secret; every request is signed with the secret using HMAC-SHA256, and the secret itself is never sent in plain text. This connection is for credential verification only — under the ShippingEasy Customer API it does not provide rate shopping, label buying, or tracking lookup by tracking number.

Prerequisites#

• A ShippingEasy account, with access to Settings → API Credentials.
• Your API Key and API Secret ready — both are on the same page: Settings → API Credentials (app.shippingeasy.com/settings/api_credentials).
• Know what this connection is for before you start: it verifies credentials only. It does not add rate shopping, label buying, or tracking lookup to Integration.

Get your credentials#

1. Sign in to ShippingEasy and go to Settings → API Credentials (app.shippingeasy.com/settings/api_credentials).
2. On that page, copy the API Key. It is the public API key for this account.
3. On the same page, copy the API Secret. It is the private API secret: each request is signed with it using HMAC-SHA256, and the secret itself is never sent in plain text.
4. Keep the Key and the Secret together as a pair from that one page, and save the Secret somewhere safe.

Fill it into Integration#

1. Open Integration → Connector Marketplace → ShippingEasy → New connection.
2. API Key (api_key) — required: paste the API Key from ShippingEasy → Settings → API Credentials. Fill the Key into the Key field only — do not swap it with the Secret.
3. API Secret (api_secret) — required: paste the API Secret from the same Settings → API Credentials page. It is encrypted at rest and never echoed back; Integration uses it to sign each request with HMAC-SHA256, and the Secret itself is not sent in plain text.

Test the connection#

Click Test connection. The test signs one read-only request with your API Secret and lists orders with GET https://app.shippingeasy.com/api/orders?per_page=1 — just 1 order as a probe. A pass means the signed credentials work and can list orders. It does not prove anything else: it does not check rates, buy a label, or look up tracking, because this connection does not offer those features.

Mapping / pick a template#

There is no mapping and no template to pick for this connection. It does not pull orders into another system and it does not map services for shipping: under the ShippingEasy Customer API, rate shopping, label buying, and tracking lookup by tracking number are not supported through this connection, so there is nothing to map for them. If you need rates or labels, do that work in ShippingEasy itself.

Activate#

After activation, the connection is saved as verified and is ready for credential checks. Nothing else starts running through it: rate shopping, label buying, and tracking lookup are not part of this connection, so keep doing those in ShippingEasy itself. If you replace the API Key or API Secret in ShippingEasy, update both values here and test again.

FAQ#

Test fails with 401

The API Key or API Secret is wrong, or the two were swapped, so the HMAC-SHA256 signature does not match and ShippingEasy rejects the signed probe.

Go back to ShippingEasy → Settings → API Credentials (app.shippingeasy.com/settings/api_credentials), copy the API Key into the API Key field and the API Secret into the API Secret field exactly as shown on that same page, then test again.

Test says credentials are missing

One or both fields are empty. The test cannot sign a request without both the API Key and the API Secret, so it stops before the probe runs.

Fill in both fields from the same Settings → API Credentials page, save, and test again. Filling in only one of the two is not enough.

Test passes, but I cannot shop rates, buy a label, or look up tracking

That is the scope of this connection, not a failure: it only verifies credentials. A passed test only proves the signed credentials can list orders — the ShippingEasy Customer API does not give this connection a rate endpoint, a label-buying endpoint, or a tracking-by-number endpoint.

Use this connection for credential checks only, and keep doing rates, labels, and other shipment work in ShippingEasy itself. Do not expect a passed test to enable those features in Integration.