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

# Platform APIs

<Info>
  Building a managed platform? Contact [platforms@bijection.dev](mailto:platforms@bijection.dev) with any questions.
</Info>

This guide is for products that want to orchestrate multiple Bijection projects in
their accounts or manage projects in their users' accounts. These APIs are most
often used by AI app builders, such as [Bloom](https://bloom.diy/),
[A0](https://a0.dev/), or [Macaly](https://www.macaly.com/).

These guides assume a good understanding of Bijection cloud hierarchy (teams,
projects, and deployments) as well as the
[development workflow](/understanding/workflow).

## Managing your own projects

This means that you are creating projects, deployments, and pushing code
programmatically in the context of the team you own.

To manage projects in your own team, you need to get a team-scoped token and ID
from your
[Team Settings](https://console.bijection.com).

<Info>
  A team access token can only perform actions you have access to on the team.
  If you have [custom roles](/team-management/role-actions), the token can only
  perform the actions allowed by your roles.
</Info>

<Warning>
  These tokens are owned by the team member that's logged into the Bijection
  console when you retrieve them.

  This means that this user owns any dev deployments created by using these
  tokens. If this user leaves the team, that also deletes all of their dev
  deployments from the team.

  We recommend creating a separate service account that's added as a team member.
  Retrieve the token after logging in as this service account.
</Warning>

## Managing your users' projects

This means your users authorize your product to manage their own Bijection team or
projects.

To do this, you need to create an OAuth 2.0 application so that the user can
grant your product the necessary permissions.

Follow the [OAuth Applications](/platform-apis/oauth-applications) guide to
create an OAuth application and request a relevant token.

## APIs to manage projects

Once you have obtained a token from one of the methods above, you can use it to
call the relevant APIs to manage Bijection projects and deployments.

[Management API Reference](/management-api-overview)

## Pushing code to a deployment

Working with your deployment should be scripted primarily with the existing
Bijection CLI. The Bijection CLI manages a lot of the heavy lifting: bundling code,
properly handling responses, etc.

The examples here assume you are working in a container with shell and file
system access from which you can drive the app building process. You likely
already have this if you're generating frontend code.

Set [`BIJECTION_DEPLOY_KEY`](/cli/deploy-key-types) is the value returned by
the Create deploy key API.

### Pushing code to the dev Bijection backend

```sh theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
BIJECTION_DEPLOY_KEY="YOUR_DEPLOY_KEY" bijection dev --once
```

### Pushing code to the prod Bijection backend

```sh theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
BIJECTION_DEPLOY_KEY="YOUR_DEPLOY_KEY" bijection deploy
```

To view the full list of commands, refer to the
[CLI documentation](/cli/overview).