Exertis Hub On-Boarding Guide

Warranty

Exertis UK does not provide any warranty as to the availability, performance, accuracy or suitability of the API or data provided by it. Exertis shall not be liable for any loss whatsoever which might arise from the use of this API. Exertis reserve the right to change, withdraw or replace the API at any time without notice, or refuse or remove access to it. By using these APIs you agree to our standard acceptable usage policy as published at https://www.exertis.co.uk/policy-accept.php

Getting started

Before you can register with eHUB, you must first be a customer of Exertis UK.

If you are not a customer, then please use the contact us page to request an account.

Please note it can take several days to create your account, depending on the checks required.

Registration

Once you have an Exertis UK account, you can then register for eHUB access via the registration page register here.

Registration requires you to provide Contact info and details of the types of APIs required along with a SAP Account Number and Account Managers Email.

You'll receive an email confirming your request. Please allow 3-5 business days for the account to be set up, depending on the APIs you've selected.

Initially you will receive details for a TEST account.

API Consumption

Create Identity Token

To consume the APIs, you must first obtain an Identity Token.

• This is achieved by logging into the eHUB Portal as an Account Manager and clicking the button “Generate Customer Identity Token”.
• The Identity Token has a year expiry and is used to generate a Bearer Token using the authentication endpoint.
• The Bearer Token has a 15-minute expiration and must be renewed periodically.
• The Bearer Token is included in the header of every API call to authorize access to Order and Product APIs.

Renew Identity Token

To renew the identity Token

• This is achieved by logging into the eHUB Portal as an Account Manager and clicking the button “Generate Customer Identity Token”

Testing

We supply a dedicated set of test products to each new customer for evaluation purposes.

When placing orders, you will be expected to check products, using the get catalogue endpoint (which provides you with sku codes, stock levels and pricing) and use the sku to place orders.

We suggest placing several orders, a couple that test the success path, plus a couple of orders that test the failure paths.

When an order fails, you will be returned a 40x response, with an overview of the issue. you will be expected to handle this issue, fix, and then resubmit.

Examples

Error Type	Error
Duplicate Order Ref	40x response
Missing Order Information. (Price, SKU, QTY)	40x response

For each successful order placed, you will need to poll the status endpoint at regular intervals until it is dispatched, for the following error conditions:

Error Type	Error
Invalid SKU code	order_sub_status = MISSING_DATA
Backorder	order_line_status = BACKORDER NOTE: You may need to ask support to trigger this scenario.

Exertis will not hold / process any failed orders.

Successful orders will be received into the PENDING status. at this point, you will need to contact support and ask them to move the orders on - so that you can then start testing the Status endpoints.

Once you have completed several tests, we can then proceed to putting your account live.

Go Live Process

Once testing has been successfully completed, you will need to ask support to create a production account. this account is separate from your test account and will use a different Identity token.

Again, it may take a couple of days to setup your account, depending on your pricing structure.

Once setup, and orders sent to this account will be fulfilled, and would be difficult to intercept – so please do not send test orders through to your production account.

Error Handling

From time to time, you may have to deal with errors, when making requests on the Exertis API. These can be categories as follows:

• Content error – Invalid content in the API request.
• Network error – Intermittent communication problems between client and server.
• Server error – A problem on the Exertis servers.

You should be expected to handle errors and ideally have a retry process in-place.

Error Codes

Exertis uses HTTP response status codes to indicate the success or failure of your API requests. If your request fails, Exertis returns an error using the appropriate status code.

In general, there are three status code ranges you can expect:

• 2xx success status codes confirm that your request worked as expected
• 4xx error status codes indicate an error because of the information provided.
• 5xx error status codes indicate an error with Exertis’ servers.

If this does not help resolve the issue, then please contact us.