API Keys & Usage


Each paid account is associated with an API Key, which has a set number of requestable "rows" per month.
The row usages reset on the day that the account subscription renews.

Each API route requires that you send your API key in either the query parameters under api_key, or in the headers under X-API-KEY.

What counts as a row?

A "row" is a unique entity or relationship returned.

For example, the response below has 3 unique nodes and unique 2 edges, which means this would be 5 rows:

Each API response returns a rows_returned key which indicates exactly how many rows were billed for the request.

Request limits / Insufficient Rows

Permission to make a request is based on the maximum possible rows returned from a request.


For example, if an /api/entities request has a specified limit=10000, the API Key must have 10,000 rows available, regardless of how many rows the request will actually return.

That said, you will only ever be billed for the rows actually returned in the response.


For this reason, request limits are set low by default, and it is recommended to set the limit according to how much data you wish to receive.


This is more complex with the connection and pathfinding routes.


With connection_limit=10, permission to make this request requires that the user have 10 connections worth of rows, or 30 rows.


With path_limit=10, permission to make this request requires that the user have 10 paths worth of rows, or ~190 rows.