Migrating your Dsco API Credentials to OAuth in Syncware

On October 1, 2026, Rithum is retiring static Auth Bearer Token credentials for the Rithum | Dsco API. If your Dsco integration is managed through the Syncware application, you must create Client Credentials (OAuth2) in the Rithum | Dsco platform and update your Dsco Integration configuration in Syncware before that date. Integrations still using an Auth Bearer Token on October 1, 2026 will stop working, and all remaining Auth Bearer Tokens will be deleted.

Before you begin

• Confirm your account currently uses an Auth Bearer Token. If you are not sure, check with your tech team or your API provider.
• You need permission to create API credentials in the Rithum | Dsco platform. Access is available from Automation → API.
• You need access to the Dsco Integration configuration in the Syncware application.
• Plan to complete Part 1 and Part 2 in the same session. Your integration continues to run on the existing Auth Bearer Token until you save the new OAuth credentials in Syncware.

Part 1: Create new API credentials in Dsco

Step 1: Log in to the Rithum | Dsco platform and navigate to Automation → API.

Step 2: On the API page, click Create Credentials.

Step 3: In the Create Credentials pop-up, complete the following fields:

1. From the API Credential Type drop-down menu, select Client Credentials (OAuth2).
2. In the Name field, enter a name for the credential. This field is optional, but a descriptive name such as Syncware OAuth makes the credential easier to identify later.
3. In the Description field, enter a description for the credential. This field is optional.

Step 4: Click Create & View Credentials.

Step 5: Copy the Client ID and Client Secret that are displayed and store them securely. Then click Close.

Note: The Client Secret is sensitive information and is displayed only once. Do not share it through unsecured channels such as email or chat. If you lose the Client Secret, create a new credential set and repeat this procedure.

Part 2: Update the Dsco Integration in Syncware

Step 1: In the Syncware application, open your Dsco Integration configuration.

Step 2: Enable Use OAuth Authentication. This setting must be enabled before you enter the new credentials.

Step 3: Complete the following fields:

1. In the Client ID field, enter the Client ID you generated in the Rithum | Dsco platform.
2. In the Client Secret field, enter the Client Secret you generated in the Rithum | Dsco platform.

Step 4: Save the Dsco Integration configuration.

Part 3: Confirm the migration and remove the old token

Step 1: In Syncware, run a connectivity test or allow a scheduled sync to complete, and confirm the Dsco Integration is transmitting successfully. Refer to Manually Running an Action for steps.

Step 2: Review recent order, inventory, and shipment activity to confirm data is flowing as expected.

Step 3: Return to the Rithum | Dsco platform, navigate to Automation → API, and delete the Permanent Bearer Token that was previously used. Refer to Managing your API credentials for steps.

Note: Do not delete the Permanent Bearer Token until you have confirmed the OAuth connection is working.

Frequently asked questions

What happens if I don't migrate before October 1, 2026?

Your Dsco API integration will stop working. Rithum deletes all remaining Auth Bearer Tokens on October 1, 2026, and any request that uses one is rejected after that date.

Can I just create a new Auth Bearer Token instead?

No. The ability to generate new Auth Bearer Tokens was removed from the Rithum | Dsco platform on April 30, 2026. Client Credentials (OAuth2) is the only credential type available.

Do I need to change any code?

Not if Syncware manages your Dsco integration. Syncware requests and refreshes the access token for you once Use OAuth Authentication is enabled and the credentials are saved. If you also call the Rithum | Dsco API directly from your own systems, those calls need to be updated separately. Refer to the Authentication and Get Access sections of the Rithum API documentation.

How long is an OAuth access token valid?

Access tokens generated through OAuth2 expire after 60 minutes and must be renewed. Syncware handles this renewal automatically.

Will my integration go down during the migration?

No. Your existing Auth Bearer Token keeps working until you save the new OAuth credentials in Syncware, and the switch takes effect as soon as the configuration is saved.

I'm not using my Dsco API integration anymore. Do I need to do anything?

Yes. Log in to the Rithum | Dsco platform and delete the Permanent Bearer Token for security purposes. Refer to Managing your API credentials for steps.