Credentials

Credentials store the authentication details VendorGate needs to connect to external systems. Keeping credentials separate from pipeline configuration makes it easy to rotate secrets and reuse the same credential across multiple resources.

Supported credential types

VendorGate supports several credential types out of the box:

• SFTP / FTP: username and password or private key.
• API (api): API keys, bearer tokens, basic auth, OAuth2 client credentials, mTLS, or query-param authentication for REST sources, destinations, and monitors.
• S3-compatible storage: access key, secret key, and bucket.
• Database: connection strings for supported databases.
• Webhook: endpoint URLs and signing secrets for alerts.
• LLM Provider: provider, model, API key, and optional base URL for LLM mappings in standardizers.

Creating a credential

1. Go to Credentials in the application.
2. Click New Credential.
3. Select the credential type.
4. Enter the required fields. The exact fields depend on the type.
5. Give the credential a clear name so you can identify it when building pipelines and monitors.
6. Save.

Using credentials

When you create a pipeline source, delivery destination, or API monitor, you choose a credential by name. VendorGate retrieves the secret details at runtime. You never need to paste secrets into pipeline or monitor configuration.

Security

Credentials are encrypted at rest and are never returned in API responses or displayed in the UI after creation. If a credential changes, update it in one place and all resources that use it will pick up the new value on their next run.

Rotating a credential

1. Open the credential you want to update.
2. Edit the secret fields.
3. Save.

Existing pipelines and monitors automatically use the updated credential for future runs.