# Using the API

In this article:

# RESTful web API

Our RESTful web API enables you to access resources in Cognite Data Fusion. To read or write to a resource, you construct requests that look like this:



  • HTTP method - The HTTP method used on the request to Cognite Data Fusion.
  • {version} - The version of the API your application is using.
  • {project} - The project identifier for the resources in Cognite Data Fusion that you're referencing.
  • {resource} - The resource in Cognite Data Fusion that you're referencing.
  • query-parameters - An optional set of parameters to modify the request or response.

When you make a request, Cognite Data Fusion returns a response that includes:

  • Status code - An HTTP status code that indicates success or failure.
  • Response message - The data that you requested or the result of the operation. The response message can be empty for some operations.
  • Pagination - If your request returns a lot of data, you need to page through it by passing the value of nextCursor as the cursor to get the next page of limit results. For details, see Paging.

# HTTP methods

Cognite Data Fusion uses the HTTP method on your request to determine what your request is doing. The API supports the following methods.

Method Description
GET Read data from a resource.
POST Create a resource, or perform an action.
DELETE Remove a resource.
PUT Replace a resource with a new one.
Standard Method HTTP Mapping Required HTTP Request Body HTTP Response Body
Create POST <collection URL> Yes Resource list Resource list
List GET <collection URL> Yes N/A Resource list
Filter POST <collection URL>/list No Filter object Resource list
Search POST <collection URL>/search No Fizzy search for objects Resource list
Get GET <collection URL>/:id No N/A Resource
Retrieve POST <collection URL>/byids No List of IDs Resource list
Update POST <collection URL>/update No Resource list Resource list
Delete POST <collection URL>/delete Yes List of IDs N/A

# Version

See API versioning to learn more about supported API versions, our policy for backwards compatibility, and the end-of-life schedule for our APIs.

# Project

Projects are used to separate customer environments from one another, and all resources in Cognite Data Fusion are linked to a project. A customer can have one or more projects. The project object contains configuration for how to authenticate users.

Automatically assigned object ids are unique only within each project.

# Resources

Your URL will include the resource or resources you are interacting with in the request, such as assets, files, events, and timeseries.

For more information about resource types, see About resource types and the resource reference topics.

# IP addresses for the API

The IP addresses for our APIs are not static and will change as we evolve our architecture and extend our service offerings. We will do our best to keep the changes to a minimum.

If you want to limit outbound traffic to api.cognitedata.com only, the IP addresses for the current and future APIs are:

# Other IP addresses

Some of our API endpoints, such as the Files endpoint, return a link to a Google Cloud resource. This is important to ensure that uploads fully leverage the Google Cloud services as efficiently as possible.

To fully use all our API endpoints, most importantly Files, you must also open up for certain Google Cloud IP addresses. Google publishes a list of these IP ranges through DNS: https://cloud.google.com/compute/docs/faq#find_ip_range (opens new window).

Because Cognite Data Fusion resides on the Google Cloud, you will also open for our API endpoints when you open for the Google Cloud IP ranges.

Last Updated: 8/10/2020, 12:03:23 PM