This portal is your starting point for connecting to our APIs. We've tried to make working with our APIs as straightforward as possible:
we support a range of industry standard formats that should make it possible to seamlessly incorporate our APIs into your existing IT infrastructure.
Getting started
To get started on the Expert API platform:
1. Identify the API you want to use.
2. Create an account in order to receive an authentication token for our testing environment.
3. Read the implementation guide on this page so you can select the best data format for your specific situation.
4. Develop the logic to send or receive the data for the API you want to use. You can use the playground to test your code.
5. Test your logic together with Expert.
6. Once everything is ready request a production API token to be able to use the production version of our APIs.
Authentication
When you create an account you will get access to an API token. You use that API token to communicate with our HTTPS based APIs.
Regenerating keys
API tokens are sensitive information. To keep these secured we encourage you to regenerate these at least once every 6 months.
The API tokens are created so that you can change them in two-steps which prevents any downtime.
The API tokens are made up of two parts, separated by a comma. When we validate an API token we first check the first part, if that's not correct we check the second part.
You can chose to regenerate the first or the second part of the token. If you only change one of the parts your existing tokens will keep working.
The process to change your token looks like this:
1. Regenerate the first part of your token.
2. Change the token in your configuration.
3. Regenerate the second part of the token.
4. Change the token in your configuration.
Implementation Guide
These guides will help you implement a specific data format. Use these guides in combination with the specific documentation for the API you want to use to get started quickly.
Data Formats
XML
XML (eXtensible Markup Language) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. This format is indicated with a "Content Type: text/xml" HTTP header.
SOAP
SOAP (Simple Object Access Protocol) is a specific protocol for sending XML data that is supported by most major software stacks. This format is indicated with a "Content Type: text/xml" HTTP header and a "SOAPAction" HTTP header.
JSON
JSON (Javascript Object Notation) is a data format based on the popular programming language Javascript. This format is indicated with a "Content-Type: application/json" HTTP header.
Receiving Data From Expert
You will have to chose how you want to receive data from Expert: do you want to call us (pull) or should we call you (push)? In the pull scenario you will have to implement a process on your end that periodically
checks for messages from Expert using the Receive Message API. In the push scenario we call a configurable URL on your end with the data you want to receive.
The pull scenario is more robust since you decide when you are ready to process messages. The push scenario is simpler
because you don't have to build a process that runs periodically and creating a webservice is supported in all platforms and most systems from SAP, Oracle, Microsoft etc.
It's up to you which model you pick based on your specific IT landscape. Once you've decided on the model you can chose from the 3 data formats we support: XML, SOAP or JSON
Playground
Loading
The message was sent succesfully.
We will show you if the message was sent succesfully here.