sendly-python 1.1.0__tar.gz → 1.3.0__tar.gz

{sendly_python-1.1.0 → sendly_python-1.3.0}/.github/workflows/ci.yml

@@ -17,6 +17,7 @@ on:
 jobs:
   test:
     runs-on: ubuntu-latest
+    timeout-minutes: 20
     strategy:
       fail-fast: false
       matrix:

{sendly_python-1.1.0 → sendly_python-1.3.0}/.github/workflows/release.yml

@@ -14,6 +14,7 @@ jobs:
   publish:
     name: Test, build & publish to PyPI
     runs-on: ubuntu-latest
+    timeout-minutes: 20
     environment: pypi # must match the environment on the PyPI trusted publisher
     permissions:
       id-token: write # OIDC for PyPI Trusted Publishing (no token stored)

{sendly_python-1.1.0 → sendly_python-1.3.0}/CHANGELOG.md

@@ -3,6 +3,56 @@
 All notable changes to `sendly-python` are documented here. This project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+## [1.3.0] - 2026-11-07
+
+### Added
+
+- **Why a message bounced or was complained about.** An email (`emails.get`, `emails.list`)
+  gains the keys `bounceType`, `bounceSubType`, `bounceStatusCode`, `bounceDiagnosticCode` and
+  `complaintFeedbackType`; each entry of its delivery history gains the four `bounce*` keys. The
+  `email.bounced` webhook body gains `bounceSubType`, `bounceStatusCode` and
+  `bounceDiagnosticCode`, and `email.complained` gains `complaintFeedbackType`. All are `str | None`
+  and additive: responses are plain dicts, so existing code is unaffected.
+- **Three other optional fields arrive with the re-sync:** `Email.hold`, `Problem.next` and
+  `CreateApiKeyBody.tiers`. All are optional and additive.
+
+### Changed
+
+- **The vendored contract is re-synced** from the released one (`docs.sendly.now/openapi.json`),
+  which had grown from 106 to 198 paths since the last sync. The additions are account, dashboard
+  and member-management routes plus key-callable operations this SDK has no method for yet; the
+  contract suite lists them in `NOT_SDK_CALLABLE` / `NOT_YET_IMPLEMENTED` rather than shipping
+  them unreviewed. No existing method changed.
+
+## [1.2.0] - 2026-11-03
+
+### Added
+
+- **Mailbox mail.** `mailboxes.list_conversations` / `iter_list_conversations`,
+  `get_conversation`, `reply_to_conversation` and `download_attachment`, under
+  the opt-in `mailbox-conversations:read` / `:reply` scopes, which no existing
+  key carries.
+- **The sender logo (BIMI).** `domains.get_logo_v1`, `upload_logo_v1`,
+  `delete_logo_v1` and `get_logo_readiness_v1`.
+- **`client.request_bytes`** for an operation that answers a file. It returns a
+  `SendlyFile(data: bytes, content_type, content_disposition)` and raises the
+  same typed errors. `request` reads the body as text, which mangles a binary file.
+- **`emails.send` takes `listUnsubscribe`**, the https URL of your own one-click
+  unsubscribe endpoint. A transactional send carries no unsubscribe of Sendly's,
+  because Sendly cannot know what the reader would be opting out of; with this
+  field Sendly writes `List-Unsubscribe: <url>` and
+  `List-Unsubscribe-Post: List-Unsubscribe=One-Click` (RFC 8058), so the mail
+  client shows its own unsubscribe button. The two headers stay reserved in
+  `headers`. The server answers `422` for a value that is not https, is over
+  2048 characters, or contains whitespace, a comma or angle brackets. Campaign
+  and workflow sends ignore it and keep Sendly's own link.
+- **The vendored spec is re-synced** from the platform contract. The new mailbox
+  conversation and domain-logo operations are listed as not yet implemented, and
+  the provider compat dialects under `/api/compat/` are excluded by path: those
+  are for the other providers' own SDKs.
+
 ## [1.1.0] - 2026-09-05
 
 Four new resources, the `/api/v1` half of six that only had a legacy one, and a

sendly_python-1.1.0/README.md → sendly_python-1.3.0/PKG-INFO

