Skip to main content

Authentication

MetService uses two primary methods for managing API access, depending on which product you are using.

Future State

We are currently working towards consolidating all Core and Classic APIs into a single self-service Developer Portal. In the meantime, please follow the specific access method for your product below.

Point Forecast API

Access is managed via the self-service Point Forecast Console. Register and manage keys automatically. Login to Console

Nowcast, Tide, Aviation, & 1-Min Obs APIs

Access for these Core and Classic APIs is managed via a manual review process. Request Access

Technical Implementation​

Header Authentication​

The authentication header you must use depends on whether you are calling a Core API or a Classic API.

Core APIs​

Core APIs take your API key in the standard Authorization header, using the Bearer scheme.

Header Name: Authorization
Value: Bearer YOUR_API_KEY

Example: Core API cURL Request
curl -H "Authorization: Bearer YOUR_API_KEY" "https://api.marine.metservice.com/tide/v4/health"

Classic APIs​

Classic APIs use one of two legacy headers: apikey or x-api-key. Please check the individual Classic API's guide in the API Catalog to confirm which header to use.

As a quick reference:

  • 1-Minute Observations API: apikey
  • Aviation API: apikey
  • Lightning API: x-api-key
  • Point Forecast API: x-api-key
Example: Classic API cURL Request (Aviation)
curl -H "apikey: YOUR_API_KEY" "https://api.metservice.com/aviation/v1/health"

Trial Access​

MetService can provide API trials for evaluation periods. At this time, trial access is only available for commercial or pre-commercial purposes. However, we are actively working to provide a free access tier for everybody in the future.

When a trial expires, the key will return a 401 Unauthorized error. See Error Handling for more information.