Apps that pull in, embed, or build functionality around another company's site, API, or product beyond a standard public API need to show they have permission from that third party — Apple may ask for a letter or written authorization.
Commonly triggered by apps that scrape or wrap another company's website or service without any formal agreement in place.
"Your app integrates content or services from a third party, but we could not confirm you have appropriate permission to do so, per guideline 5.2.2."
Guideline 5.2.2 covers apps that rely on another company's site, API or product in ways that go beyond a standard public interface. In those cases the developer needs to show that they have permission, and Apple may ask for written authorisation. It commonly appears when an app scrapes or wraps another company's website without any agreement.
A service that depends on another company's platform can stop working or cause legal disputes if that company objects. For users, an app that is later cut off becomes useless. For the third party, an unofficial client may violate terms, bypass controls or harm the service. Asking for permission keeps apps built on others' services on solid legal and practical ground.
Standard use of a public API under its terms usually does not need special permission.
A letter, agreement or other document from the third party.
Only if it respects the third party's terms and does not mislead users.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.