This BlueX Freight Commerce Platform (FCP) API document explains our various product offerings through API integrations. The API supports carrier port pairs, schedules, and spot rates, and enables users to search for rates and book via a Deep Link provided by the API.

We are actively working on supporting further carrier API integrations, along with more new features, such as inventory management, instant booking, and many more.

BlueX presents data via an HTTP API using JSON serialization and is protected with JWT. Please first click "Getting Started" to get onboarded and collect your API key.

Please use https://api.bluextrade.com for production and https://sandbox-api.bluextrade.com for sandbox API calls.

All notable changes to this project will be documented in this section.

Added

• Pricing transparency fields, e.g. surcharges, tieredSurcharges, includedSurcharges, and notApplicableSurcharges.

Changed

• Storing price in string type instead of float for better accuracy.
• Move freeTime from containerPrice to offer.

Added

• Surcharge charge types: PREPAID and COLLECT.

Added

• Show price commodity: GDSM, GARMENT and FURNITURE.

Added

• /v2/auth for getting Token V2
• /v2/rates for querying rates with Token V2

Added

• Inventory of 40GP and 40HQ.
• Show depot free times if data is available.

Before using the BlueX FCP API, please first register as a developer on our registration page. The BlueX team will review your application, and once your registration is confirmed, you will receive an API key and onboarding information for your developers.

Our API is accessible over HTTPs and returns JSON responses, and can only be accessed through BlueX provided API keys and tokens. When customers or third-party service providers access the BlueX FCP services via APIs, they are required to provide their API keys during the onboarding process.

Before accessing the API, clients must have an API key. The API key is obtained offline and identifies who the client is.

This section's Token will be obsolete soon. Please use Token V2 instead.

The client calls HTTP GET /v1/auth?api-key=[api key]&referral-user=[referral user] with a valid API key and a referral user string. The referral user is a string can identify the user who invokes /v1/auth/ with the API key. Both the api-key and referral-user are required. /v1/auth will return a JSON response. The token is in the "token" field of the response.

This is an example of the response:

{
  "token": "eyJhbGciOiJI...W0ossH6uE"
}

The token is a JWT token. To access all APIs (except /v1/auth), the client must put the token in the HTTP header. Here is an example.

Authorization: Bearer eyJhbGciOiJI...W0ossH6uE

The system will verify if the token is issued by the system or if the token is expired. The client request will be rejected if the token does not pass the verification process.

Token Refresh

The tokens issued by the system will be expired automatically. A token will expire one day after it is issued. The client can obtain a new token by calling /v1/auth with the API key or calling HTTP GET /v1/refresh_token. The response of /v1/refresh_token is the same as /v1/auth.

Token V2 introduces a mechanism to allow users to act on behalf of their customers. Users may use Token V2 to search for schedules and query rates through APIs similarly to how customers did so on the CarrierX platform (the CarrierX platform is the white-label software solution developed by BlueX Trade, which provides digitalized container solution and trade services).

To use Token V2, customers need to generate a Carrier API Key (including the API Key ID and the API Secret) from the CarrierX platform and send/delegate the Carrier API Key to API users.

The client calls HTTP POST /v2/auth with a valid API key, a valid referral user string and delegated carrier API keys. The token is then returned in the token field of the response.

$ curl -fsSL \
  --header 'Content-Type: application/json' \
    --request POST \
    --data '{"api_key":"USER_API_KEY","referral_user":"XYZ","user_carrier_api_key":[{"carrier":"EGLV","id":"CARRIER_API_KEY_ID","secret":"CARRIER_API_SECRET"}]}' \
    "https://sandbox-api.bluextrade.com/v2/auth"

{"token":"eyJhbGciOiJIUz...BbBJBXY"}

The token is a JWT token. To access all APIs (except /v2/auth), the client must place the token in the HTTP header. Here is an example:

Authorization: Bearer eyJhbGciOiJIUz...BbBJBXY

The system will verify if the token is issued by the system or if the token was expired. The client request will be rejected if the token does not pass the verification process.

Token Refresh

Tokens issued by the system will expire automatically. A token will expire one day after it is issued. The client can obtain a new token by calling /v2/auth with the API key or calling HTTP GET /v1/refresh_token. The response of /v1/refresh_token is the same as /v2/auth.

To authenticate in the JWT bearer flow, you will need to obtain a JWT containing data on the authentication request, before exchanging it for an access token.

The "Rates" API supports features for customers to receive container information and spot rates. Customers can also receive information from ocean carriers about service routes, vessel/voyage, and container types.