RMOZ / developers
Developer integration readiness
Technical guidance for integration planning, identity, data contracts, reliability and security controls.
Integration at a glance
Four steps from question to go-live.
- Step 01
Map the process
Initiating event, source of truth, actors and expected result.
- Step 02
Set the boundaries
Classify data and decide who can submit, read, amend or revoke.
- Step 03
Plan for failure
Duplicates, ordering, timeouts and a reconciliation owner.
- Step 04
Confirm go-live
Environments, security, approvals and a support route.
Start here
These resources help architects and engineers prepare an integration: the questions to answer, the data to model and the acceptance criteria to agree. Environment details, credentials and API references are issued to clients during onboarding.
Start with the integration model
Identify the source system, event owner, record schema and the verification result you need. Define what stays private, which party authorises writes and how downstream systems learn about corrections.
Prepare the technical details
During onboarding you receive interface documentation, environment identifiers, authentication instructions and the versioning policy. Error behaviour, rate limits, support ownership and recovery expectations are agreed before go-live.
Use the implementation resources
The integration guide defines discovery and acceptance steps, while the API page organizes identity, authorization and interface requirements. The downloadable checklist supports a consistent technical and operational review.
Continue the journey
FAQ
Questions, answered
Can I start sending requests now?
API access is provided to clients as part of an implementation, with credentials, environments and documentation issued by our team.
Can I see example workflows?
Yes. The integration guide walks through a typical flow, and our team shares detailed examples for your use case during discovery.
YOUR NEXT STEP
Build your next step
on trust.
Find the right starting point for your assets, records and business.
Find your use case