What authentication does the Aimtell API use?

The Aimtell API uses an API key passed in the X-Authorization header. When called through Jentic, the key is stored encrypted in your Jentic One instance and never enters the agent's context - agents receive scoped access without seeing the raw key.

Can I send a push notification to a specific segment with the Aimtell API?

Yes. POST /push accepts a target segment identifier alongside the notification title, message, and link, and dispatches the notification to all matching subscribers across the chosen website.

What are the rate limits for the Aimtell API?

Aimtell does not publish formal rate limits in the spec. In practice, calls are throttled per account; for high-volume sends use campaign endpoints rather than looping POST /push calls.

How do I create an event-triggered campaign with the Aimtell API through Jentic?

Run pip install jentic, search Jentic for 'create event-triggered push campaign', load the schema for POST /campaigns/event, then execute with the website ID, event name, and notification payload. Jentic injects the X-Authorization header automatically.

Can I track custom subscriber attributes with the Aimtell API?

Yes. POST /subscribers/{subscriberId}/attributes accepts arbitrary string key-value pairs and the values are usable as segment filters, so attributes set in one call become targetable in the next campaign.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Aimtell operations and credentials your agent may use. Aimtell puts the site id in the URL path for analytics, so you can pin reporting to a single site with a path rule on GET /analytics/{siteId}. For push and campaign calls the targets travel in the request body, so you scope those by operation, allowing only the ones your agent needs such as POST /push or POST /campaigns/event.