Create, Restrict, Rotate & Revoke Wemblo API Keys
Create a named Wemblo API key with minimum scopes, store it securely, rotate it, and revoke it when no longer required.
MAIN FIELDS
| Name | Identifies the consuming system and owner. |
|---|---|
| Scope | Controls permitted resources and actions. |
| Environment | Test or production use. |
| Created Date | Audit information. |
STEPS
- Open Wemblo Developer Settings and API Keys.
- Choose Create API Key.
- Enter a descriptive system and environment name.
- Choose the minimum required scopes.
- Create and copy the key once.
- Store it in a protected environment variable or secret manager.
- Test from an authorized server.
- Record ownership and rotation date.
- Revoke it immediately if exposed or no longer required.
ROTATION SEQUENCE
Create replacement key, update the consuming server, test, revoke the previous key, and review logs for unexpected use.
Who should use it
Authorized developers and technical workspace users.
Where to find it in Wemblo
Wemblo -> Developer Menu -> API Keys
Before you begin
- Use a server-side integration environment.
- Create separate test and production credentials.
- Use HTTPS and least privilege.
- Never expose a key or webhook secret in client-side code.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| API Key | Secret server credential. |
| Scope | Permitted operation. |
| Environment | Test or production. |
| Rotation | Controlled replacement. |
| Revocation | Immediate disablement. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| 401 Unauthorized | Missing, invalid, revoked or wrong-workspace key. |
| 403 Forbidden | Scope or resource permission. |
| 422 Validation | Required field or data format. |
| 429 Rate Limit | Backoff, volume and plan/API capacity. |
| Webhook retries | Endpoint response, signature, timeout and processing speed. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed:

