REST API · Actions
Confirm action
Run a prepared action, after the user approved what it will do
POSThttps://api.apogee.ad/api/v1/actions/{id}/confirm
What it does
An action runs once (409 action_already_ran), within 24 hours (410 action_expired). The answer lists what was created (details: new ids; for a duplicated ad, the method that kept its post).
Request
POST /actions/{id}/confirm on https://api.apogee.ad/api/v1.
Path parameters
-
idstring path requiredAction id
Headers
-
Authorizationstring header requiredBearer apk_…: an API key with the scope of this route. -
Idempotency-Keystring header requiredA unique key per request, e.g. a UUID, reused when you retry it: the first answer comes back instead of a second write (idempotency).
-
Content-Typestring header requiredapplication/json
Body
-
confirmconstant requiredtrue = the user approved this action
Response
200.
-
idstring -
doneboolean -
messagestring -
typestring or null -
detailsarray of objects
Every answer carries X-Request-Id (give it to support), Apogee-Version: 2026-10-06, and the RateLimit and RateLimit-Policy headers; a replayed answer also carries Idempotent-Replayed: true.
Errors
Errors are application/problem+json with a stable code to switch on (all the codes).
| Status | Possible codes |
|---|---|
| 400 Bad request | idempotency_key_required, not_supported, request_refused, validation_failed |
| 401 Unauthorized | invalid_api_key |
| 403 Forbidden | account_not_connected, forbidden, insufficient_scope, meta_permission_denied, platform_permission_denied, upgrade_required |
| 404 Not found | not_found |
| 409 Conflict | action_already_ran, idempotency_in_progress, plan_already_launched |
| 410 Gone | action_expired, plan_expired |
| 412 Precondition failed | drive_not_connected, meta_not_connected, platform_not_connected |
| 422 Unprocessable content | budget_above_cap, idempotency_key_reused, launch_refused, missing_answers |
| 429 Too many requests | daily_read_cap, meta_rate_limited, platform_rate_limited, quota_exceeded, rate_limited |
| 500 Internal server error | internal_error |
| 502 Bad gateway | drive_error, launch_failed, meta_error, platform_error, upstream_error |
Example
With your key in APOGEE_API_KEY (create one):
curl -X POST 'https://api.apogee.ad/api/v1/actions/120200000000000001/confirm' \
-H "Authorization: Bearer $APOGEE_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"confirm": true
}'{
"id": "120200000000000001",
"done": false,
"type": "120200000000000001",
"message": "Thanks for your message! Our team answers you in a private message.",
"details": [
{}
]
}Access and cost
| Plans | Pro and Scale. |
|---|---|
| Scope | the action's own: actions (launch for create_campaign) (scopes). |
| Credits | 2 credits per change. A request that fails costs nothing, a replayed one neither (credits). |
| Rate limit | Confirmation: 30 per 15 minutes on Pro, 60 on Scale (rate limits). |
| Meta budget | Reads Meta: spends 1 unit of the account's Meta budget (1,800 per 15 minutes, 900 per ad account). |
| Daily cap | Counts 2 units toward the 2,000 units one API key can use in 24 hours. |
In the MCP
An AI assistant does the same with this tool of the MCP server:
execute_action: Runs a prepared action (or a prepared campaign), once, after your explicit OK. Returns what was created.
Related operations
- Create action:
POST /actions - Get action:
GET /actions/{id}