Skip to content

Latest commit

 

History

History
54 lines (28 loc) · 2.93 KB

File metadata and controls

54 lines (28 loc) · 2.93 KB

2.0.1 (2026-06-22)

Bug Fixes

  • tsconfig: restore include/exclude globs (#37) (5fb956b)

2.0.0 (2026-05-15)

  • fix!: use HTTP Basic auth + /v1/saas base for SaaS Protection API (#2) (c052563)

BREAKING CHANGES

  • DattoSaasProtectionConfig.apiKey removed. Callers must now pass both publicKey and secretKey.

Known follow-up: per-customer resource paths in src/resources/*.ts were written against the same speculative spec and may need correction once a live partner key is available for verification (CHANGELOG flags this).

1.0.1 (2026-05-02)

Bug Fixes

1.0.0 (2026-05-01)

Features

  • initial SDK scaffold for Datto SaaS Protection REST API (dfaec84)

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Changed (BREAKING)

  • Auth scheme: Authorization: Bearer <apiKey>Authorization: Basic base64(publicKey:secretKey). The original scaffold used a Bearer token against /api/v1/clients — that's Datto BCDR/PSA's API surface. Datto SaaS Protection's REST API uses HTTP Basic auth with a public/secret key pair issued from the partner portal.
  • Base URL: https://api.{us,eu}.datto.com/api/v1https://api.{us,eu}.datto.com/v1/saas. The SaaS Protection REST API is rooted at /v1/saas; the old prefix returned exception.notfoundhttpexception 404s from Datto's Symfony edge.
  • Config: DattoSaasProtectionConfig.apiKey removed. Callers must now pass both publicKey and secretKey.

Known issues

  • Resource paths (/clients/{id}/domains, /clients/{id}/activity, etc.) were written against the same speculative spec as the auth/base-URL bugs. Only /v1/saas/domains is confirmed against published docs. Per-customer paths may need further correction once we have a live partner key to test against.