# Layers Partner API (/docs/api)



Layers is the platform you embed in your product. The Partner API is the one REST surface your application calls to ingest a customer, instrument them with the Layers SDK, generate and approve content, publish across their social accounts, and read back organic and paid performance. API keys are scoped to your Layers organization, every long-running operation returns a `jobId` you poll on the same envelope, and one set of error codes covers the whole surface.

## Where to start [#where-to-start]

<Cards>
  <Card title="Quickstart" href="/docs/api/getting-started/quickstart" description="Create a key, create a project, kick off your first job. About ten minutes." />

  <Card title="Core concepts" href="/docs/api/concepts/jobs" description="Jobs, projects, approval, scopes — the handful of ideas you need to hold in your head." />

  <Card title="API reference" href="/docs/api/reference" description="Every endpoint, grouped by domain. Request, response, error codes." />
</Cards>

Three onboarding paths depending on what you have to work with. Pick the one that fits.

<Cards>
  <Card title="GitHub path" href="/docs/api/getting-started/quickstart" description="You have the customer's repo. We clone it, derive brand context, open an SDK-install PR. ~10 min." />

  <Card title="App Store path" href="/docs/api/getting-started/quickstart-mobile" description="You have a shipped iOS/Android app but no repo. We scrape the store listing for brand context. ~5 min." />

  <Card title="Manual / no ingest" href="/docs/api/getting-started/quickstart-manual" description="Weekend prototype, Godot/Unity build, internal tool — no repo, no store listing. Drop in the SDK by hand and fill the brand block yourself. Under 5 min." />
</Cards>

## How this API is organized [#how-this-api-is-organized]

The docs split three ways. **Concepts** explain the durable ideas — the job envelope, projects as customer scope, the approval gate, scopes on a key. Read these once. **API reference** is the lookup surface: every endpoint with its method, path, request shape, response shape, and error codes. **Guides** walk through end-to-end flows — onboarding a customer, cloning a top performer, requesting leased TikTok accounts — and call into both of the other sections.

If you're new, start with the [Quickstart](/docs/api/getting-started/quickstart), then read [Jobs](/docs/api/concepts/jobs), then come back to the reference when you're wiring real code.