# Refresh competitor paid ads

Look for an iOS app's newest paid ads now instead of waiting for the next scheduled pass.

## Endpoint: POST /v1/competitors/{platform}/{storeId}/paid-ads/refresh

- Method: `POST`
- Path: `/v1/competitors/{platform}/{storeId}/paid-ads/refresh`
- Authentication: Bearer API credential or OAuth access token
- Required scope: `content:write`
- MCP tool: `refresh`
- MCP action: `ad_refresh`

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `platform` | path | ios | yes | Paid-ad refresh supports iOS apps. |
| `storeId` | path | numeric string | yes | Apple App Store identifier. |

## Known errors

- 400 invalid_request for an invalid filter, identity or limit.
- 401 authentication_required for a missing or invalid credential.
- 402 subscription_required when access is not entitled.
- 403 authorization_required for a missing scope or unavailable preview access.
- 403 workspace_not_accessible when x-genviral-tenancy names a workspace the credential cannot reach.
- 404 not_found when the record is outside the accessible catalogue.
- 429 rate_limited; honor Retry-After when present.
- 429 daily_call_limit; the plan's daily API and MCP calls are used until 00:00 UTC.
- 409 conflict when the write would duplicate an exclusive row.

## Request

No request body. Send an Idempotency-Key when a client may retry.

```
curl --request POST 'https://api.peekpanda.com/v1/competitors/ios/0000000000/paid-ads/refresh' \
  --header "Authorization: Bearer $PEEKPANDA_TOKEN" \
  --header 'x-genviral-tenancy: personal'
```

## MCP request

Call refresh with action ad_refresh. Path fields go in params, filters in query, and a write body in body.

```
{
  "name": "refresh",
  "arguments": {
    "request": {
      "action": "ad_refresh",
      "params": {
        "platform": "<platform>",
        "storeId": "<storeId>"
      }
    }
  }
}

```

## Response

state is running, completed, limited, unavailable or failed. Always inspect state, even after HTTP success. A refresh answers running: charged is true when it started a new walk, and false when the app's walk was already running and the request joined it. limited and unavailable are never charged, and a walk that ends failed is refunded and can be retried. retryAt says when a new request can succeed. Read the status for the outcome; its latest.state not_matched means no advertiser has the exact app name.

```
{
  "appStoreId": "0000000000",
  "state": "running",
  "charged": true,
  "retryAt": null,
  "latest": {
    "state": "running",
    "requestedAt": "2026-09-24T08:00:00.000Z",
    "settledAt": null,
    "newAdCount": null
  },
  "quota": {
    "kind": "daily",
    "limit": 3,
    "used": 1,
    "remaining": 2,
    "resetAt": "2026-09-25T08:00:00.000Z"
  }
}

```

## Source

Public ads from the app's own advertiser page, matched by its exact app name. Ads are attributed only when the advertiser matches; no looser name matching is used.

## Refresh

A refresh walks the advertiser from its newest ad. This endpoint has its own quiet daily limit, separate from your plan's tracked-app number: 1 on Peek and 3 on Panda, in a rolling 24 hours, shared by a workspace. A refresh always walks the advertiser again; while an app's walk is still running, a refresh by anyone joins that walk and is not counted. A failed refresh is not counted at all.