What authentication does the Papyrs API use?

The Papyrs API uses an API token passed as the auth_token query parameter. Through Jentic, the token is stored in the encrypted vault and injected at execution time so it never enters the agent's prompt context.

How do I create a page with content?

POST /pages/create/ accepts title, json (array of widget columns), optional layout, permissions, and notifications. The json field contains arrays of widgets with classname, id, and val properties defining the page content.

What happens when I update a widget?

When you POST to update endpoints like /page/{page_id}/paragraph/update/{widget_id}/, the widget ID changes. The response includes version_of_id containing the original widget ID before the update.

What are the rate limits?

Papyrs API has a default rate limit of 6 requests per 60 seconds. Exceeding this returns a 429 Too Many Requests error. Spread requests across time or use webhooks for real-time updates instead of polling.

Can I retrieve form submissions?

Yes. GET /pages/records/{page_id}/ returns all form records submitted on a page with pagination support (page and items_per_page parameters). Returns an array of records, each containing field-value pairs.

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

Yes. Because you run Jentic One yourself, your own rules decide which Papyrs operations and credentials the agent may use. Since Papyrs puts the page id in the URL path, such as /pages/get/{page_id}/ and /page/{page_id}/paragraph/create/, you can pin the agent to a single page and allow only reads and adding paragraphs or headings there. Destructive operations like deleting a page or a paragraph stay out of reach unless you explicitly add them to the agent's allowed set.