CLOSUM API

What authentication does the Closum API use?

Closum uses an API key passed as a query parameter on each request. Generate the key from your account settings. Through Jentic, the key is stored encrypted in your Jentic One instance and appended to the URL at execution time so agents never see it.

Can I tag contacts by email address with the Closum API?

Yes. POST /contact-tag/add-tag-by-email/ accepts an email and tag pair, so you do not need to resolve the contact id first. DELETE /contact-tag/remove-tag-by-email/ does the inverse. Both are useful for syncing tags from external sources keyed on email.

What are the rate limits for the Closum API?

Closum applies plan-based rate limits, typically a few requests per second per account. Exact limits are not encoded in the spec - handle 429 responses with backoff. Jentic surfaces 429s back to the agent for clean retries.

How do I send a templated email through Jentic?

Run pip install jentic, search for 'send closum email template', load the POST /email-template/send/{template_id} schema, and execute with template_id and contact_id. Variables in the template are passed in the request body.

Does the Closum API support custom fields?

Yes. GET /field/ lists the custom contact fields configured for the account; you can then reference these fields when creating or editing contacts. This lets you persist segmentation attributes that aren't part of the default contact schema.

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

Yes. Because you run Jentic One yourself, your own rules decide which Closum operations and credentials the agent can use. You can allow it to add leads with POST /lead/add/ and tag contacts by email with POST /contact-tag/add-tag-by-email/ while keeping template sends like POST /email-template/send/{template_id} out of scope. Since Closum's write targets, such as a contact identified by email, travel in the request body, you scope the agent by picking exactly which operations belong in its set.