Authenticate and Manage the Connector
The Build a Doc connector uses API key authentication. This guide covers how to obtain, use, and manage your API keys securely.
Obtaining an API Key
- Sign in to the Build a Doc portal
- Navigate to the API Keys section
- Click Create New Key
- Copy the key immediately (it won’t be shown again)
Using the API Key
First-Time Setup
When adding a Build a Doc action to your flow for the first time:
- You’ll be prompted to create a connection
- Enter a descriptive Connection name. This can be anything you like, but should make the key easily identifiable, e.g.
Build_a_Doc_Production - Copy and paste your API key into the API key field
- Click Create
Existing Connection
If you’ve already created a connection:
- Select it from the connection dropdown
- The API key is stored securely by Power Automate
API Key Security Best Practices
Key Management
| Do | Don’t |
|---|---|
| Use separate keys for different purposes | Share one key across all uses |
| Rotate keys periodically | Keep keys indefinitely |
| Revoke unused keys | Leave old keys active |
| Store keys in secure locations | Store keys in plain text |
Storing Keys in Azure Key Vault
For enhanced security, store API keys in Azure Key Vault:
- Create a secret in Azure Key Vault with your API key
- Use the Key Vault connector in Power Automate to retrieve the key
- Pass the retrieved key to your Build a Doc actions
Key Rotation
To rotate an API key without disruption:
- Create a new API key in the portal
- Update your Power Automate connection with the new key
- Test your flows to confirm they work
- Revoke the old key in the portal
Revoking Keys
If a key is compromised:
- Go to the Build a Doc portal → API Keys
- Find the compromised key
- Click Revoke immediately
- Create a new key and update your connections
Troubleshooting
401 Unauthorised
Causes:
- API key is missing
- API key is incorrect
- API key has been revoked
Resolution:
- Copy and paste the API key again (don’t type manually)
- Verify the key is active in the portal
- Create a new key if necessary
403 Forbidden
Causes:
- API key is valid but subscription lacks permission
- Feature not available on current plan
Resolution:
- Check your subscription plan in the portal
- Upgrade if necessary