Add restrictions to an existing token without needing the private key.
Attenuation is a Biscuit cryptographic feature that allows anyone holding a token to add restriction blocks. The resulting token can only do a subset of what the original token could do—restrictions cannot be removed.
This endpoint requires authentication with token read permission.
Cryptographic guarantee: Attenuation can only reduce permissions, never expand them. The Biscuit format ensures restriction blocks are append-only and cannot be removed without invalidating the signature.
Self-service by design: Users can only attenuate tokens they already possess. If you have a token, you can create a weaker version of it—this is analogous to being able to share read-only access to something you own.
No privilege escalation: The attenuated token inherits all existing restrictions from the source token, plus any new ones added. A read-only token cannot be attenuated into a read-write token.
All timestamps use UTC in ISO 8601 / RFC 3339 format. The Adaptyv API runs
in AWS eu-central-1 (Frankfurt), and all time comparisons are in UTC.
For the cryptographic properties of token attenuation, see the Biscuit documentation.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Request to attenuate (restrict) an existing token.
Attenuation is a Biscuit cryptographic feature that adds restriction blocks without needing the private signing key. Any authenticated user can attenuate their tokens to create limited-scope versions for delegation.
Token attenuated successfully
Response after attenuating a token.
The attenuated token string. Format: abs0_{slug}{biscuit_base64}.