Obtain OAuth 2.0 client credentials from bolttech's partner onboarding team; use them to request an access token from the bolttech token endpoint
Call the product catalog endpoint to retrieve the device-protection plans available for your configured market; filter by device type and enrollment channel
At checkout, POST customer and device details to the quote endpoint; the response returns plan options with premium and terms for display
On customer acceptance, POST a contract-creation request with the selected plan ID and customer consent acknowledgment; the response includes a contract/policy reference number
Handle the enrollment confirmation webhook or poll the contract status endpoint to confirm the policy is active before completing the checkout transaction
For multi-device households, use the multi-device enrollment feature in the API; each device is enrolled as a separate contract under the same customer account
Known gotchas
bolttech's API is versioned (currently V4.x); do not mix paths from older documentation — breaking changes between major versions are not backward-compatible
OAuth 2.0 tokens expire; implement automatic token refresh before expiry rather than handling 401 errors reactively, since a failed enrollment at checkout damages conversion rates
Encrypted payload requirements apply to sensitive customer data fields; confirm which fields require field-level encryption in addition to transport-layer TLS with your bolttech integration engineer
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp