App Store 5.2.2 rejection: Third-party service authorization
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps accessing, displaying, or monetizing content from another service.
An integration can work technically while falling outside the service’s permitted uses. Under 5.2.2, the service’s terms must specifically allow your access or use, and Apple can ask for authorization.
Compare the feature with the permission
Record the service, endpoint, content shown, and any payment connected to it. Read the terms for your actual API or account type. We’d check caching, redistribution, and monetization separately; permission to sign in doesn’t necessarily cover selling access to the service’s content.
Adjust the integration
Obtain the necessary authorization or remove the unsupported behavior. Keep documentation linking the permission to the app and submitting organization. If Apple has misunderstood a licensed integration, provide the relevant terms and a concise explanation of the permitted use.
Test the revised flow and inspect stored or cached content left behind. Give Apple the service name, authorization, and steps to see the compliant feature. A public website or functioning API key isn’t, by itself, evidence of permission for every use.
Messages this guide can help with
App Store 5.2.2 rejection; app store 5.2.2 denial; Guideline 5.2.2; Third-party service authorization
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 5.2.2 Checked 22 September 2026