Preloader

Developer FAQ

1. What does it mean to build on OMNI Kredi?

Building on OMNI Kredi means creating secure integration layers that connect approved systems to OMNI Kredi. Developers help supported OMNI services work more reliably for OK Builders, OK Business participants, OK Agents, partners, and other approved participants. The goal is not just integration; it is building systems people can trust.

2. How do developers get approved access?

Developers can begin by requesting access through the approved developer path for their role, organization, or integration purpose. Access may depend on verification, platform rules, technical readiness, and the supported OMNI services involved. Approved access helps protect participants while keeping participation flows responsible.

3. What does the OMNI Kredi API support?

The OMNI Kredi API supports approved integration paths connected to supported OMNI services. Depending on access, developers may connect participation flows, OK Token activity, service events, business systems, or role-aware experiences. Available endpoints and permissions depend on platform rules and approved use cases.

4. Can developers test before going live?

Yes. Where available, sandbox testing helps developers validate integrations before supporting real participant activity. Testing helps confirm that requests, responses, events, and role permissions work as expected. This protects trust and reduces risk before an integration reaches production.

5. What are webhooks used for?

Webhooks help connected systems respond to important OMNI events through approved integration paths. They can keep systems aligned when supported activity changes, updates, or requires follow-up. Reliable webhook handling helps developers build participation flows that stay clear, timely, and trusted.

6. What platform rules do developers need to follow?

Developers must follow OMNI Kredi platform rules for access, permissions, data handling, participant protection, and supported service use. These rules help protect the meaning of eligible participation, recognition, OK Developer, and trusted ecosystem activity. Integrations that do not follow approved paths may be limited, reviewed, or rejected.

7. How should a developer start building?

Start by defining the participant role, supported OMNI service, and purpose of the integration. Then request approved access, review the available documentation, test in sandbox where supported, and build around secure participation paths. A strong integration begins with trust, not only code.

8. What support is available for developers?

Developer support may include documentation, access guidance, sandbox help, integration review, and platform-rule clarification. Support paths depend on the integration type, approved access level, and services involved. The goal is to help developers build responsibly while protecting OMNI participants and the wider ecosystem.

Our goal is to help your business accept OK Tokens through OMNIPlus APIs and gateway tools. Explore our developer portal or contact support for integration questions.