Connect Ordoro: verify your API credentials
Create an API key in Ordoro under Settings → Account Settings → API Keys, paste its Client ID and Client Secret into Integration, and test — the test uses HTTP Basic to list your shippers read-only and confirm the credentials work.
This Ordoro connection verifies that your Ordoro API credentials work in Integration: it checks the Client ID and Client Secret of an Ordoro API Key over HTTP Basic and reads your shipper list. Keep the scope in mind — this connection is for credential verification only. It does not shop rates, buy labels, or look up tracking by tracking number, because in Ordoro rates and labels run through per-order endpoints. A passed test proves your credentials are usable, and nothing more.
Prerequisites#
- An Ordoro account you can sign in to, with access to Settings → Account Settings → API Keys.
- Permission to create an API key on that page. One key gives you both values you need: a Client ID and a Client Secret.
- Do not plan to use your Ordoro sign-in email and password here. That way of signing in to the API has been deprecated by Ordoro and will not work in these fields — see the first FAQ entry.
Get your credentials#
- Sign in to Ordoro and go to Settings → Account Settings → API Keys.
- Create an API key on that page.
- Copy the Client ID of the key you just created. This Client ID is the username for HTTP Basic authentication.
- Copy the Client Secret of that same API key, and save it somewhere safe. This Client Secret is the password for HTTP Basic authentication, and it must come from the same key as the Client ID above.
Fill it into Integration#
- Open Integration → Connector Marketplace → Ordoro → New connection.
- API Key Client ID (client_id): paste the Client ID of your Ordoro API key — the one you copied from Settings → Account Settings → API Keys. It is treated as a secret and is never echoed back. Do not fill in your Ordoro sign-in email here.
- API Key Client Secret (client_secret): paste the Client Secret of that same API key. It is treated as a secret and is never echoed back. Do not fill in your Ordoro sign-in password here, and do not pair a Secret from a different key with the Client ID above.
- That is all — this connection has only these two fields. There is no account number, shop domain, or environment field to fill in.
Test the connection#
Click Test connection. The test first checks that both fields are filled in, then uses HTTP Basic — your Client ID as the username and your Client Secret as the password — to list your shippers read-only (GET /shipper/?limit=1). If a shipper list comes back, the test passes. Read that result narrowly: a passed test only proves the API Key credentials can sign in and read that list. It does not prove that rates, labels, orders, or tracking work through this connection. If the test fails, note the error and check the FAQ below.
Mapping / pick a template#
There is no mapping to configure and no template to pick for this connection. It does not pull orders in and does not push anything back, so there are no order fields to map. Rate shopping, label buying, and tracking by tracking number are also not part of this connection: in Ordoro, rates and labels are handled through per-order endpoints that start from an Ordoro order, and tracking information sits on the order itself. Use this connection for the one job it does — verifying that your Ordoro API Key credentials work — and handle rates and labels through the order-based flow in Ordoro.
Activate#
After the test passes, activate the connection to save it in Integration with these verified credentials, so you can test it again later with the same values. Activation does not start any data flow: no orders are pulled, no rates are quoted, no labels are bought, and no tracking is synced through this connection. If you later create a new API key in Ordoro, update both fields here with the new key values and test again before relying on the connection.
FAQ#
I filled in my Ordoro login email and password, but the test fails
These two fields do not take your sign-in credentials at all. Signing in to the Ordoro API with an email and password has been deprecated by Ordoro, so a login email in the Client ID field and a login password in the Client Secret field are rejected every time.
Go to Ordoro → Settings → Account Settings → API Keys, create an API key, put its Client ID into the client_id field and the Client Secret of that same key into the client_secret field, then test again.
Test fails with 401
Ordoro did not accept the Client ID and Client Secret pair. The usual reasons are a typing or copying error, the two values swapped between the fields, extra spaces copied along with a value, or a Client ID paired with the Client Secret of a different API key.
Open the one API key you want to use in Ordoro → Settings → Account Settings → API Keys, re-copy both values from that same key without extra spaces, make sure the Client ID is in client_id and the Client Secret is in client_secret, and test again.
The test passed, but I cannot shop rates, buy a label, or track a shipment here
That is the actual scope of this connection, not a fault in your setup. In Ordoro, rates and labels are handled through per-order endpoints, so there is no standalone rate or label call for this connection to make, and tracking information lives on the Ordoro order rather than behind a lookup by tracking number. This connection only verifies credentials with a read-only shipper list.
Treat a passed test as proof that your credentials work, and nothing more. For rates and labels, follow the order-based flow in Ordoro, starting from the Ordoro order; for tracking, check the shipping information on that order in Ordoro.
The test says credentials are missing
One or both of the two fields are empty. The test checks the fields first and reports missing credentials instead of reporting success, so an incomplete connection can never look connected.
Fill in both fields — the Client ID of an Ordoro API key in client_id and the Client Secret of that same key in client_secret — save, and test again.