> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Building on Apostra: common questions

> Short answers to the five questions builders ask first: account structure, how Apostra objects map to platform objects, which platforms are live, what the API cannot do, and how to build end to end in the sandbox.

These are the questions builders ask first. Each answer is short and links to the
page that holds the detail.

## Should I use one account for all my clients, or one account per client?

Start with one Buyer Account and an advertiser for each client. It is the
simplest shape, and one API key reaches every client. Give a client its own
child Buyer Account when its own people need to sign in to Apostra, or when it
needs a different billing choice with a seller.

This also fits the common case where each client connects its own social ad
account and pays the platform directly. You connect each client's ad account
and map it to that client's advertiser, and the platform bills the client. See
[Choose an account shape](https://docs.apostra.com/v3/several-client-accounts.md#choose-an-account-shape)
and
[When each client connects its own ad account](https://docs.apostra.com/v3/several-client-accounts.md#when-each-client-connects-its-own-ad-account).

## How do Apostra's objects map to a platform's?

An Apostra campaign holds a goal, a budget and a flight, and can hold media buys
with several sellers. Each media buy becomes a campaign on the platform, each
package becomes the platform's ad group, ad set, ad squad or line item, and each
creative assignment becomes an ad. On Meta that is campaign, ad set and ad. On a
DSP it is usually campaign and line item. You control every level: budget,
targeting, pacing, bids and creatives, and you can move budget between buys.
Whether a live change goes through depends on what that platform takes. Where it
does not, you add a separate media buy. See
[How Apostra objects map to platform objects](https://docs.apostra.com/v3/concepts.md#how-apostra-objects-map-to-platform-objects)
and [Change a live media buy](https://docs.apostra.com/v3/change-a-live-media-buy.md).

## Which ad platforms are live, and what does Testing mean?

Apostra connects to Meta, TikTok, Snap, Pinterest, Reddit, Spotify, LinkedIn,
Google Ads, Amazon Ads and OpenAI Ads. Google Ads is supported. Microsoft (Bing)
Ads is on the roadmap, with no date. Testing is a label on one product or step,
not on a whole platform. It means Apostra is validating the workflow before
offering it broadly. Most of it works, and some platform-specific pieces are
still being finished. The platform's compatibility page lists what is Available,
Partial, Testing or Planned. See
[Which ad platforms are connected, and what Testing means](https://docs.apostra.com/v3/limitations.md#which-ad-platforms-are-connected-and-what-testing-means)
and [Ad platform compatibility](https://docs.apostra.com/v2/guides/ad-platform-compatibility/index.md).

## What can the API not do?

Some features exist only in a platform's own interface, such as Snap lenses or
Google's competitive bid research. Apostra can only use what the platform's API
offers. A missing feature is an action Apostra cannot take. It does not narrow the
delivery data Apostra reads. Apostra adds
a one-off platform feature when a customer needs it, as an AdCP extension. See
[What the API does not do](https://docs.apostra.com/v3/limitations.md#what-the-api-does-not-do).

## Can I build end to end in the sandbox, and what tooling is there?

Yes, up to a point. A sandbox advertiser can run a buying flow from a campaign
through proposals to a staged media buy against the Apostra synthetic seller,
with no spend. The sandbox covers discovery and staging. It does not launch on a
real platform or show real delivery. More partner sandboxes are planned. For tooling,
install the `apostra-developer` plugin in Claude Code or Codex, which adds the
Build with Apostra skill and the MCP connection. A buyer who only runs
campaigns can install the [buyer plugins](https://docs.apostra.com/v3/buyer-plugins.md) instead. For code,
use the TypeScript or Python SDK. The MCP server and the SDKs call the same public V3 operations. See
[Build end to end in the sandbox](https://docs.apostra.com/v3/developer-quickstart.md#build-end-to-end-in-the-sandbox),
[Skills, the plugin, the repository and the SDKs](https://docs.apostra.com/v3/developer-quickstart.md#skills-the-plugin-the-repository-and-the-sdks)
and the [SDK guide](https://docs.apostra.com/v3/sdk-guide.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.