Integrations
API Authentication
How to authenticate with the WaiverChaser REST API using OAuth 2 access tokens.
The WaiverChaser API uses OAuth 2 for authentication. API access is currently available through the Zapier integration. When you connect WaiverChaser in Zapier, OAuth handles the token exchange automatically. You don't manage tokens directly.
Base URL
https://waiverchaser.com/api/v1
How authentication works
When you connect WaiverChaser to Zapier, you're redirected to WaiverChaser to sign in and approve access. Zapier then receives an OAuth 2 access token and refresh token, which it stores and uses for all subsequent API calls on your behalf. Tokens are refreshed automatically when they expire.
All API requests are authenticated with a Bearer token in the Authorization header:
Authorization: Bearer YOUR_ACCESS_TOKEN
Scopes
When connecting through Zapier, the following scopes are requested:
| Scope | What it allows |
|---|---|
waivers:read |
Read waivers, waiver versions, and locations |
packets:read |
Read completed signature packets and signing requests |
requests:write |
Send signing requests by email |
Errors
All error responses return JSON with an error field:
{ "error": "Unauthorized" }
Common status codes:
| Status | Meaning |
|---|---|
401 |
Missing or expired token |
403 |
Token doesn't have the required scope, or plan restriction |
404 |
Resource not found or doesn't belong to your organization |