# Product Pages Endpoints Retrieve product pages and their localized details. ## Overview Product pages are the App Store listings that users land on after tapping an ad. You create and manage them in App Store Connect. The Apple Ads Platform API provides read-only endpoints to discover, retrieve, and inspect them. Product pages serve as the post-tap destination in a [`Creative`](/documentation/Apple-Ads-Platform-API/Creative) object and determine which app experience users see after they tap your ad. Use [Search Apps Endpoints](/documentation/Apple-Ads-Platform-API/search-apps-endpoints) to find an app’s `adamId` before looking up its product pages, and confirm the app is eligible to advertise with [App Eligibility Endpoints](/documentation/Apple-Ads-Platform-API/app-eligibility-endpoints) before building a creative around one of its product pages. ## Call the Product Pages Endpoints Use these endpoints to discover, retrieve, and inspect product pages: |Method|Path |Description | |------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |`POST`|`/v1/product-pages/query` | retrieves product pages (DPP, CPPs, PPOs) available to the authenticated ad account. | |`GET` |`/v1/product-pages/{productPageId}` | retrieves a single product page (DPP, CPP, or PPO) by its ID. | |`POST`|`/v1/product-pages/locale-details/query`| retrieves localized metadata for product pages. | |`POST`|`/v1/apps/{adamId}/locale-details/query`| retrieves the Default Product Page’s localized metadata for an app by its Adam ID.| ### Compare the Default with Custom Product Pages The endpoint you call depends on whether you need the app’s default listing or a specific custom product page: |Type |How to Fetch | |-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| |Default product page (main listing)|Use with `adamId` in the path.| |Custom product pages (CPPs) |Use with a `productPageId` filter. | ### Use the Default Product Page Every app has exactly one Default Product Page (DPP). It reflects the app’s standard App Store listing: the same screenshots, preview videos, app name, and description that all users see by default. You don’t need any additional setup to use it for advertising. When creating a creative for a default product page, set `creativeType` to `DEFAULT_PRODUCT_PAGE` and reference the app by its `adamId` in the creative’s `destination` field. To retrieve the DPP’s localized assets for a given app without needing a `productPageId`, use [`Query App Locale Details`](/documentation/Apple-Ads-Platform-API/Query-Default-Product-Page-Locale-Details-by-Adam-ID). ### Use Custom Product Pages Custom Product Pages (CPPs) are alternate product pages you configure in App Store Connect with tailored screenshots, preview videos, and promotional text. You design each CPP for a specific audience or campaign goal, showing a different app experience to different users without changing your default listing. A custom product page has its own `productPageId`, which you use in the creative’s `destination` field alongside the app’s `adamId`. Set `creativeType` to `CUSTOM_PRODUCT_PAGE` when creating a creative for a CPP. To retrieve product pages available to the authenticated ad account, use [`Query Product Pages`](/documentation/Apple-Ads-Platform-API/Query-Product-Pages). This endpoint returns all three product page types (DPP, CPP, and PPO). To fetch a specific page by its `productPageId`, use [`Get Product Page by ID`](/documentation/Apple-Ads-Platform-API/Get-Product-Page-by-ID). ### Reference a Product Page in a Creative Product page creatives use the `destination` field to define the post-tap App Store listing. The `adamId` and `productPageId` belong in `destination.parameters`, not directly on `destination`. ### Retrieve Locale Details Each product page has per-locale metadata describing how the app appears for a given App Store country or region and language. Locale details include: - **`appName`**: The localized app display name as it appears on the App Store. - **`subTitle`**: The app subtitle for the locale. - **`promotionalText`**: Up to 170 characters of promotional copy. - **`deviceClasses`**: Supported device classes (`IPHONE`, `IPAD`) for the locale. - **`assetsByDevice`**: Screenshots and preview videos organized by device type via [`DeviceAssetGroup`](/documentation/Apple-Ads-Platform-API/DeviceAssetGroup), with fallback devices when assets aren’t available for a given class. To retrieve locale details for any combination of product pages, App Store countries or regions, and languages in a single request, use [`Query Product Page Locale Details`](/documentation/Apple-Ads-Platform-API/Query-Product-Page-Locale-Details). ## Topics [`Query Product Pages`](/documentation/Apple-Ads-Platform-API/Query-Product-Pages) [`Get Product Page by ID`](/documentation/Apple-Ads-Platform-API/Get-Product-Page-by-ID) [`Query Product Page Locale Details`](/documentation/Apple-Ads-Platform-API/Query-Product-Page-Locale-Details) [`Query App Locale Details`](/documentation/Apple-Ads-Platform-API/Query-Default-Product-Page-Locale-Details-by-Adam-ID) ## See Also [Search Apps Endpoints](/documentation/Apple-Ads-Platform-API/search-apps-endpoints) Browse the endpoints for searching apps and retrieving app details. [App Eligibility Endpoints](/documentation/Apple-Ads-Platform-API/app-eligibility-endpoints) Check whether apps qualify to run ads and look up rejection reasons for creatives. --- Copyright © 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)