Credential Creation
Credential Creation
Before creating a BATCH integration, you need a credential. It ensures that only authorized systems can send and receive files in your integration, and makes it easier to track and revoke access later.
How to create one
Before you start, you need the bucket or container already created in your cloud provider and the access credentials at hand — see Setting up your delivery channel.
With those values ready, go to Developer > Credentials in the dashboard and follow the steps below:
- Click Create credential.
- Under General data, fill in the credential's Name and, optionally, a Description.
- Under Destination, choose the Delivery channel: AWS S3, Azure Blob Storage, or Google Cloud Storage. The required fields change depending on the channel — see below.
- Under Validation, enter the Container / Bucket name and click Test credential to confirm the data is correct.
- Click Go to review to finish.
The test uploads a file to your bucket. If it fails, it usually means the user or service principal you created is missing write permission — check the permissions listed in your provider's step-by-step guide.
Fields per delivery channel
AWS S3
| Field | Description |
|---|---|
| Access key | Access key for your AWS account |
| Secret key | Secret key associated with the access key |
| Endpoint | S3 service URL, in the format `https://s3.<region>.amazonaws.com` |
| Region | Region where the bucket is hosted, for example `us-east-1` |
Azure Blob Storage
| Field | Description |
|---|---|
| Tenant ID | Microsoft Entra ID tenant identifier |
| Client ID | Identifier of the application registered in Azure |
| Client secret | Secret of the application registered in Azure |
| Connection string | Storage account URL, in the format `https://<StorageAccountName>.blob.core.windows.net`, without the container name |
Google Cloud Storage
| Field | Description |
|---|---|
| Project ID | Google Cloud project identifier |
| Credentials JSON | Service account key, in JSON format |
Not sure where to get these values? The step-by-step for creating the bucket, the access user, and the permissions in each provider is in Setting up your delivery channel.
After creating it
Once the credential is created, it becomes available to select in the Destination step when setting up your BATCH integration.
Technical Support
If you have any questions or technical issues during the process, our technical support team is available. You can reach us by email at [email protected] or via WhatsApp at (11) 91162-6684.