Help
Answers to the questions we get most. Not covered here? Contact support — integration details live in the docs.
I never received my invite email
First check your spam or quarantine folder — invite emails come from developeroffice.com. If it's not there, a previous bounce may have put your address on our suppression list (one hard bounce is enough), which silently blocks further sends. Ask the admin who invited you to resend the invite; if it still doesn't arrive, contact support with your email address and we'll clear the suppression and resend. Invites also expire — an old link that says it's invalid just needs the admin to send a fresh one.
I'm locked out of my account
Too many failed password or code attempts locks the account temporarily. The lock clears on its own after about 10 minutes — wait, then try again carefully. If you've forgotten the password, use the password reset instead of guessing (guessing extends the lock). If your account says it is locked even after waiting, an administrator can unlock it immediately — contact your org admin or our support.
My app shows a redirect_uri mismatch error
Redirect URIs are matched exactly — scheme, host, port, and path must all be identical to a URI registered on the application, with no wildcards. Production URIs must be https; the only exception is http://localhost (any port) for development. Fix: open the application in the admin console, copy the exact URI your app sends in the authorize request, and add it to the app's redirect URI list.
Which URL do I integrate against?
Everything hangs off https://login.developeroffice.com — the OIDC discovery document at /.well-known/openid-configuration lists the authorize, token, and JWKS endpoints, and standard OIDC client libraries configure themselves from it. The developer documentation walks through the full authorization-code + PKCE flow.
Still stuck? Open a support request and we'll reply by email.