Guide summary
Interpret a REGISTERED Android Developer ID Status API response and complete the final release checks.
For: Developers who received a successful checker response and need to know what to record next.
Release sequence
- Confirm the query used the production package and, when supplied, the production fingerprint.
- Record the check timestamp and the artifact or release it applies to.
- Confirm policy, target API and store submission requirements separately.
- Repeat the check after signing-key or package ownership changes.
Quick facts
Registration status does not evaluate app content, permissions, target API level or a store's review decision.
Detailed guidance
What REGISTERED does and does not prove
When a certificate was included, REGISTERED confirms that the package-and-certificate pair matches the official record. Without a certificate, it only confirms that the package name is linked to a verified developer.
Save the state with the input, artifact digest and timestamp. Then continue with store review, target API, permissions, content policy and rollout checks.
- Recheck after signing-key changes.
- Recheck after package ownership transfers.
- Do not treat the result as store approval.
{
"state": "REGISTERED"
}Frequently asked questions
Can REGISTERED later change?
Ownership, key and official record changes can affect later checks, so treat the result as time-bound release evidence.
Does it confirm my APK is safe?
No. The state concerns registration identity, not malware, code quality or policy compliance.
Sources and review
Last reviewed: