Skip to main content
The Entire API has two layers. The control plane (a Core, one per jurisdiction such as US or EU) manages organizations, projects, repositories and plugin installations. The region API holds repository data: contents, branches, check runs. Every call needs a bearer token, and the token decides which layer accepts it. See Authentication for the credentials and Regions and routing for which host to call.

​
Two ways in

Use your own login

Automate your own work. entire auth token prints your bearer token. Call the API over HTTP, through entire api, or with the Go SDK.

Build a plugin

Act on repositories that customers share with your service. Install flow, receipts, installation tokens and the SDK’s plugin package. Selected partners only.
The endpoint reference in the sidebar has two parts: accounts, projects and repositories on Core, and repository data on the region API.
The plugin API is the only way for a third-party service to obtain a token today, and it is open to selected partners only. Every other endpoint is reachable with your own login, and may change without notice.