Can I retrieve waivers signed before API integration?

Yes, GET /waivers retrieves all historical waivers stored in Otter Waiver, not just those signed after API integration. Filter by date range to retrieve specific periods.

How do I receive real-time notifications when waivers are signed?

Configure a webhook with POST /webhooks. Specify your endpoint URL and the API will send POST requests with waiver data immediately when participants sign. This enables real-time onboarding and compliance workflows.

Can I create or send waivers via the API?

The current API focuses on retrieving and managing signed waivers. Waiver creation and sending is handled through the Otter Waiver web interface, kiosks, or mobile apps. The API accesses the results.

Is participant data encrypted and secure?

Yes, Otter Waiver encrypts participant data at rest and in transit. The API uses HTTPS for all connections, and bearer tokens should be kept secure. Through Jentic, tokens are stored encrypted and never exposed in agent contexts.

Can I export waivers in PDF format?

The API returns waiver data in JSON format. For PDF exports, use the Otter Waiver web interface or contact support for bulk export options. The API provides the data needed to generate custom PDF reports.

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

Yes. Because you run Jentic One yourself, your own rules decide which Otter Waiver operations and credentials the agent may use, so you can grant read-only access to retrieve signed waivers via GET /waivers and look up people via GET /participants while withholding the ability to register webhooks with POST /webhooks. Since Otter Waiver puts the id in the URL path for GET /waivers/{id} and GET /participants/{id}, a rule can pin the agent to a single waiver or participant rather than the whole account. Your stored credentials are injected only when an allowed call runs, so the agent can read signed waivers without any write access.