canonical: https://jentic.com/apis/otterwaiver.com/otterwaiver

# Otter Waiver API

Otter Waiver (OtterSign) is a digital waiver signing platform designed for businesses that require liability waivers, consent forms, or customer agreements. The API provides programmatic access to waivers, participants, folders for organizing waivers, and webhook subscriptions for real-time signing notifications. Otter Waiver eliminates paper forms with iPad kiosks, mobile signing, and web-based waiver collection for gyms, adventure sports, events, medical offices, and any business requiring signed agreements.

## For AI agents

Manage digital waivers and consent forms: retrieve signed waivers, access participant information, organize waivers in folders, and configure webhooks for signing events.

## Scope

Does not create waivers, send waiver requests, or manage waiver templates via API - use only for retrieving signed waivers, participant information, and webhook configuration.

## Capabilities

- Retrieve signed waivers with participant information and signatures
- Access participant details including contact info, emergency contacts, and custom fields
- Organize waivers into folders by location, event, or category
- List waivers with filtering by date, participant, or waiver template
- Configure webhooks to receive real-time notifications when waivers are signed
- Export waiver data for compliance, auditing, and record-keeping
- Search participants by name, email, or phone number
- Manage waiver retention and archival policies

## Use cases

### Event Check-In and Waiver Verification

Event organizers can verify that attendees have signed required waivers during check-in. GET /waivers retrieves signed waivers filtered by date or event, and GET `/participants/{id}` confirms participant details. Agents can automate check-in flows by looking up attendees in the waiver system and flagging those who haven't signed, reducing manual paperwork at registration.

Example prompt: GET /participants with email or name filter to find the participant, then GET /waivers filtered by participant ID to confirm they've signed the required waiver for the event.

### Gym and Fitness Center Member Onboarding

Gyms can automate member onboarding by integrating waiver signing into signup flows. Webhooks configured with POST /webhooks notify backend systems when new members sign liability waivers, triggering membership activation, access card issuance, or welcome emails. GET /waivers retrieves signed waiver history for compliance audits and renewals.

Example prompt: POST /webhooks to configure real-time notifications, then when a waiver is signed, the webhook triggers GET `/waivers/{id}` to retrieve the signed waiver and activate membership.

### Multi-Location Waiver Management

Businesses with multiple locations like trampoline parks, escape rooms, or adventure sports can organize waivers by location using folders. GET /folders lists organizational units, and GET /waivers with folder filtering retrieves location-specific waivers. This enables centralized compliance tracking while maintaining per-location visibility for franchises or multi-site operations.

Example prompt: GET /folders to list locations, then GET /waivers filtered by folder ID to retrieve waivers for a specific location for compliance reporting.

### Medical and Healthcare Consent Forms

Medical offices, clinics, and healthcare providers can manage patient consent forms digitally. GET /participants retrieves patient information with signed consent status, and GET /waivers accesses the signed forms for medical records. Webhooks notify EHR systems when new consent forms are signed, enabling automated record updates and reducing administrative overhead.

Example prompt: POST /webhooks to notify the EHR when consent forms are signed, then GET `/waivers/{id}` to retrieve the signed consent form for attachment to the patient's medical record.

### AI Agent for Waiver Operations

Let an AI agent handle waiver-related tasks for an event company - verifying attendees have signed waivers, retrieving participant information, and generating compliance reports. Through Jentic, the agent loads only the required operations and Otter Waiver API keys are injected at execution time.

Example prompt: Use the Jentic search query 'retrieve signed waivers' to find GET /waivers, load its schema, and execute with date and event filters to generate compliance reports.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/waivers` | List signed waivers with filtering by date, participant, or template |
| GET | `/waivers/{id}` | Retrieve a specific waiver with full details and signature data |
| GET | `/participants` | List participants with search by name, email, or phone |
| GET | `/participants/{id}` | Retrieve participant details and waiver history |
| GET | `/folders` | List folders for organizing waivers |
| POST | `/webhooks` | Configure webhooks for waiver signing events |

## Key resources

- **Waivers** — Signed digital waivers with participant signatures, timestamps, and custom fields
- **Participants** — Customer information including contact details, emergency contacts, and signing history
- **Folders** — Organizational units for categorizing waivers by location, event, or department
- **Webhooks** — Real-time notifications for waiver signing events and participant updates
- **Waiver Templates** — Reusable waiver forms with custom fields and legal language

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 72 / 100
- **View full report:** https://jentic.com/apis/otterwaiver.com/otterwaiver/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Otter Waiver by hand means obtaining a JWT through its OAuth 2.0 client credentials flow, sending it as a bearer token to the api.otterwaiver.com host, and handling token refresh and retries yourself. Through Jentic you install once, import the Otter Waiver API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Otter Waiver puts the waiver and participant id in the URL path (`/waivers/{id}`, `/participants/{id}`), so a rule can pin your agent to reading one waiver or participant. You choose the operations it may call, so registering webhooks is not included unless you add it, and a read-only agent can retrieve signed waivers without any write access.
- **Credential handling:** Your Otter Waiver client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve a signed waiver' or 'look up a participant', and Jentic returns the matching Otter Waiver operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PandaDoc API** — A document and e-signature platform for creating, sending, and tracking agreements, offered as an alternative to Otter Waiver API.
- **Dropbox Sign API** — An e-signature service for requesting and collecting legally binding signatures, offered as an alternative to Otter Waiver API.

## FAQ

### What authentication does the Otter Waiver API use?

The Otter Waiver API uses bearer token authentication. API keys are generated in the Otter Waiver dashboard and sent via the Authorization header. Through Jentic, keys are stored encrypted and injected at execution time.

### 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.