---
title: Ads Endpoints
framework: Apple Ads Platform API
role: collectionGroup
role_heading: API Collection
platforms: [apple ads platform api 1.0+]
path: apple-ads-platform-api/ads-endpoints
---

# Ads Endpoints

Create, retrieve, update, and delete ads using these endpoints.

## Overview

Overview An Ad object connects a Creative to an ad group. The ad is the serving unit: It tells the system which ad creative to show when the ad group wins an auction. An ad group can contain multiple ads, but only one ad per ad group can be ENABLED at a time. Enabling a different ad requires pausing the one currently serving. Creating an ad requires a name, a status, the adGroupId of the target ad group, and a creativeId referencing an existing Creative. Create the ad creative first, then reference its id here. The campaignId, adAccountId, and other system fields are read-only, and the system populates them automatically at creation. Use the Ads Endpoints Use these endpoints to create, retrieve, update, and delete ads:  |  |   |  |   |  |   |  |   |  |   |  |  Track Ad Status and System Status Ads have three status fields that together determine whether an ad is serving: status: The advertiser-controlled field. Set it to ENABLED to let the ad serve, or PAUSED to stop delivery without deleting the ad. You can only update status and name after creation. systemStatus: A system-computed field that reflects whether the ad is actually running. A value of RUNNING means the ad is active and eligible to serve, and a value of NOT_RUNNING means the system identified a condition that’s preventing delivery. displayStatus: A system-computed field that represents a rolled-up label combining status and systemStatus into a single delivery state. See AdDisplayStatus for all values. When systemStatus is NOT_RUNNING, the system populates the systemStatusReasons array with one or more values explaining why. Reasons marked App Store-specific apply only to App Store ads. Unless marked, a reason applies to both App Store and Apple Maps ads:  |   |   |   |   |   |   |   |   |   |   |   |   |   |   |   |   |   |   |   |   |  Interpret System Status Limiting Reasons When an ad is running but delivering at reduced capacity, the system populates the systemStatusLimitingReasons array. Unlike systemStatusReasons, these reasons don’t stop delivery. Instead, they constrain reach. There’s one possible value, CREATIVE_POLICY_ISSUES, which means the ad creative associated with the ad has policy conditions that limit but don’t fully stop delivery. Understand Apple Review Requirements Apple must approve ads before they can serve. For App Store ads, the review covers the ad creative content and product page. For Apple Maps ads, the review covers the brand ad creative instead. The CREATIVE_PENDING and CREATIVE_INVALID reasons reflect this review state. While an ad is under review, systemStatus is NOT_RUNNING and systemStatusReasons includes AD_APPROVAL_PENDING or CREATIVE_PENDING. Once Apple approves the ad, systemStatus changes to RUNNING unless the advertiser sets status to PAUSED or schedules a future start date.

## Topics

- [Create an Ad](apple-ads-platform-api/post-ads.md)
- [Query Ads](apple-ads-platform-api/post-ads-query.md)
- [Get an Ad](apple-ads-platform-api/get-ads-_id_.md)
- [Update an Ad](apple-ads-platform-api/put-ads-_id_.md)
- [Delete an Ad](apple-ads-platform-api/delete-ads-_id_.md)

## See Also

### Ads

- [Ads Data Objects](apple-ads-platform-api/ads-data-objects.md)
- [Ads Data Types](apple-ads-platform-api/ads-data-types.md)