Skip to main content
Deprecated. This page documents the v2 buyer API, which is closed to new API clients and switches off on 1 December 2026. Use V3 instead: see Move a v2 buyer REST integration to V3. The conversion endpoint, Log event, stays open.
POST /api/v2/buyer/storefronts/{storefrontId}/direct-billing-acceptance Records direct-billing approval for one selected seller. The approval is buyer account × seller, not advertiser-specific, so it applies to all current and future advertisers. The caller must have the ADMIN or SUPER_ADMIN account role.
This endpoint is only for billing choices owned by the buyer account. If your account joined through a seller-sponsored link, the seller fixed the billing path on that link and you cannot approve or change it. A sponsored direct-billing path already carries the seller’s authority, so no separate buyer acceptance is required.
Set the billing policy to operator first. Acceptance allows eligible advertisers to move from Action required to Provisioning. It does not lock the billing policy by itself; the policy locks when Apostra dispatches the first real eligible activation.

What the seller receives

When Apostra asks the seller to open the account for an advertiser, it names the business the seller should invoice: the advertiser’s media billing entity, resolved from the advertiser, then its account, then your organization’s primary entity. The seller receives the entity’s legal name, tax ID, postal address, and billing email addresses (up to ten), as the AdCP billing_entity on sync_accounts. An advertiser with no resolved media billing entity stays at Action required until you add one, and the seller is not contacted. The same applies when the entity is longer than AdCP allows: a legal name over 200 characters, a street address over 200, a city over 100, a postal code over 20, or a tax ID over 30.

Request

The request has no body.

Parameters

Response

Errors

  • 400 VALIDATION_ERROR — the ID is invalid or direct billing is not the selected policy.
  • 401 UNAUTHORIZED — the bearer token is missing or invalid.
  • 403 FORBIDDEN — the caller is not an account administrator, or the account is seller-sponsored and its billing path is controlled by the seller.
  • 409 CONFLICT — the seller is not selected, the policy is locked, or the current selection changed while acceptance was recorded.
See Errors for the full error contract.

Update billing policy

Select direct billing while the policy is unlocked

Media Partners overview

Understand selection, billing, and advertiser activation