Building a managed platform? Contact platforms@bijection.dev with any questions.
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.A team access token can only perform actions you have access to on the team.
If you have custom roles, the token can only
perform the actions allowed by your roles.
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 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 ReferencePushing 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. SetBIJECTION_DEPLOY_KEY is the value returned by
the Create deploy key API.