DocumentationApplications

Publisher verification

Who stands behind an application: a publisher profile, the documents a reviewer reads, and a verification status only staff can set.

A developer, several publishers

A publisher profile is the business — or the individual — an application goes out under. One developer may hold several; each application names the one it uses with GET/PUT /v1/developer/applications/{applicationId}/publisher. The consent screen shows the publisher's name above the release, and verified_publisher on the go-live checklist is about this profile.

POST /v1/developer/publisher-profiles creates one; GET, PATCH and DELETE …/{profileId} manage it.

Fields — all optional, each at most the length shown

publisherDisplayName
150 characters. The name people see when no verified legal name applies.
legalName
200 characters.
businessType
individual, sole_trader or company.
registrationNumber
80 characters.
registrationCountry
Two-letter country code.
businessAddress
300 characters.
websiteUrl
2048 characters.
supportEmail
A valid email address, up to 320 characters.
supportUrl
2048 characters.

Documents for the reviewer

POST …/{profileId}/documents takes one multipart file — a PDF, JPEG, PNG or WebP up to 10 MB — scans it, keeps it, and answers with the profile whose documents now lists it. DELETE …/{profileId}/documents/{documentId} removes one.

A document is for the person reading the submission. It is never shown to the people who sign in.

Submitting, and what staff decide

POST …/{profileId}/submit sends the profile for verification. verificationStatus is not writable by you at any point: it is a staff decision, so a developer cannot assert that their own business was checked.

Statuses

draft
Not yet submitted.
submitted, in_review
With UnifyID. Only draft can be submitted; a submitted profile waits.
verified
Approved. A live application may name this publisher.
rejected
Refused. Resubmission is allowed unless the decision said otherwise.
reverification_required
Was verified; UnifyID has asked for it to be checked again. Applications naming it stay live meanwhile.
withdrawn
No longer verified.

What this does not do

  • Verification is of the publisher, not the application. Passing it says somebody stood behind the name; it says nothing about what the application does.
  • An individual developer's production application that requests personal data is published under their verified legal name, whatever publisherDisplayName says. See What the person sees.

Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.