The Content1 API 2.0 allows anyone to read public item data from the Item Management platform via an M2M API. This is essentially a READ API for the Item Management platform.

Note: The documentation for Content1 API can be found under IM Read API 2.0.

The Content1 API 2.0 supports the following output formats.

• JSON

The following are supported via the Read API 2.0

• Searching can be done by
  • GLN (Information Provider)
  • GTIN
  • Last Changed Date
  • Target Market

The Content1 API 2.0 is used by anyone to see item data published to a public GLN.

• Suppliers who wish to increase the reach of their item data can publish to a public GLN which is available to any subscriber of that public GLN.
  • This is used by anyone to see item data published to a public GLN.
  • This is visible in Item Management as the following GLNs
    • Production
      • 1WorldSync Content1
      • GLN = 0838016003360
    • Pre-Production
      • 1WorldSync Content1
      • GLN = 0838016003353
  • If a supplier wants to make their item data available to anyone with access to the 1WorldSync Content1 platform, they would publish to the Content1 public GLN
  • If a recipient (or supplier) wanted to see all of the item data published to the Content1 public GLN, they would request an appid for the public GLN for Content1 (as above).

The Content1 API 2.0 is a new implementation of the 1WorldSync’s Content1 API (previously know as the Marketplace API). The new API was released in April 2023 to existing and new users of the Content1 API in Beta. Please note the API is production ready, but will remain in Beta status until the previous version is sunset in early 2024 (final sunset date has not been set yet). 

What are the differences between the original API and the new API? The original API had some limitations which the new API aims to address.

Original API

• Roughly based on the existing GDSN standard, but did not strictly follow this standard
• Include some, but not all GSDN attributes
• Did not include 1WorldSync Top Off attributes
• Large databases could take some time to read due to the Search then Fetch architecture
• Supported a recipient model – suppliers had limited support to read their item data

New API

• Based on the 1WorldSync data model to more closely match attribute names and structure as it appears in Item Management
• Includes all GDSN attributes
• Includes all 1WorldSync attributes
• Larger databases can be read much more quickly (10x throughput increases)
• Natively supports Suppliers as well as Recipients and Distributors
• The existing HMAC based key and secret mechanism will be used for now. This could change in the future to include a bearer token mechanism. For the time being, to simplify migration for existing users, we will continue to support this method.

At some point in the future all existing users of the current Content1 API will be required to migrate to the new Content1 API 2.0. Dates for this have not been finalized yet. This will be dependent on and in collaboration with feedback from current users.

If you are an existing Content1 API customer you may request early beta access by clicking here .