Integration

Accounts

In Shiptify, data is inextricably linked to an account. Each account is either:

  • Shipper : this type of account owns orders, shipment requests, shipments (tracking) and invoicing.

or

  • Carrier : this type of account aznswers and manages the shipment requests. It can access data from dedicated shipments of its clients (shippers).

All shipments belong to one shipper account. They can be made visible to other accounts (either carrier or shipper). An account is usually the extent of a dedicated team of transport professionals.

Users

A user from the platform is closely interelated to one or several accounts which have:

  • the same domain (ex : deachelle.com)

and

  • the same type of account: shipper or carrier

If you need to test both sides from the API, you will be requested to provide us with two different users.

The API key we deliver is attached to a user. So if you generate a shipment via the API, the owner of the shipment inside the platform will be your API user. That will be the same for any operations on the platform that is done thanks to the API.

A shipper gets to see all available pieces of information about his account.

A carrier has less visibility on a shipment. Some attributes of objects may not be available for the carrier (Costs of a shipment per instance).

How to check your access?

To check your credentials to SHIPTIFY APIs, you can use the hello API endpoint of API Docs in order to access the environment you are looking for (See Environment section).

  1. Select the top-right-green Authorize button. You should see this form:

  1. Write your API Key in the field Value (the prefix Api-Key is part of key value. For instance : Api-Key v54eix0u3xz0keiao4k234j0ewy601ml);

  2. Select Authorize button under the filled field;

  3. Then use hello api endpoint, select the button Try it out and Execute

You should get server response :

Code 200 : “Hello from public Shiptify API!”

Dictionnaries

On Shiptify Platform, we label dictionaries which are the list of common attributes: content type, specificities, metadatas… These dictionaries are the same for all accounts.

Before asking to create a new item in a dictionary, please check first if it’s not yet available. If you don’t find what you are looking for, our team will be happy to create a new one for you as long as it serves the community needs. Please be in touch with your sales representative to do so.

For a simpler interface on the platform, you can choose to restrain to your favorite items from dictionaries. On the API side, all items are always available. So you can access items which are out of your pre selected list from the Platform.

Tips and tricks

When you call a “get all…” request, the list of objects in the response are always listed from lower to higher ID.

Limit parameter With limit parameter, you can define the number of object you will receive in the response. Ex : if you set limit = 30, and the last shipment request id is 220, you will receive only the last 30 ID of shiptment requests’ list, from ID 191 to 220 included

Offset parameter Offset parameter introduce a lag from the last ID send in the response. Ex : if you set offset = 10 and the last shipment request id is 180, you will only receive the ID from 1 to 170

Date format All date format are a string with YYYY-MM-DDTHH:MM:SS value, in which T is a fixed separator (example: 2020-10-20T12:00:00). Dates must be set in UTC Timezone.

Last updated