One API, two onboarding paths
CHeKT exposes a single Partner API at /partner/v1/... — the same paths, the same OAuth 2.0 client credentials flow, the same DTOs whether you're building a Dealer app or a Platform integration. What differs is the scope of dealers your token can reach:
- Dealer app
- Tied to a single dealer. The dealer admin installs your app in the portal, you receive credentials, and your token can only read or write data for that one dealer.
- Platform partner
- Cross-dealer access. Your credentials can act on any dealer that has connected their account to your external system via /partner/v1/dealers/connect.
The two onboarding paths in detail
Dealer apps
A third-party service that operates on behalf of one dealer at a time. The dealer admin installs your app in the dealer portal; you receive client credentials scoped to that dealer.
- Best for: AI verifiers, custom dashboards, automation tools, reporting integrations.
- Onboarding: Self-service — any developer can create an app.
- Auth: OAuth 2.0 client credentials, dealer-scoped.
- Time to ship: hours to days.
Platform partners
A platform that brings traffic and customers to CHeKT — video providers, intrusion-panel manufacturers, large automation platforms. Cross-dealer credentials let one integration serve every dealer that connects with your system.
- Best for: Video / panel / automation platforms with their own user base.
- Onboarding: Signed agreement + security review (typically 2–8 weeks).
- Auth: OAuth 2.0 client credentials, cross-dealer scope.
- Connect flow: Each dealer that wants to use your platform calls PUT /partner/v1/dealers/connect once to bind themselves to your external_dealer_id.
Who should apply as a Platform partner?
The Platform partner path adds operational overhead — the security review, the partnership agreement, the cross-dealer audit trail. It's the right choice when:
- You operate a platform with its own users
- Video providers, panel manufacturers, large-scale automation platforms. You bring dealers; CHeKT does the monitoring.
- You need to act on many dealers programmatically
- Hundreds or thousands of dealers using your platform — managing each as a separate Dealer app would not scale.
- You need elevated rate limits
- Cross-dealer workloads can exceed Dealer app limits. Partner agreements come with custom rate-limit ceilings.
- Most other partners
- Stick with Dealer apps. They cover ~95% of integration patterns and ship faster.
The connect flow
For Platform partners, every dealer that wants to use your integration goes through a one-time connect step. The dealer admin (or your service, with the dealer's authorization access token) calls PUT /partner/v1/dealers/connect, supplying your external_dealer_id and the dealer's company name. CHeKT records the mapping, and your client credentials can act on that dealer from then on.
Disconnect is symmetrical: PUT /partner/v1/dealers/{dealerId}/disconnect removes the binding.
Applying for Platform partner access
Email partners@chekt.com with the following information. We respond within one business day; full onboarding typically takes 2 weeks for standard partners, 6–8 weeks if Assertion Tokens or custom rate-limit ceilings are involved.
- What you're building. Your platform, your customers, and how CHeKT fits.
- Expected traffic. Calls per minute, peak periods, geographies.
- Number of dealers. How many of your users you expect to connect in the first 6 months.
- Timeline. When you want to go live, plus any external deadlines (regulatory, customer contracts).