Skip to main content
Entire plugins use two credentials. You sign a plugin JWT with your own key to talk to a Core. You exchange it for an access token to talk to a repository’s region, or to create a repository on a Core. Your service never holds customer passwords or long-lived tokens. See Building a Plugin for the full flow.

Plugin JWTs

Sign a fresh JWT for each call, or reuse one for a few minutes: Header: "alg": "EdDSA", and "kid" when you registered a JWKS URL.

Access tokens

Mint an access token with the access-tokens endpoint. What the token can reach depends on what you ask for: Hand only a token scoped to one repository to code you trust less than your service, such as a customer’s build job. Cache tokens until shortly before they expire. Entire limits how many tokens one installation can mint, and answers 429 rate_limited with a Retry-After header, in seconds, when you exceed it. Send credentials only to hosts under entire.io that Entire named: a Core, or an api_base_url from the repository list. See Regions and routing.