What authentication does the FeedBlitz API use?

FeedBlitz uses an API key passed as the 'key' query parameter on each request. Through Jentic the key is stored in the vault and Jentic appends it at call time so it is not exposed in agent prompts or logs.

Can I add and remove subscribers programmatically?

Yes. POST /subscribers/add adds a subscriber to a FeedBlitz list and POST /subscribers/remove removes them, supporting standard CRM-to-newsletter automation.

What are the rate limits for the FeedBlitz API?

FeedBlitz does not publish numeric rate limits in this spec; throughput is constrained per account plan. Apply exponential backoff on 429 responses and contact FeedBlitz support if bulk operations need higher throughput.

How do I add a subscriber to FeedBlitz through Jentic?

Run pip install jentic, search 'add a feedblitz subscriber', load POST /subscribers/add, and execute it with the email and list ID to enrol the contact.

Can I list scheduled campaigns?

Yes. GET /campaigns returns campaigns configured on the account, useful for confirming send schedules before launch.

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

Yes. Because you run Jentic One yourself, you decide exactly which FeedBlitz operations your agent may call, so you can grant read-only access to GET /subscribers, GET /feeds, GET /campaigns, and GET /triggers while withholding writes. Since FeedBlitz identifies the subscriber and list in the request body rather than the URL, a write such as POST /subscribers/remove is available only when you explicitly add it to the agent's allowed operations. Your FeedBlitz API key stays in your own instance and is appended at call time, so the agent never sees it and can only act within the operations you have permitted.