**Source URL:** https://limited.veevavault.dev/regulatory/vault-api/api-reference/22.3/authentication.md

# Authentication



Authenticate your account using one of the methods outlined below. The response returns a session ID that you can use in subsequent API calls. Session IDs time out after a period of inactivity, which varies by Vault. Learn more about [session duration and management](/vault-api/explanation/session-management).

After acquiring a Vault Session ID, include it on every subsequent API call inside the `Authorization` HTTP request header.

## Basic Authorization {#basic-authorization}

<FieldTable>
| Name | Description |
| --- | --- |
| `Authorization` | {`sessionId`} |
</FieldTable>
Alternatively, you can use Salesforce or OAuth2/OIDC Delegated Requests.

The Vault API also accepts Vault Session IDs as Bearer tokens. Include `Bearer` keyword to send Vault Session IDs with as bearer tokens:

## Bearer Token Authorization {#bearer-token-authorization}

<FieldTable>
| Name | Description |
| --- | --- |
| `Authorization` | Bearer {`sessionId`} |
</FieldTable>

---

**Previous:** [Run in Postman](/regulatory/vault-api/api-reference/22.3/run-in-postman)  
**Next:** [User Name and Password](/regulatory/vault-api/api-reference/22.3/authentication/user-name-and-password)