All Collections
Other CargoAi Products
CargoCONNECT
All APIs
Best practices for testing our CargoCONNECT APIs
Best practices for testing our CargoCONNECT APIs

How can you test our APIs?

Remi Giudicelli avatar
Written by Remi Giudicelli
Updated over a week ago

Our success story relies not just on a great product. ​We understand that there is never a downtime in the air cargo industry, which is why integrating CargoCONNECT into your system can begin as soon as you create a RapidAPI account. ​It takes only a few minutes to set up your dev environment. ​

Testing our APIs on RapidAPI is very easy:

1. Sign-up for the BASIC Plan of the API, which you would like to test - available on Rapid API under the Pricing tab (https://rapidapi.com/organization/cargoai).

2. After signing up, you can access your API key and start testing:

  • For Schedule & Rate API:

    We recommend to start testing with the mock airline to get acquainted with the structure of the API.

    These are the following destinations which can be tested with the mock airline:

    • CDG

    • MIA

    • MNL

    • MAD

    • ATL

    • FRA

    • JFK

    • CRK

    • CEB

    • BOM

    • HKG

    • DPS

    • AMS

    • LAX

    • CAN

    • BKK

    • DFW

    • DXB

  • For Track & Trace API: You can test the API with 3 test AWB for status / event code testing:

    000-99999992 mock-canceled
    000-99999981 mock-intransit
    000-99999970 mock-delivered

3. If you want to start using the Schedule & Rate API with live data, the IATA CASS needs to be configured:

  • You can start testing with live data with the first paid plan

  • We recommend to move to live data only once you have completed the testing process with mock data and understand the structure of the API

  • Please, contact support+rapidAPI@cargoai.co and provide the below information on user level:

    We will not accept generic email addresses.

    RapidAPI account / Country / Origin Station / IATA-CASS Number / Contact Email on User level / Contact Phone
    1 `
    2
    3 etc.

Happy testing!

Did this answer your question?