Affinity CRM API

What authentication does the Affinity CRM API use?

Affinity uses HTTP basic authentication with an empty username and the API key as the password, base64-encoded in the Authorization header. Through Jentic the key is stored in the vault and injected at execution time.

Can I add an organization to an Affinity list through the API?

Yes. Call GET /lists to find the target list, then POST /lists/{list_id}/list-entries with the organization_id (or person_id, or opportunity_id) to add it as an entry. Custom field values can then be set with POST /field-values.

How do I read the interaction history for an organization?

Call GET /interactions with the organization_id query parameter and Affinity returns the email, meeting, and other touchpoints captured for that organization, including which colleagues were involved. Use this to identify the strongest internal relationship before outreach.

What are the rate limits for the Affinity CRM API?

Affinity exposes the current limit and remaining calls via GET /rate-limit. Specific allowances depend on plan tier; HTTP 429 responses indicate the limit has been reached and Jentic surfaces them verbatim.

How do I subscribe a webhook through Jentic?

Run pip install jentic, search Jentic with 'subscribe to affinity changes', load the /webhook-subscriptions schema, and execute with the callback URL and event types. Jentic injects the basic-auth credentials at execution time.

Can I limit what my agent is allowed to do with the Affinity CRM API?

Yes. Jentic One is self-hosted, so you run it and your own rules decide which Affinity operations and credentials the agent may use. Because the list id sits in the URL path for list entries (POST /lists/{list_id}/list-entries), a rule can pin the agent to a single list, while reads of organizations, persons, and opportunities are constrained through their query parameters. You choose which operations sit in the allowed set, so webhook subscriptions stay out unless you add them.