The Oceans 2.0 API provides public access to Ocean Networks Canada's extensive data archive, via 6* discovery, 4 data delivery and 2 interoperability web services. The API provides programmatic access to:

  1. data products, (identical to those accessed interactively using the Ocean's 2.0 Data Search interface)
  2. scalar, and raw data for near-realtime applications.

Discovery Services

A collection of services for obtaining all of the codes needed to successfully request data, via the data delivery services. The services use reductive filtering to return a list, in json format, of all of the items that meet the filter criteria defined in the url parameters. Codes returned from one service can be used in another service to refine the selection, for example, a deviceCategoryCode obtained from the deviceCategories service can be used as a filter on the locations service to find all locations that have instruments of that device category.

Data Delivery Services

A collection of services which return data from the ONC archive, including

  1. An asynchronous service: dataProductDelivery service allows large amounts of customizable data to be delivered in a variety of formats. This delivery method is both flexible and scalable, but requires additional processing time on the server. By utilizing the Task Queue framework, an asynchronous programming pattern of multiple service calls is used to return the data. 
  2. Two synchronous services: scalardata and rawdata services return data in the response payload, which supports near real-time access. Because this type of delivery method is optimized for speed, the services do not support resampling or aggregation and have a 100k record count limit.
  3. Direct file access service: archivefiles service returns archived files, using the filename, in the payload. 

Interoperability Services

A collection of services that have standardized interfaces designed for sharing and data integration.


All of the services, with the exception of the interoperability services, require the use of a method and token. Only the scalardatarawdata and archivefiles services support the responseType optional parameter. 









Each Web Service has 1 or more methods outlined in the documentation. The method name is case sensitive.




All Web Services require a token. This can be generated, after logging in at Click the "Web Services" tab, then click "Generate Token"






Valid values are "json" and "jsonp". Defaults to "json".

ONLY AVAILABLE for scalardatarawdata and archivefiles services

responseType =jsonp

Request Format

All web service are method oriented and use the following Url pattern:[SERVICE_NAME]?method=[METHOD_NAME]&token=[YOUR_TOKEN_HERE]



Please report all issues with the web services, documentation, samples and client libraries to the Oceans 2.0 Help Centre