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

# Connections

> Give workloads and agents access to third-party accounts without handing them the credential

A connection is one connected account at a third-party service. It lives in a vault of your Workspace. The credential stays in the vault: Akua only injects it into requests, and no API response ever returns it.

## Resources

| Resource | What it is |
| - | - |
| **Vault** | Holds connections and secrets. Every Workspace has a default vault, which is listed first. |
| **Connection** | One connected account. A new connection is `PENDING_CONSENT` until its key is set or OAuth consent completes. |
| **Connection policy** | Who may use the connection, for which operations, and until when. Without a binding, nobody can use it. |

## Connect an account

1. Create a connection in a vault with `POST /v1/vaults/{vault}/connections`.
2. Set its key with `POST /v1/vaults/{vault}/connections/{connection}:setCredential`, or complete OAuth consent. Akua verifies a key with the provider before storing it.
3. Bind each principal that should use the connection with `POST /v1/vaults/{vault}/connections/{connection}:setIamPolicy`.

## Revoke access

Revoking takes effect at once:

* Remove a principal's binding with `:setIamPolicy` to stop one principal.
* Revoke the connection with `POST /v1/vaults/{vault}/connections/{connection}:revoke` to stop all use.

See the [API reference](https://docs.akua.dev/apis/openapi.md) for every request and response field.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.