Connect Rithum (Dsco): orders in, ASN and invoice messages out

Get the Client ID and Client Secret for your Rithum supplier account, leave the API Base URL empty for production or fill in the sandbox address to try first, test, set up trading partner mapping, activate — orders flow in and ASN and invoice messages flow back.

The Rithum connector exchanges EDI documents with retailers through the Rithum network (Dsco API v3): order documents from your trading partners flow in and become orders, and ASN and invoice documents flow back out to those partners, with inventory exchanged through the same connection. It is not a store sign-in — everything is organised by trading partner and by document.

Prerequisites#

• A Rithum (Dsco) supplier account. The API credentials for this connection belong to that supplier account — they are not a store login.
• Your Rithum onboarding contact within reach: the Client ID and Client Secret are issued as a pair for your supplier account, and if you do not have them yet, the onboarding contact is who provides them.
• At least one trading partner (retailer) you exchange documents with on Rithum — orders in, ASN and invoices out. Each partner is mapped separately later in this guide.
• A choice of environment for the first connection: leave the API Base URL empty to use production, or fill in the sandbox address to try the connection first. The exact addresses are in the fill-in step below.

Get your credentials#

1. Look in your Rithum supplier account, in the API / developer settings, for the API credentials: the Client ID and the Client Secret. They belong to the supplier account and are issued as a pair — you need both.
2. If there are no API credentials there, ask your Rithum onboarding contact for them. Tell them you need the API Client ID and Client Secret for your supplier account.
3. Copy both values in full and save them somewhere safe. The pair only works together: a Client ID from one issued pair will not work with a Client Secret from another.
4. If the Client Secret is lost, ask Rithum to issue a new one — a lost secret cannot be recovered from the connection, because it is never shown back after you save it.

Fill it into Integration#

1. Open Integration → Connector Marketplace → Rithum → New connection.
2. API Base URL (optional): leave this field empty to use production — the connection then goes to https://api.dsco.io/api/v3. To try the connection against the sandbox first, fill in https://staging-api.dsco.io/api/v3 instead. Fill in one of these two addresses exactly, or leave the field empty — do not type an address from another system.
3. Client ID: paste the Client ID issued for your Rithum supplier account. Take care not to swap it with the Client Secret — the ID goes in this field, the secret in the next one.
4. Client Secret: paste the Client Secret from the same issued pair as the Client ID. It is encrypted at rest and never echoed back.

Test the connection#

Click Test connection. The test runs in two steps, and both must pass before the connection counts as working. First it exchanges your Client ID and Client Secret for an access token with Rithum. Then it uses that token to call the /hello check on the API address you chose — the production address when the Base URL is empty, or the sandbox address you filled in. A pass means both steps worked: your credentials were accepted and the Rithum API answered. If it fails, keep the error the test shows — it tells you whether the token step or the /hello step broke, and the FAQ below walks through each case.

Mapping / pick a template#

Mapping on Rithum is per trading partner, not one setting for the whole connection. For each retailer partner, pick that partner’s template and check how its order documents map into the standard order — order number, line items, quantities, and ship-to details — and how ASN and invoice data maps back into the document format that partner expects. A partner with no mapping set up has nowhere for its documents to land: its orders cannot come in, and ASN and invoice documents cannot be built for it. A passed connection test only proves the credentials and the API address work — it does not mean any partner is mapped yet. Work through your partners one by one, and check the mapping preview for each before activating.

Activate#

After activation, order documents from your mapped trading partners flow in and become orders, inventory is exchanged through the connection, and ASN and invoice documents are sent back out to each partner through Rithum. Partners without a mapping stay silent — nothing flows for them until their mapping is set up. If you tested against the sandbox address, switch the API Base URL back to empty (production) and test again before activating for real trading. Watch the first documents for each partner in Runs / Logs before trusting the exchange unattended.

FAQ#

Test fails at the token step

Rithum did not accept the credentials, so no token was issued and the test never reached the /hello check. The usual causes are a value copied incompletely, the Client ID and the Client Secret pasted into each other’s fields, or the two values coming from different issued pairs — the ID and the secret only work as the pair they were issued in.

Re-copy both values from your supplier account’s API / developer settings, making sure the Client ID goes in the Client ID field and the Client Secret in the Client Secret field, both from the same issued pair. If you no longer have the secret, or you are not sure which pair your values belong to, ask your Rithum onboarding contact for a newly issued pair, fill in both values, save, and test again.

Token is issued, but the /hello check fails

Your credentials were accepted — the token step passed — but the API address the connection is pointing at did not answer the /hello check, so the connection does not count as connected yet. The usual cause is the API Base URL: it was typed differently from the two addresses this connection uses, edited by hand, or left pointing at the sandbox after you meant to test production (or the other way round).

Set the API Base URL to exactly one of the two addresses: leave it empty for production (https://api.dsco.io/api/v3), or fill in the sandbox address https://staging-api.dsco.io/api/v3 if you are testing against the sandbox. Save and test again. If the /hello check still fails on the exact address, keep the error the test shows and check Runs / Logs before trying again.

Connected, but a partner’s orders never come in

The connection itself works — the test passes and other partners may be flowing. The problem is that this trading partner has no mapping set up, or you are still connected to the sandbox address while the partner is sending on production, so its order documents have nowhere to land on this connection.

First check the API Base URL: for real trading it should be empty (production). Then open the mapping for that trading partner, pick its template, and check the mapping preview with one of its real order documents — order number, line items, quantities, and ship-to details should all land in the standard order. Save the mapping, then check Runs / Logs for that partner’s next document.

Orders come in, but ASN and invoice documents do not reach the partner

Inbound is working, so the credentials and the API address are fine. The gap is on the outbound side of that partner’s mapping: the partner is mapped for order documents in, but its ASN and invoice documents out were never set up, so the fulfilled results have no document to travel back in.

Open that trading partner’s mapping and set up the outbound side as well: ASN documents and invoice documents, in the format that partner expects. Check the mapping preview with a fulfilled order, then watch Runs / Logs for the next outbound document to that partner.