---
search:
  tags:
    - Ad groups
    - GET
seo:
  description: >-
    Available on: Meta TikTok Google Ads. Reference for the GET
    /observe/{advertiserId}/ad-groups/{id} endpoint in the AdCrunch API.
sidebar:
  label: Get one ad group
  badge: GET
title: Get one ad group
type: openapi-operation
---
**Available on:** [![Meta](/providers/meta.svg)](https://docs.adcrunch.dev/connect/providers) [![TikTok](/providers/tiktok.svg)](https://docs.adcrunch.dev/connect/providers) [![Google Ads](/providers/gads.svg)](https://docs.adcrunch.dev/connect/providers)

Live read. Asks the provider for one ad group now, and gives its payload with the field names of the provider.

The keys are the provider’s, and so is the shape. A Meta ad set answers `id`, `name`, `campaign_id`, `status`, its two budget fields, its bid as `bid_strategy`, `bid_amount` and `bid_constraints`, and its schedule as `start_time` and `end_time`; a TikTok ad group answers `adgroup_id`, `budget_mode`, `optimization_goal`, `billing_event` and `placement_type`; a Google Ads ad group answers `id`, `name`, `status` and `campaignId`.

**The payload holds the fields AdCrunch asks the provider for, and no more.** Targeting is outside that set at every provider, so no payload here carries it.

### Money

AdCrunch changes one thing in the payload: the money of Meta, `bid_amount`, `daily_budget` and `lifetime_budget`. Meta writes each amount in a unit that depends on the currency. This read gives each one as a number in **whole units** of the currency of the advertiser. It is the unit of `budget` on a row: `250` is 250.00. When AdCrunch does not know the currency of the advertiser, each of these fields is `null`.

A TikTok amount is in whole units already, so it does not change. A Google Ads field whose name ends in `Micros` states its unit, so it stays in micros: `12340000` is 12.34.

### When there is nothing to give

**`404`** — the provider holds no such ad group on this ad account, the provider has no ad group at all, or your organization does not own the advertiser in the path. They are deliberately not told apart: distinguishing them would confirm that a ad group exists to somebody who cannot read it.

`GET /observe/{advertiserId}/ad-groups/{id}`

**Responses**

- `200` — The payload the provider holds now, with the money of Meta in whole units.
- `400` — The request does not match the schema of this operation: a field is missing or has the wrong type, or the body is not valid JSON. \`error\` is \`invalid\_request\`, and \`issues\` names each field. Nothing was changed.
- `401` — No API key, or one that does not resolve. See the security scheme. \`error\` is \`unauthorized\`.
- `402` — The organization has no active subscription. An owner subscribes at \`paywallUrl\`. \`error\` is \`organization\_unentitled\`.
- `403` — The caller does not hold \`observe:read\`. \`error\` is \`forbidden\`.
- `404` — The provider holds no such entity on this ad account, the provider does not have this kind of entity, or your organization does not own the advertiser in the path. They are deliberately not told apart. \`error\` is \`not\_found\`.
- `409` — This advertiser has no usable connection to its provider. A person must reconnect it. The stored read of the same resource, with \`advertiserId\`, still answers what AdCrunch holds.
- `501` — AdCrunch cannot read this resource live from this advertiser’s provider. It is permanent. Read the stored copy instead, at the same resource without the advertiser in the path and with \`advertiserId\`.
- `502` — The provider refused the request, or could not answer it. This failure is often transient. Send the request again.

Response example, 200:

```json
{
  "account_id": "1203456789012345",
  "bid_amount": 12.5,
  "bid_strategy": "COST_CAP",
  "campaign_id": "120210000000000",
  "created_time": "2026-09-16T23:06:40+0000",
  "end_time": "2026-12-31T23:59:00+0100",
  "id": "120210000000001",
  "name": "Women 25-44, France",
  "start_time": "2026-09-17T00:00:00+0200",
  "status": "ACTIVE",
  "updated_time": "2026-09-20T10:26:40+0000"
}
```