@@ -1,5 +1,49 @@
+Metadata-Version: 2.4
+Name: sendly-python
+Version: 1.3.0
+Summary: Official Python SDK for Sendly (sendly.now), the email API and platform for developers by Devino Solutions: transactional email, contacts, templates and webhooks.
+Project-URL: Homepage, https://sendly.now
+Project-URL: Documentation, https://docs.sendly.now
+Project-URL: Repository, https://github.com/DevinoSolutions/sendly-python
+Author-email: Devino Solutions <dev@devino.ca>
+License: MIT
+License-File: LICENSE
+Keywords: api,email,email-api,sdk,sendly,sendly.now,transactional-email,webhooks
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Communications :: Email
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: httpx==0.28.1
+Provides-Extra: dev
+Requires-Dist: mypy==1.15.0; extra == 'dev'
+Requires-Dist: pytest==8.3.4; extra == 'dev'
+Requires-Dist: ruff==0.9.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
 # Sendly Python SDK
 
+**Sendly is an email platform for developers: one REST API for transactional email, marketing
+campaigns and visual automation workflows, built on AWS SES, with contacts, segments, templates,
+webhooks and an event stream behind the same account.** It offers a free tier and metered
+pay-as-you-go sending. Sendly is made by Devino Solutions.
+
+What Sendly is not: not a multi-channel messaging suite (email is the only channel; no SMS, push or
+in-app messages), not a marketing suite (no landing pages, forms, ads or CRM), and not related to
+other products or companies that use the word "Sendly". The PyPI package `sendly` is not ours;
+this SDK is published as `sendly-python`.
+
+Canonical site: https://sendly.now · Docs: https://docs.sendly.now · API: https://api.sendly.now
+
 Official Python SDK for the [Sendly](https://sendly.now) REST API —
 transactional email, contacts, lists, topics, events, domains, templates,
 snippets, email verification, address validation, deliverability reporting,
@@ -233,6 +277,13 @@ receipt = sendly.emails.send({"from": "a@you.com", "to": "b@them.com", "subject"
 sendly.emails.send_legacy({"from": "a@you.com", "to": ["b@them.com", "c@them.com"],
                            "subject": "Hi", "body": "<p>Hi</p>"})
 
+# Your own one-click unsubscribe (https only). Sendly writes the RFC 8058
+# List-Unsubscribe headers, so the mail client shows its unsubscribe button; the
+# endpoint gets a cookie-less POST and must unsubscribe the reader on it alone.
+sendly.emails.send({"from": "notify@you.com", "to": "b@them.com", "subject": "New reply",
+                    "body": "<p>Someone replied.</p>",
+                    "listUnsubscribe": "https://you.com/unsubscribe?token=abc123"})
+
 # Batch send (up to 100)
 sendly.emails.batch({"emails": [{"from": "a@you.com", "to": "b@them.com", "subject": "Hi", "body": "<p>Hi</p>"}]})
 
@@ -260,6 +311,26 @@ for event in email["events"]:
 somebody opened, read `openedAt` / `opens` on the rows — engagement is not a
 status.
 
+A bounced or complained message says why. Each key below is `str | None` and is
+`None` until the event happens (or when the receiving server did not say):
+
+```python
+email = sendly.emails.get("em_123")["data"]
+if email["status"] == "BOUNCED":
+    # `bounceType` is "Permanent" or "Undetermined" here (a "Transient" bounce is
+    # retried and never sets BOUNCED); the rest are the receiving server's own words.
+    # Show them to a person, do not parse them.
+    print(email["bounceType"], email["bounceSubType"],
+          email["bounceStatusCode"], email["bounceDiagnosticCode"])
+if email["complainedAt"] is not None:
+    print(email["complaintFeedbackType"])  # e.g. "abuse"
+```
+
+Each entry of `email["events"]` carries the same four `bounce*` keys for the
+transition that recorded them. The `email.bounced` webhook body adds
+`bounceSubType`, `bounceStatusCode` and `bounceDiagnosticCode`, and
+`email.complained` adds `complaintFeedbackType`.
+
 ### Contacts
 
 ```python
@@ -432,6 +503,28 @@ neither is a spelling of the other. `verify_v1` verifies nothing itself:
 verification happens in the domain's DNS when its owner publishes the DKIM
 records SES minted at creation, and this call asks SES what it currently sees.
 
+#### The sender logo (BIMI)
+
+Each identity serves a logo that BIMI-capable inboxes show beside its mail, once
+its DNS is ready:
+
+```python
+logo = sendly.domains.get_logo_v1("d_123")
+print(logo["bimi_record"])  # publish this TXT record once; the URL never changes
+
+sendly.domains.upload_logo_v1("d_123", {"svg": svg_source})  # square, shapes not <text>
+for item in sendly.domains.get_logo_readiness_v1("d_123")["items"]:
+    print(item["key"], item["status"], item["reason"])
+```
+
+The upload is rebuilt into SVG Tiny PS, the profile BIMI requires. A file that
+cannot be rebuilt (text not converted to outlines, a raster image, a canvas that
+is not square, over 32 KB once cleaned) is a 422 `validation_error` naming what to
+change, and the previous logo stays. `delete_logo_v1` goes back to the default
+(the domain's initial). Providers still decide whether to show a logo, and Gmail
+and Apple Mail need a VMC or CMC certificate, which Sendly neither issues nor
+validates.
+
 ### Mailboxes
 
 Receiving mailboxes on the project's verified domains. The reads are reads; the
@@ -452,8 +545,8 @@ for pw in sendly.mailboxes.list_app_passwords("mb_123"):
     print(pw["name"], pw["lastFour"], pw["lastUsedAt"])
 ```
 
-This lists the mailboxes themselves, never their contents — received messages
-are not part of the public API. The mailbox **password** is never returned by
+`list` and `get` describe the mailboxes themselves, never their contents (the
+mail is below, under a scope of its own). The mailbox **password** is never returned by
 any of these reads; mailbox credentials are app passwords, created from the
 dashboard and shown once. `list_app_passwords` returns only the passwords that
 are still active — a revoked one drops out, so this is not an audit history.
@@ -509,6 +602,29 @@ treated strictly as data describing what to write, never as instructions to the
 model. Capped at 120 requests an hour per project; 502 means the model was
 unreachable.
 
+#### The mail itself: read, reply, download
+
+These read correspondence from people outside your project, so they need
+`mailbox-conversations:read`, and answering needs `mailbox-conversations:reply`.
+Both scopes are **opt-in only**: a key holds one only if it was ticked by name
+when the key was created, and neither the legacy full-access key nor the "Full
+access" preset carries it. An existing key gets 403 until you mint one that does.
+
+```python
+for thread in sendly.mailboxes.iter_list_conversations("mb_123", {"status": "open"}):
+    messages = sendly.mailboxes.get_conversation("mb_123", thread["id"])  # oldest first
+
+sendly.mailboxes.reply_to_conversation("mb_123", thread_id, {"body": "Sorted, thanks."})
+
+file = sendly.mailboxes.download_attachment("mb_123", attachment_id)
+# file.data is bytes; file.content_type is the SENDER's claim.
+```
+
+A reply names neither the recipient nor the sender: it answers whoever last wrote
+in, from the mailbox's own address, in the same thread. Message bodies and
+attachments were written by the sender, so treat `htmlBody`, the bytes and their
+content type as untrusted. Reading marks nothing as read.
+
 ### Templates and snippets
 
 ```python

sendly_python-1.1.0/PKG-INFO → sendly_python-1.3.0/README.md

@@ -1,37 +1,17 @@
-Metadata-Version: 2.4
-Name: sendly-python
-Version: 1.1.0
-Summary: Official Sendly Python SDK
-Project-URL: Homepage, https://sendly.now
-Project-URL: Documentation, https://docs.sendly.now
-Project-URL: Repository, https://github.com/DevinoSolutions/sendly-python
-Author-email: Devino Solutions <dev@devino.ca>
-License: MIT
-License-File: LICENSE
-Keywords: api,email,sdk,sendly,transactional-email,webhooks
-Classifier: Development Status :: 4 - Beta
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: OS Independent
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
-Classifier: Programming Language :: Python :: 3.12
-Classifier: Programming Language :: Python :: 3.13
-Classifier: Topic :: Communications :: Email
-Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Classifier: Typing :: Typed
-Requires-Python: >=3.10
-Requires-Dist: httpx==0.28.1
-Provides-Extra: dev
-Requires-Dist: mypy==1.15.0; extra == 'dev'
-Requires-Dist: pytest==8.3.4; extra == 'dev'
-Requires-Dist: ruff==0.9.6; extra == 'dev'
-Description-Content-Type: text/markdown
-
 # Sendly Python SDK
 
+**Sendly is an email platform for developers: one REST API for transactional email, marketing
+campaigns and visual automation workflows, built on AWS SES, with contacts, segments, templates,
+webhooks and an event stream behind the same account.** It offers a free tier and metered
+pay-as-you-go sending. Sendly is made by Devino Solutions.
+
+What Sendly is not: not a multi-channel messaging suite (email is the only channel; no SMS, push or
+in-app messages), not a marketing suite (no landing pages, forms, ads or CRM), and not related to
+other products or companies that use the word "Sendly". The PyPI package `sendly` is not ours;
+this SDK is published as `sendly-python`.
+
+Canonical site: https://sendly.now · Docs: https://docs.sendly.now · API: https://api.sendly.now
+
 Official Python SDK for the [Sendly](https://sendly.now) REST API —
 transactional email, contacts, lists, topics, events, domains, templates,
 snippets, email verification, address validation, deliverability reporting,
@@ -265,6 +245,13 @@ receipt = sendly.emails.send({"from": "a@you.com", "to": "b@them.com", "subject"
 sendly.emails.send_legacy({"from": "a@you.com", "to": ["b@them.com", "c@them.com"],
                            "subject": "Hi", "body": "<p>Hi</p>"})
 
+# Your own one-click unsubscribe (https only). Sendly writes the RFC 8058
+# List-Unsubscribe headers, so the mail client shows its unsubscribe button; the
+# endpoint gets a cookie-less POST and must unsubscribe the reader on it alone.
+sendly.emails.send({"from": "notify@you.com", "to": "b@them.com", "subject": "New reply",
+                    "body": "<p>Someone replied.</p>",
+                    "listUnsubscribe": "https://you.com/unsubscribe?token=abc123"})
+
 # Batch send (up to 100)
 sendly.emails.batch({"emails": [{"from": "a@you.com", "to": "b@them.com", "subject": "Hi", "body": "<p>Hi</p>"}]})
 
@@ -292,6 +279,26 @@ for event in email["events"]:
 somebody opened, read `openedAt` / `opens` on the rows — engagement is not a
 status.
 
+A bounced or complained message says why. Each key below is `str | None` and is
+`None` until the event happens (or when the receiving server did not say):
+
+```python
+email = sendly.emails.get("em_123")["data"]
+if email["status"] == "BOUNCED":
+    # `bounceType` is "Permanent" or "Undetermined" here (a "Transient" bounce is
+    # retried and never sets BOUNCED); the rest are the receiving server's own words.
+    # Show them to a person, do not parse them.
+    print(email["bounceType"], email["bounceSubType"],
+          email["bounceStatusCode"], email["bounceDiagnosticCode"])
+if email["complainedAt"] is not None:
+    print(email["complaintFeedbackType"])  # e.g. "abuse"
+```
+
+Each entry of `email["events"]` carries the same four `bounce*` keys for the
+transition that recorded them. The `email.bounced` webhook body adds
+`bounceSubType`, `bounceStatusCode` and `bounceDiagnosticCode`, and
+`email.complained` adds `complaintFeedbackType`.
+
 ### Contacts
 
 ```python
@@ -464,6 +471,28 @@ neither is a spelling of the other. `verify_v1` verifies nothing itself:
 verification happens in the domain's DNS when its owner publishes the DKIM
 records SES minted at creation, and this call asks SES what it currently sees.
 
+#### The sender logo (BIMI)
+
+Each identity serves a logo that BIMI-capable inboxes show beside its mail, once
+its DNS is ready:
+
+```python
+logo = sendly.domains.get_logo_v1("d_123")
+print(logo["bimi_record"])  # publish this TXT record once; the URL never changes
+
+sendly.domains.upload_logo_v1("d_123", {"svg": svg_source})  # square, shapes not <text>
+for item in sendly.domains.get_logo_readiness_v1("d_123")["items"]:
+    print(item["key"], item["status"], item["reason"])
+```
+
+The upload is rebuilt into SVG Tiny PS, the profile BIMI requires. A file that
+cannot be rebuilt (text not converted to outlines, a raster image, a canvas that
+is not square, over 32 KB once cleaned) is a 422 `validation_error` naming what to
+change, and the previous logo stays. `delete_logo_v1` goes back to the default
+(the domain's initial). Providers still decide whether to show a logo, and Gmail
+and Apple Mail need a VMC or CMC certificate, which Sendly neither issues nor
+validates.
+
 ### Mailboxes
 
 Receiving mailboxes on the project's verified domains. The reads are reads; the
@@ -484,8 +513,8 @@ for pw in sendly.mailboxes.list_app_passwords("mb_123"):
     print(pw["name"], pw["lastFour"], pw["lastUsedAt"])
 ```
 
-This lists the mailboxes themselves, never their contents — received messages
-are not part of the public API. The mailbox **password** is never returned by
+`list` and `get` describe the mailboxes themselves, never their contents (the
+mail is below, under a scope of its own). The mailbox **password** is never returned by
 any of these reads; mailbox credentials are app passwords, created from the
 dashboard and shown once. `list_app_passwords` returns only the passwords that
 are still active — a revoked one drops out, so this is not an audit history.
@@ -541,6 +570,29 @@ treated strictly as data describing what to write, never as instructions to the
 model. Capped at 120 requests an hour per project; 502 means the model was
 unreachable.
 
+#### The mail itself: read, reply, download
+
+These read correspondence from people outside your project, so they need
+`mailbox-conversations:read`, and answering needs `mailbox-conversations:reply`.
+Both scopes are **opt-in only**: a key holds one only if it was ticked by name
+when the key was created, and neither the legacy full-access key nor the "Full
+access" preset carries it. An existing key gets 403 until you mint one that does.
+
+```python
+for thread in sendly.mailboxes.iter_list_conversations("mb_123", {"status": "open"}):
+    messages = sendly.mailboxes.get_conversation("mb_123", thread["id"])  # oldest first
+
+sendly.mailboxes.reply_to_conversation("mb_123", thread_id, {"body": "Sorted, thanks."})
+
+file = sendly.mailboxes.download_attachment("mb_123", attachment_id)
+# file.data is bytes; file.content_type is the SENDER's claim.
+```
+
+A reply names neither the recipient nor the sender: it answers whoever last wrote
+in, from the mailbox's own address, in the same thread. Message bodies and
+attachments were written by the sender, so treat `htmlBody`, the bytes and their
+content type as untrusted. Reading marks nothing as read.
+
 ### Templates and snippets
 
 ```python

{sendly_python-1.1.0 → sendly_python-1.3.0}/pyproject.toml

@@ -8,13 +8,13 @@ build-backend = "hatchling.build"
 # the PyPI trusted-publisher configuration). The import package is
 # unchanged (`import sendly`) — see [tool.hatch.build.targets.wheel] below.
 name = "sendly-python"
-version = "1.1.0"
-description = "Official Sendly Python SDK"
+version = "1.3.0"
+description = "Official Python SDK for Sendly (sendly.now), the email API and platform for developers by Devino Solutions: transactional email, contacts, templates and webhooks."
 readme = "README.md"
 requires-python = ">=3.10"
 license = { text = "MIT" }
 authors = [{ name = "Devino Solutions", email = "dev@devino.ca" }]
-keywords = ["sendly", "email", "api", "sdk", "transactional-email", "webhooks"]
+keywords = ["sendly", "sendly.now", "email", "email-api", "api", "sdk", "transactional-email", "webhooks"]
 dependencies = ["httpx==0.28.1"]
 classifiers = [
     "Development Status :: 4 - Beta",

{sendly_python-1.1.0 → sendly_python-1.3.0}/src/sendly/__init__.py

@@ -50,6 +50,7 @@ from sendly.resources.validation import ValidationResource
 from sendly.resources.verify import VerifyResource
 from sendly.resources.webhooks import WebhooksResource
 from sendly.resources.workflows import WorkflowsResource
+from sendly.types import SendlyFile
 from sendly.webhook_utils import DEFAULT_TOLERANCE_MS, construct_event, verify_signature
 
 __version__ = SDK_VERSION
@@ -74,6 +75,7 @@ __all__ = [
     "SendlyConflictError",
     "SendlyConnectionError",
     "SendlyError",
+    "SendlyFile",
     "SendlyNotFoundError",
     "SendlyPermissionError",
     "SendlyRateLimitError",

{sendly_python-1.1.0 → sendly_python-1.3.0}/src/sendly/client.py

@@ -53,6 +53,7 @@ from sendly.resources.validation import ValidationResource
 from sendly.resources.verify import VerifyResource
 from sendly.resources.webhooks import WebhooksResource
 from sendly.resources.workflows import WorkflowsResource
+from sendly.types import SendlyFile
 
 if TYPE_CHECKING:
     from collections.abc import Mapping
@@ -63,7 +64,7 @@ if TYPE_CHECKING:
 __all__ = ["DEFAULT_BASE_URL", "SDK_VERSION", "Sendly"]
 
 #: Package version. Kept in sync with ``pyproject.toml``.
-SDK_VERSION = "1.1.0"
+SDK_VERSION = "1.3.0"
 
 #: Default production API base. Override via ``base_url`` for staging/self-hosted.
 DEFAULT_BASE_URL = "https://api.sendly.now"
@@ -174,30 +175,7 @@ class Sendly:
         success body, or ``None`` for 204 / ``no_content``. Errors are raised as
         :class:`SendlyError` subclasses based on status.
         """
-        url = self._build_url(path, query)
-        request_headers: dict[str, str] = {
-            "Authorization": f"Bearer {self._api_key}",
-            "Accept": "application/json",
-            "User-Agent": USER_AGENT,
-            **self._default_headers,
-            **(dict(headers) if headers else {}),
-        }
-
-        content: str | None = None
-        if body is not None:
-            request_headers["Content-Type"] = "application/json"
-            content = json.dumps(body)
-
-        try:
-            response = self._client.request(
-                method,
-                url,
-                content=content,
-                headers=request_headers,
-                timeout=self._timeout,
-            )
-        except httpx.HTTPError as exc:
-            raise SendlyConnectionError(f"Sendly request failed: {exc}", exc) from exc
+        response = self._send(method=method, path=path, body=body, query=query, headers=headers)
 
         # 204 No Content or caller-forced no-content (DELETE endpoints, which
         # now respond 200 with an id body the SDK intentionally discards).
@@ -229,6 +207,67 @@ class Sendly:
 
         return parsed
 
+    def request_bytes(
+        self,
+        *,
+        method: str,
+        path: str,
+        query: Query | None = None,
+        headers: Mapping[str, str] | None = None,
+    ) -> SendlyFile:
+        """Like :meth:`request`, for an operation whose success body is a file.
+
+        Returns the raw bytes with the response's own ``Content-Type`` and
+        ``Content-Disposition``. A failure is still a JSON error document and is
+        raised as the same :class:`SendlyError` subclasses. Reading the body as
+        text, as :meth:`request` does, would mangle any file that is not UTF-8.
+        """
+        response = self._send(
+            method=method, path=path, query=query, headers={"Accept": "*/*", **(headers or {})}
+        )
+        if not response.is_success:
+            self._raise_for_error(response)
+        return SendlyFile(
+            data=response.content,
+            content_type=response.headers.get("content-type"),
+            content_disposition=response.headers.get("content-disposition"),
+        )
+
+    def _send(
+        self,
+        *,
+        method: str,
+        path: str,
+        body: Body | None = None,
+        query: Query | None = None,
+        headers: Mapping[str, str] | None = None,
+    ) -> httpx.Response:
+        """Issue the request; errors and parsing are the caller's."""
+        url = self._build_url(path, query)
+        request_headers: dict[str, str] = {
+            "Authorization": f"Bearer {self._api_key}",
+            "Accept": "application/json",
+            "User-Agent": USER_AGENT,
+            **self._default_headers,
+            **(dict(headers) if headers else {}),
+        }
+
+        content: str | None = None
+        if body is not None:
+            request_headers["Content-Type"] = "application/json"
+            content = json.dumps(body)
+
+        try:
+            return self._client.request(
+                method,
+                url,
+                content=content,
+                headers=request_headers,
+                timeout=self._timeout,
+            )
+        except httpx.HTTPError as exc:
+            raise SendlyConnectionError(f"Sendly request failed: {exc}", exc) from exc
+
     def unwrap(self, envelope: Any) -> Any:
         """Return the ``data`` field of a ``{success, data}`` envelope, else the
         value unchanged. Centralizing this keeps resource code clean.

{sendly_python-1.1.0 → sendly_python-1.3.0}/src/sendly/resources/domains.py

@@ -16,6 +16,8 @@ if TYPE_CHECKING:
         DomainDeletedV1,
         DomainListResponse,
         DomainListV1,
+        DomainLogoReadinessV1,
+        DomainLogoV1,
         DomainRecord,
         DomainSetupSession,
         DomainV1,
@@ -208,3 +210,59 @@ class DomainsResource:
             method="DELETE", path=f"/api/v1/domains/{encode_path_segment(id)}"
         )
         return response
+
+    def get_logo_v1(self, id: str) -> DomainLogoV1:
+        """The logo this identity serves to inboxes (BIMI), the
+        ``default._bimi`` TXT record that makes them fetch it (``bimi_record``),
+        and a fresh DNS reading of whether they will show it today.
+
+        The URL never changes, so the record is published once. Until a logo is
+        uploaded it serves a default (the domain's initial), and it serves
+        nothing until the identity verifies. Providers decide whether to show a
+        logo; Gmail also needs a VMC or CMC certificate, which Sendly neither
+        issues nor checks. :meth:`get_logo_readiness_v1` is the full checklist.
+        """
+        response: DomainLogoV1 = self._client.request(
+            method="GET", path=f"/api/v1/domains/{encode_path_segment(id)}/logo"
+        )
+        return response
+
+    def upload_logo_v1(self, id: str, body: Body) -> DomainLogoV1:
+        """Replace the logo with an SVG: ``{"svg": "<svg ...>"}``.
+
+        It is rebuilt into SVG Tiny PS, the profile BIMI requires: square, shapes
+        rather than ``<text>``, nothing referenced outside itself, at most 32 KB
+        once rebuilt. A file that cannot be rebuilt answers 422
+        ``validation_error`` with a ``detail`` naming what to change, and the
+        previous logo stays in place.
+        """
+        response: DomainLogoV1 = self._client.request(
+            method="PUT", path=f"/api/v1/domains/{encode_path_segment(id)}/logo", body=body
+        )
+        return response
+
+    def delete_logo_v1(self, id: str) -> DomainLogoV1:
+        """Remove the uploaded logo, so the URL serves the default again.
+
+        Returns the logo now served; removing one that was never uploaded is not
+        an error. The DNS record does not change.
+        """
+        response: DomainLogoV1 = self._client.request(
+            method="DELETE", path=f"/api/v1/domains/{encode_path_segment(id)}/logo"
+        )
+        return response
+
+    def get_logo_readiness_v1(self, id: str) -> DomainLogoReadinessV1:
+        """How ready the identity is to show its logo as the inbox avatar.
+
+        Each step (DMARC at enforcement on the host and its organizational
+        domain, the BIMI record, the logo file, the mark certificate) comes back
+        ``met``, ``missing``, ``unknown`` or ``not_applicable`` with a
+        plain-English ``reason``, plus one checklist per inbox (Gmail, Yahoo,
+        Apple Mail, Fastmail). For the certificate only "the URL answers with a
+        PEM file" is checked; its chain is not validated.
+        """
+        response: DomainLogoReadinessV1 = self._client.request(
+            method="GET", path=f"/api/v1/domains/{encode_path_segment(id)}/logo/readiness"
+        )
+        return response