Can I start a checklist run through the Manifestly Checklists API?

Yes. POST /runs starts a new run from a published checklist template. The payload references the checklist_id and accepts a run name, owner, and assignees so the run is set up correctly from the moment it starts. List active runs with GET /runs.

What are the rate limits for the Manifestly Checklists API?

Manifestly's published documentation does not pin a single per-second number; the API throttles per-workspace and returns 429 with a Retry-After header when exceeded. Pace bulk imports of templates or runs and respect the Retry-After value rather than retrying immediately.

How do I add a step to a checklist template through Jentic?

Run pip install jentic, then search Jentic for 'add a step to a manifestly checklist'. Jentic returns the POST /checklists/{checklist_id}/steps operation with its step schema, which you execute with the title, description, and position to add the new step to the template.

Does the Manifestly Checklists API support webhooks?

Yes, at two levels. Workflow hooks fire on workflow-level events (run started, run completed); step hooks fire on step-level events (step started, step completed). Register both through the hooks endpoints under /checklists/{id}/hooks and /steps/{id}/hooks.

Can I capture data inside a checklist run?

Yes. Each step can have data settings configured via the step data setting endpoints, which expose typed fields the assignee fills in during the run. The captured values are returned with the run and can be pulled out by reporting and downstream automations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Manifestly operations and credentials your agent may use. Manifestly puts the checklist id in the URL path, such as /checklists/{checklist_id}/steps, so you can pin the agent to a single checklist where it reads and edits only that checklist's steps and nothing else. You pick the operations it may call, so template creation via POST /checklists or starting runs via POST /runs is excluded unless you explicitly allow it.