--- title: Creatives Endpoints framework: Apple Ads Platform API role: collectionGroup role_heading: API Collection platforms: [apple ads platform api 1.0+] path: apple-ads-platform-api/creatives-endpoints --- # Creatives Endpoints Create, retrieve, update, and delete ad creatives through these endpoints. ## Overview Overview You create a Creative object at the ad account level, and an Ad object references it to define what users see when your ad serves. Ad creatives are reusable; you can link the same ad creative to multiple ads across different ad groups. Use the Creatives Endpoints Use these endpoints to create, retrieve, update, and delete ad creatives: | | | | | | | | | | | | Understand Creative Types The creativeType field determines the ad creative’s content source, how the pre-tap ad renders, and which placements it’s eligible for. You set the creative type at creation, and you can’t change it afterward. The following table summarizes each creative type, its pre-tap content source, and its post-tap destination: | | | | | | | | Define the Pre-Tap and Post-Tap Experience Every ad creative has two distinct content areas, creativeSpec and destination, each with a separate responsibility: creativeSpec: Defines the pre-tap experience, what users see before they interact with the ad. It contains the visual assets and copy rendered in the ad placement. destination: Defines the post-tap experience, where users land after they tap the ad. The Destination object specifies the destinationType and destination-specific parameters. These two fields operate independently. For product page ad creatives, creativeSpec is intentionally empty because App Store Connect controls the pre-tap rendering. Only destination carries meaningful data. For Apple Maps ad creatives, creativeSpec contains the Apple Maps creative spec with the brand’s visual content and promotional text. Understand Product Page Creatives For DEFAULT_PRODUCT_PAGE and CUSTOM_PRODUCT_PAGE creative types, creativeSpec is a product page creative spec object, which is intentionally empty. The pre-tap experience isn’t customizable through the API. All visual assets and copy come from App Store Connect. The destination object carries all required parameters for product page ad creatives: The destinationType field is set to APP_STORE_PRODUCT_PAGE. The parameters.adamId field is the App Store app identifier, and it’s required for both ad creative types. The parameters.productPageId field is the custom product page identifier, and it’s required for CUSTOM_PRODUCT_PAGE. Omit it or leave it null for DEFAULT_PRODUCT_PAGE. Understand Apple Maps Creatives For LOCAL_ADS_SEARCH_CREATIVE, creativeSpec contains an Apple Maps creative spec with the brand’s visual content and promotional text. The spec includes the following fields: | | | | | For Apple Maps ad creatives, the post-tap destination is always the Apple Maps place card. Set destination.destinationType to LOCAL_ADS_PLACECARD at creation. This destination type takes no parameters, since there’s no equivalent of adamId or productPageId to specify for a Maps place card. Track System Status and Eligibility Every ad creative has a systemStatus field that reflects whether the ad creative is ready to serve: | | | | When systemStatus is INVALID, the systemStatusReasons array contains one or more of the following values. Reasons marked Apple Maps ad creatives only or Product page ad creatives only apply exclusively to that creative type. Unless marked, a reason applies to both App Store and Apple Maps ad creatives: | | | | | | | | | | | | | | | Each ad creative also carries an eligibility field of type CreativeEligibility. The system returns eligibility data for ad creatives of every creativeType, including App Store product page ad creatives (DEFAULT_PRODUCT_PAGE, CUSTOM_PRODUCT_PAGE) and Apple Maps ad creatives (LOCAL_ADS_SEARCH_CREATIVE). It summarizes whether the ad creative meets the requirements to serve on each supported ad placement. Query Ad Creatives The Query Ad Creatives endpoint supports filtering ad creatives by creativeType, systemStatus, name, and eligibility.status using dot-notation, with observed values ELIGIBLE and INELIGIBLE. Look Up Rejection Reasons For product page ad creatives (DEFAULT_PRODUCT_PAGE, CUSTOM_PRODUCT_PAGE), detailed rejection information is available as CreativeRejectionReason records. These records are queried and fetched through endpoints documented under Apps > App Eligibility rather than under Creatives: see Query Rejection Reasons (POST /v1/rejection-reasons/apps/query) and Get Rejection Reasons (GET /v1/rejection-reasons/apps/{rejectionReasonId}). For Apple Maps ad creatives (LOCAL_ADS_SEARCH_CREATIVE), rejection information is available as policy assignment records instead, queried through the Brands endpoint: see Query Rejection Reasons for Brands (POST /v1/rejection-reasons/business-brands/query), filtered by the brand’s promotedObjectId. ## Topics - [Create an Ad Creative](apple-ads-platform-api/post-creatives.md) - [Query Ad Creatives](apple-ads-platform-api/post-creatives-query.md) - [Get an Ad Creative](apple-ads-platform-api/get-creatives-_id_.md) - [Update an Ad Creative](apple-ads-platform-api/put-creatives-_id_.md) - [Delete an Ad Creative](apple-ads-platform-api/delete-creatives-_id_.md) ## See Also ### Creatives - [Ad Creatives Data Objects](apple-ads-platform-api/creatives-data-objects.md) - [Ad Creative Data Types](apple-ads-platform-api/creative-data-types.md)