Developer, registration, and support readiness
5 published notes
- New
Public support requests now receive a reference and are stored as encrypted payloads for the staff support queue.
- Security
Registration records the current Terms and Privacy acceptance on the server before a profile photo can be stored or an account can complete.
- Improved
Developer quickstarts now include required country fields, JSON content type, idempotency, and the current hosted-verification URL.
- Improved
OIDC guidance now states the production limit of one exact HTTPS callback URL for each developer workspace.
- Fixed
Registration and public profile wording now distinguishes account setup, contact confirmation, and identity verification.