Integration lifecycle
End-to-end path from discovery to production support for MasteryHive partner APIs.
Stages
| # |
Stage |
What you do |
Done when |
| 1 |
Discovery |
Read Products, readiness summary, and this Integration section |
You know which products and contracts apply |
| 2 |
Environment setup |
Agree environment with MasteryHive; read Base URLs and Environments |
You have a host (or an explicit owner-decision ticket) |
| 3 |
Credentials |
Complete Access onboarding; for Fraud follow Auth tutorial |
Keys / gateway access issued; no secrets in client apps |
| 4 |
Schema agreement |
Lock OpenAPI + named contracts for your revision (conventions) |
Request/response fields agreed; unknowns listed |
| 5 |
Initial call |
Run the product quickstart |
First 200 (or accepted async) with expected body |
| 6 |
Asynchronous completion |
Wire Fraud report callback and/or recon status / events |
You can observe completion without polling forever |
| 7 |
Error handling |
Implement error catalogue + retry tables |
Retries are safe; bad bodies are not blindly retried |
| 8 |
Testing |
Negative cases from examples; contract tests against staging when available |
Auth failures, scope errors, and rejects are covered |
| 9 |
Rollout |
Promote with change control; watch score/report and session completion |
Production traffic matches agreed readiness |
| 10 |
Production support |
Use session/transaction/tenant ids; escalate via account channel |
Support can correlate one failed run |
Product-specific entry
| Product |
Quickstart |
Primary auth |
Completion signal |
| Fraud |
Quickstart |
ApiKey JWT + x-tenant-id |
Prediction and/or dashboard report (see reliability notes) |
| KYC / KYB |
Quickstart |
Per-environment |
Per-route HTTP success with vendor-backed payload |
| Reconciliation |
Quickstart |
Per-environment + scope fields |
Session pipeline status / exception audit |