CRM for developers

Build CRM tasks into your own software

Read and update contacts, deals, and tasks from your code. Use the documented API, add custom fields, and let your team review the same records in the dashboard.

Create a workspace Connect an agent

What CRM for developers means

The term explained, followed by how it works in Agent Native CRM.

A CRM you can program

Use an API to save contact details, create follow-up tasks, and update deals from a service or script. You do not need to automate browser clicks.

A dashboard for your team

Your software and the included dashboard use the same CRM features. People can inspect and correct the records your integration creates.

What to check before you choose

For CRM for developers, check these details before connecting your team or software.

API coverage

Question to askCan I perform the actions my integration needs?

Agent Native CRMThe API covers records, activities, tasks, deals, custom fields, saved views, and access management.

Access keys

Question to askCan each integration have separate access?

Agent Native CRMIssue keys to separate people or agents and choose their workspace roles.

Custom data

Question to askCan I store business-specific fields?

Agent Native CRMAdd fields and record types through the API, then use them alongside standard fields.

Error handling

Question to askHow can my code react to a failed request?

Agent Native CRMResponses include an error code, a message, and details where available.

What you can do

Here are the actions you can take, followed by the API requests a developer or agent can use for each one.

Read the API reference

Open the API reference to see the supported requests and expected fields. The setup guide provides worked examples.

GET /v1/openapi.json
GET /v1/skill
GET /v1/health

Issue access keys

Create a separate identity for each integration or agent. Issue keys for it and revoke keys when access is no longer needed.

POST /v1/principals
POST /v1/principals/{id}/keys
DELETE /v1/principals/{id}/keys/{key_id}
POST /v1/principals/{id}/rekey

Add your own fields

Use the API to add custom fields, record types, deal stages, and status choices for the workflow you are building.

POST /v1/schema/fields
POST /v1/schema/objects
PUT /v1/schema/stages
PUT /v1/schema/status-lists/{name}

Save reusable record lists

Create a saved view with filters, sorting, and columns. Read its records to show the same list in your own interface.

POST /v1/views
GET /v1/views/{id}/records
PATCH /v1/views/{id}

Handle failures in code

Check the error code before deciding what to do next. For example, an already-claimed task should send your worker to another task.

GET /v1/companies
GET /v1/tasks
POST /v1/tasks/{id}/claim

Agent Native CRM

Use the API for updates and the dashboard for review.

How you stay in control

Choose who can change data, review important work, and correct mistakes. Some checks are built in; optional policies need to be configured.

Keep credentials on the server

An access key gives its holder the associated role. Store keys securely and avoid placing privileged keys in public browser code.

Inspect fields before writing

Read the workspace settings to see which fields exist. Requests with unknown fields are rejected with details you can use to fix them.

Match existing contacts

Company writes match the domain; person writes match email or LinkedIn URL. This helps retries update the existing record when those keys match.

Use the published request formats

The API reference is generated from the request definitions. Check it when adding an operation to your integration.

GET/v1/skill

Connection and response details

These notes explain the fields or connection settings used in this example. The setup guide includes the complete request and response formats.

Read the setup guide

GET /v1/views/{id}/records

view: The saved list’s filters, sorting, and grouping settings.
data: The records that match the view, including custom fields.
groups: Record counts for each group, when grouping is enabled.
next_cursor: A cursor for fetching the next page of results.

What you provide

Use the CRM for records and tasks, and connect the other tools your workflow needs.

Use your own application runtime

The CRM stores your data and serves requests. It does not host, deploy, or schedule the code that makes those requests.

Provide the sending service

This API does not send sales messages. Your application uses its own email or messaging service, then records the outcome.

Build the connections you need

The API lets you write integrations. It does not automatically synchronize your CRM with every other product your team uses.

Common questions

Practical answers about setup, capabilities, and what you need to provide.

Is this a service for hiring CRM developers?

No. It is CRM software that developers can use through an API to manage contacts, tasks, deals, and custom records in their own applications.

Do I need a special SDK?

No. You can make HTTP requests using your language’s usual tools. Read the API reference for request fields, authentication, and responses.

How do I authenticate API requests?

Send an access key in the Authorization bearer header. The key belongs to a workspace identity and requests are checked against that identity’s role.

Can I build a custom front end?

Yes. Your server can call the CRM API and show the results in your interface. Keep privileged access keys on the server rather than in public client code.

Related guides

Learn more about the connection options and examples that fit your work.

Start with your first contact

Create a workspace, connect your agent, and add your first contact. Choose a plan based on how many records and activity entries you need to store.

Create a workspace See pricing