Articles in this section

Set up a connection to Deposco

Deposco is a cloud-based supply chain and omnichannel fulfillment platform that helps retailers, distributors, and 3PLs manage inventory, warehouse operations, orders, and fulfillment across multiple locations and sales channels.

Important

The Deposco connector is in BETA and may be subject to changes.

Set up a connection

After you start the connection, configure it in the Create connection panel and complete all of the required * authentication settings:

Setting Instructions
Name your connection *

Enter a clear and distinguishable name.

Throughout integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account.

Region *

Select your Deposco account region:

  • North America: if your account URL begins with https://api.deposco.com/.
  • UK and EU: if your account URL begins with https://api.eu.deposco.com/.
Client ID * Enter your Deposco client ID. For more information on retrieving your client ID, see Create an application.
Client secret * Enter your Deposco client secret. For more information on retrieving your client secret, see Create an application.
Multiple layers of protection are in place, including AES-256 encryption, to keep your connection’s client secret safe. When editing this form later, you must enter this token again; it is stored only when the connection is saved and never displayed as text.
Refresh token *

Enter the Deposco refresh token. For more information on retrieving your refresh token, see Install the application.

integrator.io uses the refresh token, client ID, and client secret to request an access token from https://auth.deposco.com/oauth2/token. The access token is valid for one hour. When it expires, integrator.io uses the refresh token to request a new one.

The refresh token remains valid until the application is updated in the Deposco developer portal.

Multiple layers of protection are in place, including AES-256 encryption, to keep your connection’s refresh token safe. When editing this form later, you must enter this token again; it is stored only when the connection is saved and never displayed as text.

Tip

This connector documentation describes only the settings shown for the Simple view. For the corresponding HTTP settings, see the Token auth universal connector documentation.

Additional reference