Connect DigitalOcean to ShipVitals
Month-to-date cost, invoices per Droplet and app, and App Platform deploys
BetaRead-only key · about 2 minutes
Beta: this connector is new in the beta, and we're still checking it against more accounts.
What it reads
- account:read
- Names the team the token reads
- billing:read
- Reads the month-to-date balance and invoice items
- droplet:read
- Lists Droplets, to put their costs on them
- app:read
- Lists App Platform apps and their deployments
- domain:read
- Lists DNS domains, to match apps to projects
Read-only: ShipVitals can't change anything at DigitalOcean.
What ShipVitals keeps: The access token, encrypted.
How to connect
- In DigitalOcean, open API → Tokens and generate a new personal access token.
- Name it ShipVitals, choose Custom Scopes and tick read for account, billing, droplet, app and domain (or choose Read Only).
- Copy the token. DigitalOcean shows it once.
About 2 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs, Health.
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
DigitalOcean reports a day in full after 1 day; ShipVitals waits for it.
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- DigitalOcean didn't accept the token: it may have expired or been deleted. Generate a new one with read scopes and paste it.
- A permission is missing
- DigitalOcean refused part of the account's data: the token is missing a read scope. Generate it again with account, billing, droplet, app and domain read, or Read Only.
- Access removed
- ShipVitals' access was removed in DigitalOcean. Connect it again; the history it brought in is kept.
- Rate-limited
- DigitalOcean is limiting this token's requests (250 a minute, 5,000 an hour). ShipVitals tries again shortly.
- Quota reached
- The account used up a DigitalOcean quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from DigitalOcean: renamed, moved or removed. Review the connection's resources, or connect again.
- DigitalOcean is unavailable
- DigitalOcean is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach DigitalOcean
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that DigitalOcean is reachable.
- An answer ShipVitals didn't expect
- DigitalOcean answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- A field in the connection doesn't work with DigitalOcean. Check it against How to connect, and test again.