DigitalOcean

What Plutus imports

• Daily spend by SKU, region, and team (nightly invoice-item estimates)

Connecting

Method: Personal Access Token

1. Sign in to cloud.digitalocean.com and go to API → Tokens.
2. Click Generate New Token, give it a name, and grant it read scope — Billing (billing:read) is the only scope Plutus needs.
3. Copy the token. DigitalOcean only shows it once.
4. In Plutus, paste the token into Personal Access Token.
5. Leave Account URN blank unless you need organization-wide spend across several teams. Plutus auto-detects your team by calling GET /v2/account and building do:team:<your team uuid> — this URN is what the billing endpoint is keyed by, and it’s not the same as the account or user UUID the rest of the DigitalOcean API returns.
6. Only fill in Account URN by hand if you want organization-wide spend: use the form do:teamgroup:<uuid>. This URN doesn’t appear in GET /v2/account, so auto-detection can’t find it for you.
7. Save. Plutus pulls daily usage from the Billing Insights API, walking the requested date range in 31-day slices (the largest window that endpoint accepts per request).

Notes

DigitalOcean’s daily billing figures are nightly invoice-item estimates — DigitalOcean’s own API documentation states they may not add up to the month-end invoice total, since they don’t capture every invoicing factor (taxes, credits, and adjustments are billed separately from product usage). Treat the daily chart as a trend, and your DigitalOcean invoice as the authority on what you were charged.