Quick start
Three steps to your first API call
Authentication
OAuth 2.0 client credentials flow
Client credentials
Receive a client ID and client secret when you register your integration. Store these securely—never expose them in client-side code.
CLIENT_ID=rm_abc123
CLIENT_SECRET=sk_live_xyz789Access token
Exchange credentials for a short-lived access token. Include this token in the Authorization header of all API requests.
POST /oauth/token
{
"grant_type": "client_credentials",
"client_id": "rm_abc123",
"client_secret": "sk_live_xyz789"
}API requests
Include the access token in the Authorization header as a Bearer token.
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...Key endpoints
Core API resources for building comparison experiences
/v1/matchSubmit user context and receive matched product offers
Bearer token required
/v1/productsRetrieve available products and eligibility criteria
Bearer token required
/v1/applicationsSubmit application intent and track lifecycle
Bearer token required
/v1/webhooksConfigure webhook endpoints for async notifications
Bearer token required
SDKs & libraries
Official client libraries for popular languages
Node.js
Available
Python
Available
Ruby
Coming soon
Go
Coming soon