Erudus API Version 2 - Now Live

Why has it taken so long to introduce API Version 2?

First things first, we know that this has taken longer than expected to get off the ground. We’d always planned to launch a new API to accompany last year’s major Erudus upgrade, one which uses all of our new attributes and features, but we wanted to take a “do it right and do it once” approach.

Essentially, knowing the importance of automating the flow of data from our Data Pool and ensuring there was minimal disruption to our Integration Partners making the switch - alongside technical roadblocks, user feedback and additional data requirements from industry that have caused changes to the data model over the last 12 months which would have caused disruption to our partners using V2 of the API meant we had to hold off until kinks were ironed out and it we had made the necessary updates for it to be worth the time and effort for our users to move over to the new API.

TLDR, We had hoped to launch API Version 2 alongside last year’s update to Erudus but it would have been too disruptive to users and we only wanted to make everyone get used to a new API once.

What is changing when it comes to API Version 2?

There are lots of positive changes with API Version 2. Here are some of the main ones:

New Attributes

Users of API Version 1 can only access data in our legacy data model (before we updated Erudus), but API Version 2 will display data using the new data model for specifications that have been updated to new specification types. These new attribute sets include:

• “Free From” Allergen Claims
• Updated Diet Suitability
• Updated Waste Packaging
• Updated Product Origin Attributes
• Updated Nutritional Attributes
• Product Specification Types
• Schema type

Endpoints & Version Control

Although Erudus now boasts a Revision & Version control feature that allows users to keep track of every version of their used products, API Version 1 has no concept of product versions and will only display the latest available version of a product specification.

API Version 2, however, uses catalogue endpoints, so API users can view the specific version of a product the Wholesaler’s product code is linked to, and they can also view a specific version of any product should they request it using product endpoints.

You can find out more about Revision & Version control here.

Managing Product Codes

Historically, Wholesalers wanting to attach their product codes to specifications in the Erudus Data Pool has always been a manual task - either for them internally or performed by Erudus via range matching. With API Version 2 Wholesalers or their internal solution providers can add and remove their product codes using the API.

API documentation is published and publicly available at developer.erudus.com for users to peruse at their leisure.

How do I access API Version 2?

Firstly, we will imminently be contacting all Wholesalers and Integration Partners to start the process of getting them migrated from API Version 1 to API Version 2. There are so many benefits to using the new API that we strongly encourage everyone to get on board with it as soon as possible.

Accessing API Version 2 requires the user to have a “token”, which can be obtained from the Erudus Support Team. They will create and distribute tokens on behalf of both Wholesalers and Erudus (for Integration Partners who have a commercial agreement with Erudus), and can be contacted via support@erudus.com and on 0333 121 89 99.

Those Integration partners that do have a commercial agreement with Erudus directly will have a single user added to Erudus with the newly created “Standard” user role. Only one API user is to be added per partner with a commercial agreement, and this will give access to Product endpoints for getting product data.

Once API access has been granted to a user, the user can access the Erudus API portal using the URL api.erudus.com and log in with their existing Erudus login details.

How long will version 1 of the API remain available after the launch of version 2?

We don’t want to pull the rug out from any of our users, and intend to give everyone time to adjust. With that in mind, we will be keeping Erudus API Version 1 running alongside Erudus API version 2 for 12 months so everyone has ample time to make the switch and test their integrations.

Officially, API Version 1 will be sunsetted on the 12th of June 2026.

Is there an online guide to API Version 2?

Yes, you can always access an online guide to Erudus API Version 2 here, at Erudus Knowledge Base.

Still got questions?

Hopefully this gives you a good amount of insight to Erudus API Version 2, but should you still have questions about the change over, you can contact Erudus Support via support@erudus.com or on 0333 121 89 99.