Skip to main content

​
Cover Whale API

The Cover Whale API provides programmatic access to commercial trucking insurance quoting, submission management, and policy binding. It is designed for insurance agents, brokers, and integration partners who need to embed Cover Whale’s insurance products into their workflows.

​
What You Can Do

Get Indications & Quotes

Submit DOT numbers and fleet details to receive preliminary pricing or binding-eligible quotes across 5 coverage lines.

Manage Submissions

Track submission status, update insured information, and add vehicles, drivers, and trailers.

Bind Policies

Convert quoted submissions into active policies with coverage selection, e-signature, and financing options.

Policy Lifecycle

Create endorsements, process cancellations, reinstatements, non-renewals, and declines.

​
Base URL

All API requests are made to: 
https://app.coverwhale.com/api/v1

​
Getting API Access

To start integrating with the Cover Whale API:
  1. Request credentials — Contact api-support@coverwhale.com or your Cover Whale account representative
  2. Receive your credentials — You’ll get a username and password for API authentication
  3. Authenticate — Exchange your credentials for an AccessToken via the authentication endpoint
  4. Start building — Follow the Quickstart to make your first API call
API credentials are issued per integration partner. Each set of credentials is scoped to your agency and its submissions. Contact your Cover Whale representative to discuss your integration needs.

​
Authentication

The API uses token-based authentication. Include your AccessToken in the header of every request: 
curl -X GET https://app.coverwhale.com/api/v1/submission/2172961 \
  -H "Accept: application/json" \
  -H "AccessToken: eyJraWQiOiJnRk5oTTh2RnRKWXVDVXU1S..."
The header name is AccessToken — not Authorization and not Bearer. This is a custom header.
Tokens expire after 1 hour. Use the refresh token to obtain a new access token without re-entering credentials. See the Authentication guide for details.

​
API Versioning

The current API version is v1. The version is included in the base URL path. Breaking changes will be introduced in new versions.

​
Rate Limits

API requests are rate-limited to protect service stability. If you receive a 429 Too Many Requests response, wait before retrying. Contact the API team if you need higher limits for your integration.

​
Error Handling

The API uses standard HTTP status codes. See the Error Handling guide for details on error response formats and troubleshooting.
CodeMeaning
200 / 201Success
400Bad request — check your request body
401Unauthorized — missing or invalid AccessToken
404Resource not found or submission not in required status
422Validation error — check the errors object in the response
429Rate limited — wait and retry

​
Support

For API access, credentials, or technical support: