Skip to main content
POST
ProvisionManagedOrganizationAdsContainerAPI gives a managed org its own Google Ads container in

Authorizations

Authorization
string
header
required

An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).

Path Parameters

orgSlug
string
required

Body

application/json
currency_code
string
descriptive_name
string
time_zone
string

Response

Success response

already_provisioned
boolean

delegated connection under this manager's MCC, which was returned instead of creating a second sub-account.

billing_configured
boolean

setup, which is what decides whether it can serve. A container is created with none: Google's BillingSetupService can only attach one programmatically for customers on monthly invoicing, so until the MCC is approved for that, somebody has to link a payments profile in the Google Ads UI. Saying so here is the difference between a known remaining step and one discovered at go-live, when the campaigns are built and nothing serves.

billing_status
string

APPROVED_HELD, CANCELLED. Two values are ours rather than Google's: "none" when the account has no billing setup at all, and "unknown" when the check itself could not be made. Those are different facts and a caller gating go-live must not read the second as the first — an unreadable answer is a reason to go and look, not evidence of absence.

customer_id
string

under the manager's MCC).

descriptive_name
string

Empty when AlreadyProvisioned: Erdo does not store Google's display name, and re-reading it would put a Google call on the idempotent path.

integration_id
string<uuid>
login_customer_id
string

the id every request against CustomerID is sent in the context of.

org_slug
string