The API Channel · Defense + PreAuth
Score identity in a single POST.
The Kombatix API is the developer channel for two products — Defense (dispute-time identity scoring) and PreAuth (pre-authorization network screening). REST-first, JSON in, JSON out, sub-second response. API access is granted the moment you subscribe and your first month is paid; keys are generated in the developer portal in minutes.
What you can do with the API
| Endpoint | Purpose | Response Time |
|---|---|---|
| POST /v1/defense | Score a dispute: three engines + composite 0–100 score + AI narrative + reason codes + identity match breakdown. | < 1 second |
| POST /v1/preauth | Screen a transaction's identity against the Kombatix Network. Hit/no-hit response with severity on hits. | < 200ms |
Sample Defense Request
POST /v1/defense
The Defense endpoint takes dispute context plus original transaction context and returns a composite score. The example below shows the operation, dispute-side fields, transaction-side fields, and metadata inputs.
POST /v1/defense HTTP/1.1
Host: api.kombatix.io
Content-Type: application/json
Authorization: Bearer <your_api_key>
{
"operation": "defense",
"disputeName": "John Smith",
"disputeEmail": "",
"disputePhone": "5551234567",
"disputeBillingAddress": {
"street1": "", "city": "", "state": "", "zip": "", "country": ""
},
"transactionName": "",
"transactionEmail": "[email protected]",
"transactionPhone": "",
"transactionBillingAddress": {
"street1": "123 Main St", "city": "Anytown",
"state": "CA", "zip": "12345", "country": "US"
},
"transactionShippingAddress": {
"street1": "", "city": "", "state": "", "zip": "", "country": ""
},
"paymentCardType": "Visa",
"transactionDate": "2026-04-22",
"transactionAmount": "24.99",
"deviceIds": [""],
"payments": [
{ "type": "CARD", "token": "" }
]
}Sample Defense Response
200 OK
The response returns the validated and standardized identity inputs, field-by-field match status, the full composite score with sub-scores, and any triggered reason codes.
HTTP/1.1 200 OK
Content-Type: application/json
{
"requestID": "fd8c7a53-b9e6-42f1-a8e5-e8d3f69c1234",
"identitySource": {
"disputeName": {
"identity": "Identity 1",
"validated": true,
"standardized": "JOHN DOE"
},
"confirmedSource": "Identity 1 (Dispute Name is Identity 1)"
},
"disputeInputValidation": {
"name": { "matchStatus": "Matches Identity 1" },
"phone": { "matchStatus": "Matches Identity 1" },
"email": { "matchStatus": "Matches Identity 1" },
"billingAddress": { "matchStatus": "Matches Identity 1" }
},
"transactionInputValidation": {
"email": { "matchStatus": "Matches Identity 1" },
"billingAddress": { "matchStatus": "Matches Identity 1" },
"shippingAddress": { "matchStatus": "Matches Identity 1" }
},
"identityConsistencySummary": {
"disputeNameMatches": true,
"disputeEmailMatches": true,
"disputeBillingAddressMatches": true,
"transactionEmailMatches": true,
"transactionBillingMatches": true
},
"dateFirstSeen": "03-15-2018",
"dateLastSeen": "02-25-2025",
"kombatixDefenseScore": {
"Defense Score": "95.44",
"Risk Category": "High Dispute Risk - Likely Friendly Fraud",
"Sub-Scores": {
"Identity Match Score": "100.00",
"Identity Risk Score": "1.05",
"Behavioral Risk Score": "30.00"
},
"Reason Codes": {
"Behavioral Risk": [
"Multiple payment methods used (8).",
"Transactions from different locations (5)."
]
},
"Match Insights": {
"insight": "Transaction likely valid."
}
},
"transactionDetails": {
"paymentCardType": "Visa",
"transactionDate": "02-24-2025",
"transactionAmount": "125.50"
}
}Response Field Reference
What each response field means.
| Field | Type | Notes |
|---|---|---|
| requestID | UUID | Every request uniquely identified. Persist this for audit trails and bank evidence. |
| identitySource | object | Which submitted field Kombatix used as the canonical identity reference. |
| disputeInputValidation | object | Per-field validation + standardization + match status for the dispute-side inputs. |
| transactionInputValidation | object | Per-field validation + standardization + match status for the transaction-side inputs. |
| identityConsistencySummary | object | Boolean flags — does each submitted field match the canonical identity? |
| dateFirstSeen / dateLastSeen | date string | When the identity was first and last observed in our verified data network. |
| kombatixDefenseScore | object | The composite score, risk category, sub-scores, reason codes, and match insights. |
| transactionDetails | object | Echoed transaction metadata for audit. |
PreAuth Endpoint
PreAuth takes a subset of the Defense fields — identity without the dispute/transaction split — and returns a hit/no-hit response. Full request/response reference available in the developer portal after signup.
Authentication
Authorization: Bearer <your_api_key>
Bearer token (API key). Include in every request.
Environments
Sandbox environment available for integration testing. Sandbox calls do not count against your monthly allocation and do not contribute to the Kombatix Network.
Rate Limits
Per-plan rate limits apply. Enterprise plans have custom rate limits. Full schedule in developer portal.
API Pricing
Two products, two pricing tracks, one API channel.
The Kombatix API gives developers access to both products through the same REST surface. Each product is subscribed independently. Defense API bills for actionable Defense Score results (60+); PreAuth API bills per-check with per-tier hit/no-hit pricing.
Defense API
Dispute-time identity scoring · billed for 60+ results
Standard
Starts at
$75/month
Up to 75 Defense hits/month
- Full three-engine scoring
- $0.60 per additional hit
- API access live as soon as you subscribe
- Self-service developer portal
Advanced
Starts at
$500/month
Up to 1,000 Defense hits/month
- Full three-engine scoring
- $0.40 per additional hit
- API access live as soon as you subscribe
- Self-service developer portal
Enterprise
Custom
50,000+ calls/month
- Custom data dictionary options
- Dedicated product specialist
- SLA & priority support
- Enterprise contract + invoicing
PreAuth API
Pre-authorization network screening · per-check pricing
PreAuth Starter
Starts at
$49/month
Up to ~25K transactions/month
- No-hit: $0.005 each
- Hits: $0.15 each
- $49 monthly credit toward usage
- API access live as soon as you subscribe
PreAuth Growth
Starts at
$149/month
25K–100K transactions/month
- No-hit: $0.005 each
- Hits: $0.10 each
- $149 monthly credit
- Priority support
PreAuth Enterprise
Starts at
$499/month
100K+ transactions/month
- No-hit: $0.005 each
- Hits: $0.05 each
- $499 monthly credit
- Dedicated support
- Custom integrations
One-time $250 implementation fee applies to all PreAuth plans at onboarding.
Full developer documentation is behind login.
Complete endpoint documentation, error codes, response schemas, SDKs, and integration guides are inside the developer portal. Subscribe and pay your first month — keys can be generated in minutes and the docs are live immediately.
No engineering capacity? Use the Web Portal.
Web Portal Access is the no-code path to Defense scoring — browser-only, no integration required. Same scoring engine, full reports with AI insights, PDF export, searchable history. Subscribe separately from the API.