What Vectis does with Datto

Syncs BCDR devices and protected agents as customer-linked assets, so every agent shows up on the account hub even before its first backup run.
Tracks backup-run history in the backup_jobs table — last success, last failure, sizes, error messages.
Fans failures into the alerts feed as backup-job-failure alerts, so rules can auto-open PSA tickets or trigger a retry on repeat failures.

What you'll need

Partner API Public Key and Secret Key from the Datto Partner Portal
Region — us or eu, matching the cloud your partner account lives in

1. Mint a Partner API key

Sign in to the Datto Partner Portal (portal.dattobackup.com) as an admin.
Open Admin → Integrations → REST API.
Click Generate new key. Label it “Vectis”. Request the BCDR API scope at minimum — without it, listing devices returns 403.
Copy the public key and secret key Datto displays. The secret is shown only once; if you lose it, revoke and regenerate.

Partner keys authorize against the entire partner tenant, not a single customer. Treat them the same way you’d treat the partner login credentials — rotate promptly if anyone with access leaves, and use a dedicated key per external tool so revocation is surgical.

2. Paste credentials into Vectis

Go to Admin → Integrations and click Configure on Datto BCDR.
Paste the public key, secret key, and pick your region.
Click Test. You’ll see “Connected to Datto (region) — N BCDR devices visible” within a few seconds.
Click Save, then trigger an initial sync.

3. What appears where

Customer hub → Backups section: per-agent summary cards (last success, last failure, currently failing) plus the 10 most recent backup runs.
Alerts feed: backup-job failures land with alert type backup-job-failure, severity high.
Rules engine: the three “Datto backup fails 2+ nights in a row” templates (ConnectWise / Autotask / HaloPSA) are ready to enable — pick the one matching your PSA.

Common errors

401 Unauthorized — Public key / secret key pair is wrong. Rotate from the Partner Portal and re-enter.

403 Forbidden — The key lacks the BCDR API scope. Datto may require a support ticket to add it — it’s not always a self-service toggle.

404 on /v1/bcdr/device — Region is wrong for this partner account. Try the other region; partner accounts don’t span clouds.