About API Keys
- Send Authorization: Bearer <api_key> on /api/v1 requests.
- Only two scopes exist: backups:read and backups:trigger.
- Keep your keys secure and never share them publicly.
Developer API Keys
Manage API tokens for CLI scripts, CI/CD automation, and custom integrations.
Could not load API keys.
Best Practices
- Rotate keys regularly
- Use least privilege permissions
- Store keys securely (no hardcoding)
- Revoke unused keys
API Key Calls (This Month)
Unavailable
- API key calls
- — / Unavailable
- Backup triggers
- — / Unavailable
- Resets in
- —
Call the API
Public Bearer routes only. Keys cannot manage settings, other keys, or another account.
GET /api/v1/backups
List this account's backups. Requires backups:read. No request body.
Optional query: connection_id (owned UUID, else 404),
limit (default 50, max 100), offset (default 0).
curl "https://api.infracherry.com/api/v1/backups?limit=50" \
-H "Authorization: Bearer YOUR_API_KEY"POST /api/v1/backups/trigger
Start a manual backup of one of your connections. Requires backups:trigger.
JSON body has one required field: connection_id (string UUID of a connection you own).
curl -X POST https://api.infracherry.com/api/v1/backups/trigger \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d "{\"connection_id\": \"CONNECTION_UUID\"}"| Name | Key prefix | Permissions | Last Used | Status | Actions |
|---|---|---|---|---|---|
|
No API keys yet. |
|||||
No keys match your current search or filters.
Showing 0 of 0 results
1
Key activity log
View key activity (created, rotated, revoked, renamed)
No activity yet.