Salsify APIs: Developer Resources

The API section has moved to its own dedicated space. Please visit https://developers.salsify.com for API documentation and endpoint reference.

Articles

Getting Started: API Authorization
In order to call any Salsify APIs , you must provide your authentication token. The auth token is specific to a user account (not an organization). Treat this token as you would your own personal password -- don't send it to anyone, and make...
Authenticating with Salsify via OAuth 2.0
Overview There are two ways to authenticate with the Salsify API: authentication via OAuth 2.0 and authentication by passing HTTP  Authorization   headers.   We also support passing the authentication token via an access_toke...
Integration with Salsify
Overview Salsify provides access to portions of our API to customers that wish to do an integration. In general, there are three primary ways to get product data out of Salsify programmatically: Using the Product CRUD API Creating a &ldquo...
API Rate Limiting
In order to provide a quality experience for all users, Salsify has put limits in place for API requests. Rate limiting for Salsify APIs is on a per user token basis. Each user is allowed 5000 requests per hour, which includes all authenticated ...
Basic Product CRUD API
Updates have been made to include organization ID in the URL path as of April 2017. This is the preferred method, but previously-working methods will continue to function as expected. Overview The product CRUD API is a REST API supporti...
Property CRUD API
List of Operations The property API is a REST API supporting the following actions and endpoints: Fetch a single property - GET https://app.salsify.com/api/v1/orgs/< org_ID >/properties/< property_id > Fetch multiple properties - RE...
JSON Import Format
Overview The high level structure of the JSON document is: Version 1: 2013-04 Version 2: 2 [ { "header": { } }, { "attributes": [] }, { "attribute_values": [] }, { "products": [] } ] ...
Imports API
Updates have been made to include organization ID in the URL path as of April 2017. This is the preferred method, but previously-working methods will continue to function as expected. Overview Imports are designed to get your data into our sy...
Ephemeral Exports API
Updates have been made to include organization ID in the URL path as of April 2017. This is the preferred method, but previously-working methods will continue to function as expected. Overview Ephemeral exports are designed as data dumps from t...
Digital Asset CRUD API
Updates have been made to include organization ID in the URL path as of April 2017. This is the preferred method, but previously-working methods will continue to function as expected. List of operations The digital asset API is a REST API s...
Product Change Webhooks
Products are serialized using the product CRUD API JSON export format.   Click here for more information on format. Products that have been destroyed will have salsify:destroyed_at property with the date of their delete. parent_produc...
Single Sign-On with Salsify
With single sign-on (SSO) in Salsify,  users can login using their existing corporate credentials for login.   With single sign-on, you’ll: Provide a better user experience for your users.  They’ll only need to remembe...
Configuring AD FS 2.0 for Salsify SSO
There are three main steps to setting up AD FS 2.0. Click any of the links to move to that section of the instructions, or scroll down for full details on each. Add a new Relying Party Trust Create the Claim Rules Adjust the Trust Settings...