Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "guide" |
| 3 | title: "DigitalOcean authentication" |
| 4 | description: "Current authentication choices for the DigitalOcean toolkit." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-08-17T00:00:00Z" |
| 8 | tags: |
| 9 | - "digital_ocean" |
| 10 | --- |
| 11 | # DigitalOcean authentication |
| 12 | |
| 13 | ## DigitalOcean supports managed OAuth2, custom OAuth2, or a personal access token |
| 14 | |
| 15 | The current `digital_ocean` toolkit supports OAuth2 and API-key authentication. |
| 16 | Use Composio-managed OAuth for the standard connection flow. Use a custom |
| 17 | DigitalOcean OAuth app when the customer needs control over provider settings; |
| 18 | register the exact callback URI shown by the current Composio flow. |
| 19 | |
| 20 | For API-key authentication, provide a DigitalOcean Personal Access Token in the |
| 21 | `bearer_token` connection field. If OAuth fails before consent, compare the |
| 22 | authorization request with the customer-owned app registration and use the API |
| 23 | key path only when it matches the customer's security requirements. |