Skip to main content
Read access to your Octolane CRM. Each object (Accounts, Contacts, Opportunities) has two endpoints:
  • A simple list endpoint (GET) with basic text search and cursor pagination.
  • A search endpoint (POST) with full filtering, sorting, field selection, and cursor pagination.

Base URL

Authentication

Every request must include the API key in the x-api-key header.
Find your API key in Settings → Integrations → API.

Endpoints

Shared concepts

Filters

Operator reference and aliases used in every POST .../search endpoint.

Cursor pagination

How to paginate GET and POST endpoints safely.

Field selection

Every list and search endpoint accepts a fields parameter to return only the fields you need. Pass a comma-separated string (for GET) or a JSON array (for POST).

Custom fields

Every response includes a custom_fields object on each record and a top-level custom_field_definitions object describing those fields.
The keys in custom_field_definitions match the keys in custom_fields, so clients can resolve slug/value mappings dynamically.

Need help?

Email one@octolane.com. We ship custom endpoints when teams need something specific.