1. Should I use the Content Experience Suite API?

1 Should I use the platform API?

Suppliers who are considering automating the creation of products, updates to products, and publications to recipients may consider the platform API.

Recipients who want to automate the search and retrieval of product data from their own account or from Marketplace may consider the platform API.

Things to Consider When Considering the Content Experience Suite API

• Do you have an in-house technical team that can support you during your implementation?
  • Suppliers implementing the Syndigo Platform API require the support of a technical team over approximately 16 weeks. This time frame can expand or contract based on complexity, your resource availability, and commitment to the project.
  • Recipients implementing the Syndigo Platform API require the support of a technical team over approximately 2 weeks to understand the Syndigo API and to create code to ingest product data from Syndigo. The additional time required to integrate the data into downstream systems will vary significantly based on the customer’s infrastructure but is generally between 2 and 6 weeks. This time frame can expand, or contract based on your resource availability and commitment to the project.
• If you don’t have a technical team, will your business support engaging a partner to complete the implementation?
  • You will need in-house support for API maintenance over time.
  • You will need an eCommerce representative from your company to actively participate for the length of the implementation
    • For data validation
    • To plan for the necessary business processes for ongoing success post implementation

Supplier API Implementation:

You will need to generate code to create the necessary payload structures. Many of our API clients employ middleware to create the output format needed to meet the platform API standards. Some PIMs may be able to directly create the output format necessary.

Supplier API maintenance:

• Do you have a technical team that can support recipient updates to requirements?
  • Our recipient network is vast. As such there are always updates occurring within the recipient network. After implementation, you will need to have technical resources that can support updates to attribution requirements as the recipients need.
  • You will still need to support business processes around syndication to include checking data quality before publication, monitoring for recipient updates to include new attribution, changes to existing attribution, or changes to validations, as well as checking and actioning recipient feedback post publish.

Recipient API Maintenance

• Recipients should plan for the addition of product attributes, choice values and product categories over time as data collection requirements change.