Skip to main content
Choosing the right authentication scheme determines how an integration proves its identity to the target service. Guild supports three schemes: API Key, OAuth 2.0, and No Authentication Required. You select the scheme during the integration creation wizard, and it controls which configuration fields are required.

​
Supported schemes

​
API Key

Use API Key when the target service authenticates requests with a static key. After selecting API Key in the creation wizard, fill in the required key fields before proceeding to the next step. On the integration detail page, these integrations display API Key as their auth scheme badge.

​
OAuth 2.0

Use OAuth 2.0 when the target service requires user authorization via the OAuth 2.0 flow. After selecting OAuth 2.0 in the creation wizard, provide the required OAuth configuration fields before proceeding. On the integration detail page, these integrations display OAuth 2.0 as their auth scheme badge.

​
No Authentication Required

Use No Authentication Required when the integration does not need any credentials, tokens, or user login to access the target service. After selecting No Authentication Required in the creation wizard, no additional fields are required — you can proceed to the next step immediately. On the integration detail page, these integrations display No Authentication Required as their auth scheme badge.

​
API reference

When creating an integration via the API, pass the following auth_config to use this scheme:
No additional fields are required.

​
Auth config ID

Each integration’s auth configuration has a unique ID. You need this ID — the auth_config_id — to mint a credential through the public API with POST /workspace_agents/{id}/credentials/api-key. To find it, open the integration’s Configuration tab and locate the ID field in the auth card, directly under the auth scheme. Use the copy button next to the field to copy the value.