What authentication does the Buttondown API use?

Buttondown uses a token-based API key passed in the Authorization header in the format 'Token YOUR_API_KEY'. Through Jentic, the key is stored in the encrypted vault and never enters an agent's context.

Can I send a newsletter through the Buttondown API?

Yes. POST to /emails creates a new newsletter email; PATCH to /emails/{id} updates a draft. The API supports the full draft, edit, and send lifecycle for newsletter content.

What are the rate limits for the Buttondown API?

Buttondown does not publish hard rate limits in the spec. For batch subscriber syncs, space requests at a moderate cadence and watch for 429 responses; back off when they appear rather than retrying tight loops.

How do I add a subscriber through Jentic?

Run pip install jentic, then search Jentic with the query 'add a buttondown subscriber', load the schema for POST /subscribers, and execute with the email and any optional tag or metadata fields.

Can I look up a subscriber by email address?

Yes. GET /subscribers/{idOrEmail} accepts either the subscriber's UUID or their email address as the path parameter, returning the full subscriber record if it exists.

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

Yes. Because you run Jentic One yourself, your own rules decide which Buttondown operations and credentials the agent may use. You can grant it read and create calls like GET /subscribers/{idOrEmail} and POST /subscribers while withholding destructive ones such as deleting a subscriber or removing an email draft. Since the subscriber or email id sits in the URL path (/subscribers/{idOrEmail}, /emails/{id}), you can also pin the agent to specific records rather than the whole audience.