Our APIs are designed to simplify integration with authoritative Panama Canal data.

Whether you're building analytics platforms, logistic solutions, or new digital services, our APIs offer consistent access to curated datasets with a high degree of reliability.

Why it matters:

• Built and maintained by the Canal?s own integration experts
• High availability through a modern cloud-based platform
• Designed for seamless connectivity with your applications

Focus on building value ? we take care of the plumbing.

 
 

Every API product comes with clear, concise, and continuously updated documentation to accelerate your development.

We include real-world examples, request and response templates, and step-by-step usage guides ? no guesswork involved.

You'll get:

• Clear descriptions of available datasets
• Sample requests and responses
• Downloadable Postman collections
• ?Try it out? options available in our Developer Portal

Everything you need to start building ? without delays.

We offer personalized onboarding and support to ensure your success with our APIs.

From first-time developers to enterprise clients, our support team helps you understand how to use our data effectively.

What we offer:

1. Direct assistance from our API experts
2. Onboarding sessions for enterprise integrations
3. Best practices and integration examples
4. Support in both English and Spanish

We?re here to help you go from idea to implementation ? faster.

Step-by-step guide to retrieve operational insights:

1. Access the Developer Portal and subscribe to the Operations API
2. Generate your Client ID and Client Secret within your app
3. Obtain a bearer token via our OpenID Connect /token endpoint
4. Use this token to authenticate your requests
5. Available endpoints:
   • /operations/v1/vessel-arrivals: Historical ETA and vessel info
   • /operations/v1/transit-count: Daily number of transits
   • /operations/v1/transit-times: Estimated durations per transit route
6. Include headers:
   • Authorization: Bearer {access_token}
   • Content-Type: application/json
7. Structure your POST body with required parameters like start_date, vessel_type, originPort, destinationPort, etc.

Useful for logistics optimization, forecasting, and maritime analytics.

Accessing Panama Canal watershed data in 7 steps:

1. Sign into the Developer Portal and select the Hydrology API
2. Register your application to obtain credentials
3. Use your credentials to get an OAuth2 bearer token
4. Make authenticated requests to:
   • /hydrology/v1/precipitation
   • /hydrology/v1/temperature
5. POST body must include:
   • locationId, startTime, endTime, and measurement details
6. The headerRequest object must be populated (example provided in documentation)
7. Results include timestamps, location metadata, and measurement units

All data reflects historical measurements and is suitable for research, environmental analysis, or water resource management.

Steps to consume historical meteorological data:

1. Join the Developer Portal and subscribe to the Meteorology API
2. Retrieve your app credentials (Client ID & Secret)
3. Generate an access token via our authentication endpoint
4. Call one of the available endpoints:
   • /meteorology/v1/temperature
   • /meteorology/v1/humidity
5. Your POST body must include device and location metadata:
   • locationId, measurementTime, measurementUnit, etc.
6. Use a valid bearer token in the Authorization header
7. All responses return structured meteorological readings

Designed to support impact assessments, planning, and environmental studies.

Step-by-step guide to access cargo volume data:

1. Log in to the Panama Canal Developer Portal
2. Subscribe to the Commercial Info API product and select a plan (Free, Basic, or Premium)
3. Copy your Client ID and Client Secret from your registered application
4. Get an access token using the /token endpoint from our Keycloak identity provider
5. Use the token to authenticate your requests (Bearer token)
6. Call the /commercial/v1/cargo-volumes endpoint using the POST method
7. Filter your query using parameters like:
   • transitDateFrom / transitDateTo
   • vesselSize, vesselType
   • lockageType

All responses are returned in JSON format. Ensure your application handles authentication token refresh logic as needed.