***

title: Content Gateway Authentication
description: Supported authentication methods for the Moveworks Content Gateway
-------------------------------------------------------------------------------

## Supported Authentication

Here are the supported authentication types with Content Gateway:

### API Key Auth

API Key authentication entails sending an API key in the header.

**Required Info:**

* `API Key` — Your actual API key value. This will be sent as the value for the `Authorization` header key.

**Additional Info:**

* `Custom Base Url` — In case you have a different custom base URL for the connector, you can specify it here.

***

### OAuth 2.0 with Client Credentials

OAuth 2.0 with Client Credentials grant type entails sending a valid Client ID and Client Secret in exchange for an Access Token. This Access Token is then used in subsequent requests as a Bearer Token to authenticate the API request.

**Required Info:**

* `Client ID` — Your actual Client ID value.
* `Client Secret` — Your actual Client Secret value.
* `Oauth2 Token Url` — The **full** token URL.

**Additional Info:**

* `Client Authentication Method` — Moveworks will try making the request with both Basic Auth and Request Body Auth by default.
* `Custom Base Url` — In case you have a different custom base URL for the connector, you can specify it here.
* `Encrypted Authentication Header` — If needed, you can configure additional headers for the auth request. Data will be sent in the header like so:

```bash
curl --location 'URL' \
  --header 'x-api-key: <YOUR-ENCRYPTED-KEY-HERE>'
```