Container Event History
Once you have Signed Up for an account, Accepted a Plan and registered your App to generate your own API keys, you are ready to start testing our APIs. Everything you need is detailed below, starting with Step 1. Sandbox - Container Event History. Once you are satisfied with your own development and testing, migration to production can be found in Step 2. Production - Container Event History. It's here that you will learn about our OAuth 2.0 authorisation which is needed to generate a bearer token for subsequent calls. Finally, feel free to read our Open API spec found below via our Container Event History .yaml file.
Step 1. Sandbox - Container Event History
To get you started, we've created a simple GET request API for you:
- https://api-sandbox.apmterminals.com/container-event-history
To call this API, you will need to add Container numbers to the assetId query parameter, along with a Facility code, e.g. USLAX for Pier 400, Los Angeles. This API uses test data only. Go ahead and make calls using the any of the examples below;
- Test Containers = TCLU1619533, MRSU3638119, TCNU6736993, TCLU5517519, TCLU5088040
- Test Facility = USLAX
Your GET request should look something like this:
- https://api-sandbox.apmterminals.com/container-event-history?assetId=TCLU1619533,MRSU3638119,TCNU6736993,TCLU5517519,TCLU5088040&facilityCode=USLAX
Step 2. Production - Container Event History
To access our Production APIs we have a base security policy enforcing the OAuth2.0 Client Credentials Grant. This means that you must request an access token from us which is then used in subsequent calls to the APIs. The access token is added to the "Authorization" header with a "Bearer " prefix. So, the full Authorization header looks like - "Authorization: Bearer {access_token}". This access token expires after 30 minutes, so you will need to repeat this request to get a new token.
How to request an access token?
- Issue a POST request to https://api.apmterminals.com/oauth/client_credential/accesstoken?grant_type=client_credentials
- Please ensure your POST body is x-www-form-urlencoded and includes the two following key:value pairs created when you register your App
- client_id = your Consumer Key
- client_secret = your Consumer Secret
- In the response you will see a key called "access_token", this is what you will include in the Authorization header for the Import Availability API
How to access the Production Container Event History API?
As with our Sandbox API you can issue a simple GET request, to the endpoint listed below, but this time you will need to add your access token.
- https://api.apmterminals.com/container-event-history
- Headers: Authorization: Bearer Token {access_token}
The production API is connected directly to our terminal operating systems for real-time data. As such, when calling this API, you will need current container IDs, along with the appropriate facility code, e.g. USLAX for Pier 400, Los Angeles. Terminal codes shown between ():
- Algeciras, Spain (ESALG)
- Apapa, Nigeria (NGAPP)
- Aqaba, Jordan (JOAQB)
- Bahrain (BHKBS)
- Gothenburg, Sweden (SEGOT)
- Lázaro Cárdenas, Mexico (MXLZC)
- Los Angeles, USA (USLAX)
- South Florida Container Terminal, Miami, USA (USMIA)
- Maasvlakte II, Rotterdam (NLMSV)
- Monrovia, Liberia (LRMLW)
- Mobile, USA (USMOB)
- Moin, Costa Rica (CRPMN)
- Mumbai, India (INNSA)
- Onne, Nigeria (NGONN)
- Pecém, Brazil (BRPEC)
- Pipavav, India (INPAV)
- Port Elizabeth, USA (USNWK)
- Tangier, Morocco (MAPTM)
- Vado, Italy (ITVDL)
- Valencia, Spain (ESVLC)
- Yucatán, Mexico (MXPGO)
| Attachment | Size |
|---|---|
| APMT Container Event History_4.yaml (9.16 KB) | 9.16 KB |