Starting on June 25th, 2018, Dsco will begin migrating accounts currently connecting to the https://api.dsco.io endpoint to a new endpoint, https://apis.dsco.io. Accounts will have until September 30th, 2018 to migrate to the new endpoint. The documentation below has been updated to reflect the endpoint URL change. Go here for more information on the endpoint migration.
A developer performing an integration using the Dsco API needs to first consider the following...
1. Accessing the APIs
The APIs are hosted here: https://apis.dsco.io/docs/
The current version of the APIs is V2 located here: https://apis.dsco.io/docs/v2/.
The previous deprecated version of the APIs, V1, is located here: https://apis.dsco.io/docs/v1/.
2. Retailer or Supplier
Are you acting as a Retailer or a Supplier when invoking the Dsco APIs?
Your account was assigned either a Retailer or Supplier role when it was setup and the required params for the APIs can differ depending on your Account Role.
It's possible that both a retailer and supplier account were created for you. When interacting with the APIs, you will need to use the correct account depending on what you are trying to do.
A supplier account commonly will want to acknowledge orders, change order statuses, add shipping/tracking information to an order, etc.
A retailer account will often want to create orders, check on order statuses, get order tracking information, etc.
3. OAuth Security
You will be provided an OAuth security token which will need to accompany each API call as an http header - more on this later. For now, make sure you have one for your account.
If you don't have one, please email us at support@dsco,io and title your email, "Need Oauth Token". Make sure to include the name of your organization and your account information in the body of the email.