ORBIS.ID Open the walletWallet

Partners · application

Apply to build on ORBIS.ID.

Nine questions, all of them things you already know. This creates one record in the ORBIS review queue — it provisions nothing, and it is the only thing on this platform a person outside ORBIS can start on their own.

Tell ORBIS who you are and what you are building

Everything here goes to a human reviewer. Fields marked * are required. Never put a secret, a token, a password or a key in this form — there is no field for one, and the server refuses a submission that even contains a field NAMED like one.

Which are you? *

The legal entity that will appear on the credential or the contract. Up to 120 characters.

Public https address. It is recorded for the reviewer; this page does not fetch it.

Country or region. It drives which regulations apply to your integration.

Who ORBIS should talk to about this.

How ORBIS replies — and one of the two things you need to look your own status up later. Use an address you will still have in six months.

In your own words — who holds the credential, who checks it, and what changes for them. At least 20 characters, up to 1200.

A band is enough. It only helps a reviewer triage; nothing is committed by it.

A public domain name only — no scheme, no path. Leave it empty if you do not have one yet; it changes nothing about your application.

ORBIS records exactly the fields above and nothing else — an unrecognised field is refused rather than quietly stored. Submitting creates one application in stage applied; it grants no access and provisions nothing.

Back to the profiles

What happens after you press send

  1. Applied ORBIS acts

    Your application exists and is in the review queue. Nothing has been provisioned.

    What moves it: An ORBIS reviewer picks it up. You do not need to do anything.

  2. Reviewing ORBIS acts

    A reviewer is reading it and may come back to you with questions.

    What moves it: The reviewer either asks you something or moves you to a sandbox.

  3. Sandbox you act

    You have a demonstration organization to build against. It is marked as a demo everywhere, permanently.

    What moves it: You build the integration, then ask for certification.

  4. Certifying you act

    The platform is running the real exercises against your integration and recording the evidence.

    What moves it: Every check on the readiness board passes. Each failure names the concrete fix.

  5. Live nobody waits

    You are a provisioned organization on the production rail.

    What moves it: Nothing — this is the destination. Your organization is now managed in Organizations, not here.

You will be shown a reference that looks like pa_…. Keep it: with your contact email it is how you read your own status at /partners/status. It is not a password and it grants nothing on its own — and ORBIS will never ask you to send it anywhere but that form.

Already a partner? Sign in to the partner portal to see your status, issue and revoke your own API keys, and manage who else is on your account. To read your status without signing in, /partners/status takes your reference and contact email and nothing else.

The API reference lives at /developers and the machine-readable contract at /openapi.json. Nothing on this page restates them — they are the one source.