canonical: https://jentic.com/apis/waiverfile.com/waiverfile # WaiverFile API WaiverFile is a digital waiver solution. This API allows management of waivers, events, subscriptions, and SMS subscribers. The API exposes 17 endpoints secured with apiKey authentication. ## For AI agents Programmatically check that the service is live, get your waiversite details. Covers 17 operations with apiKey authentication. ## Scope Does not handle communications, crm, or developer tools - use for payments only. ## Capabilities - Check that the service is live - Get your WaiverSite details - Search waivers - Query and filter WaiverFile API records by parameters - Monitor WaiverFile API operational status and events ## Use cases ### Payments Operations Use the WaiverFile API to perform payments operations programmatically. The API provides 17 endpoints covering core functionality including check that the service is live, get your waiversite details, get an individual waiver. Example prompt: Call GET `/api/v1/Ping` to check that the service is live ### Automated SMS Management Automate sms operations by combining multiple WaiverFile API endpoints. Agents can get your waiversite details and then get an individual waiver in a single workflow. Example prompt: Call GET `/api/v1/GetSiteDetails` to get your waiversite details, then verify the result ### AI Agent Integration via Jentic AI agents discover and call WaiverFile API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'check that the service is live', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/Ping` | Check that the service is live | | GET | `/api/v1/GetSiteDetails` | Get your WaiverSite details | | GET | `/api/v1/GetWaiver` | Get an individual waiver | | GET | `/api/v1/GetWaiverPDF` | Get an individual waiver as PDF | | GET | `/api/v1/SearchWaivers` | Search waivers | | GET | `/api/v1/GetWaiversByReferenceID` | Get waivers by reference ID | | GET | `/api/v1/GetEventsByDateRange` | Get events by date range | | GET | `/api/v1/GetUpcomingEvents` | Get a list of upcoming events | ## Key resources - **SMS** — Operations related to SMS - **Subscription** — Operations related to Subscription - **WaiverEvent** — Operations related to WaiverEvent - **WaiverFile** — Operations related to WaiverFile ## 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:** 46 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 65 / 100 - **View full report:** https://jentic.com/apis/waiverfile.com/waiverfile/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 ``` ## Why Jentic - **Setup:** Wiring the WaiverFile API by hand means passing your key as the apiKey query parameter on api.waiverfile.com and attaching it to every request yourself. Through Jentic you install once, import the WaiverFile API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** The WaiverFile API exposes read operations that take identifiers as query parameters rather than fixed resource URL paths, so limit the agent to the operations it needs, such as searching waivers and fetching site details, and leave others out of the allowed set unless you add them. - **Credential handling:** Your WaiverFile API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'check that the service is live' or 'search signed waivers', and Jentic returns the matching WaiverFile API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe** — Alternative payments API - **Adyen** — Alternative payments API - **Square** — Complementary payments API - **Paypal** — Complementary payments API ## FAQ ### What authentication does the WaiverFile API use? The WaiverFile API uses an API key passed in the `apiKey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I check that the service is live with the WaiverFile API? Yes. Use the GET `/api/v1/Ping` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the WaiverFile API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I check that the service is live through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check that the service is live'. Jentic returns the matching WaiverFile API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the WaiverFile API have? The WaiverFile API exposes 17 endpoints covering sms, subscription, waiverevent operations. ### Can I limit what my agent is allowed to do with the WaiverFile API? Yes. Because Jentic One is self-hosted, you set the rules that decide which WaiverFile API operations and credentials your agent may use. Since these are read operations that take identifiers as query parameters, you can allow only the ones the agent needs, such as searching waivers or fetching your WaiverSite details, and leave others like retrieving waiver PDFs or events by date range out of the allowed set. Your API key is injected at execution time under those limits, so the agent can only call the operations you have permitted.