Lookup tables

Read and maintain your tables

Lookup tables hold shared data such as account owners, territories, and routing rules. The API lets your applications read and maintain the same tables your workflows use.

Create a key and follow the quickstart, or try a request in the Playground. Read operations, including POST queries, do not change data. Write operations require Read & write permission.

Endpoints

Use https://api.neondeerdata.com with an Authorization: Bearer <API key> header. The key's saved table and field permissions apply to every request.

Method	Path	Reference
GET	/v1/lookup-tables	List tables
GET	/v1/lookup-tables/{table_id}	Get a table
GET	/v1/lookup-tables/{table_id}/rows	List rows
GET	/v1/lookup-tables/{table_id}/rows/{row_id}	Get a row
POST	/v1/lookup-tables/{table_id}/rows/query	Query rows
POST	/v1/lookup-tables/{table_id}/rows	Add a row
PATCH	/v1/lookup-tables/{table_id}/rows/{row_id}	Update a row
POST	/v1/lookup-tables/{table_id}/rows/upsert	Add or update rows
DELETE	/v1/lookup-tables/{table_id}/rows/{row_id}	Delete a row

Configure tables and import data

• Table settings: create, rename, archive, or delete a table.
• Fields: maintain field definitions and workflow access.
• Workflow lookups: define how a workflow finds a row and preview its answer.
• Library and synced tables: install a starter or sync an Attio status table.
• CSV imports: upload, check, preview, apply, and follow an import.

Row permissions do not automatically grant access to table settings. Imports use the required row permissions. See permissions.

Guides

• Tables and fields: field keys, value formats, and permissions.
• Filtering: find rows with equality, membership, and combined conditions.
• Pagination: read every page or split a large read into parallel segments.

Writing rows

Use a custom table to add or delete rows. On tables synced from Attio or maintained by an app, update your own fields on existing rows; the source controls row membership and synced values. Writes affect Neon Deer lookup tables, not Attio records.

Follow the write guide for permissions, value formats, version checks, and retry handling.

Response format

A single item returns data as an object. A list returns data as an array, with pagination.next_cursor. Keep reading until the cursor is null.

Most field names use snake_case; record references use objectId and recordId. Tables, field definitions, and rows include an object identifier. Value maps and pagination objects do not. Treat IDs and cursors as opaque strings.

Use only documented parameters. A GET request can repeat fields or separate its keys with commas; other parameters appear once. Integer parameters use whole-number digits, without signs or leading zeros.

Errors include error.code, error.message, optional error.param, and request_id. Authenticated requests return X-Request-Id, Cache-Control: no-store, and rate-limit headers. Unsupported paths or methods can return 404 resource_not_found. See Errors for recovery.

OpenAPI

The public OpenAPI 3.1 document describes the schemas and accepted parameter ranges. No key is required. The document can be cached and does not carry rate-limit headers.