agentmail 0.1.13 → 0.1.15

package/dist/llms-full.txt

@@ -5,7 +5,7 @@
 <Tip title="Welcome to AgentMail!" icon="fa-solid fa-star" />
 
 <Frame caption="We're excited to have you onboard!">
-  <img src="file:310e2395-5411-4afa-b39b-892397ecb1ca" alt="We're excited to have you onboard!" />
+  <img src="file:e53d2b86-fc27-4718-9b51-14cf6ad0cf40" alt="We're excited to have you onboard!" />
 </Frame>
 
 AgentMail is an API platform for giving AI agents their own inboxes to send, receive, and act upon emails. This allows agents to assume their own identity and communicate via the universal protocol of email with services, people, and other agents.
@@ -171,7 +171,7 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
   <Step title="Create an API Key">
     Now that you're in the console, you'll need to create an API key to
     authenticate your requests. Navigate to the API Keys section in your console
-    dashboard. ![API Key Creation Screenshot](file:96bda405-2981-443a-a64d-e1a2835c9fb0) Click
+    dashboard. ![API Key Creation Screenshot](file:da49aed8-52d2-4bb8-9fca-f018e82fe721) Click
     "Create New API Key" and give it a descriptive name. Once created, copy the
     API key and store it securely. Create a `.env` file in your project's root
     directory and add your key to it. We recommend using environment variables to
@@ -322,7 +322,7 @@ Unlike traditional email providers that are designed for human scale, AgentMail
 
 As the diagram below illustrates, your `organization` is the top-level container that holds all your resources. You can provision many `Inboxes` within your `organization`, each with its own `Threads`, `Messages`, and `Attachments`, allowing you to manage a large fleet of agents seamlessly.
 
-<img src="file:b0c8b4e6-563d-4ff5-b08c-d9dde55452da" alt="AgentMail Organizational Hierarchy" />
+<img src="file:ca8f8d7a-74d3-4f45-8b91-767788e96af6" alt="AgentMail Organizational Hierarchy" />
 
 <Steps>
   <Step title="Organization">
@@ -742,7 +742,7 @@ Here is an example of a well-structured and styled HTML header:
 </CodeBlocks>
 
 <Frame caption="Look how pretty this message looks!">
-  <img src="file:1e8d927e-c68d-49f1-8278-166497a45a69" alt="rendered css" />
+  <img src="file:149f72bc-a78d-4519-95c1-fa25a108d242" alt="rendered css" />
 </Frame>
 
 ## Receiving `Messages`
@@ -1981,10 +1981,29 @@ Configuring your domain is a three-step process: add the domain via API, copy th
     After creating your domain in the AgentMail Console, click the "Download BIND Zone File" button to get the complete zone file.
 
     <Frame caption="Downloading BIND zone file from AgentMail Console">
-      <img src="file:d9e83f6a-1341-4b14-b758-7e3508a231d4" alt="Download BIND Zone File from Console" />
+      <img src="file:b2476421-c898-403a-8fb9-1c285f2475ba" alt="Download BIND Zone File from Console" />
     </Frame>
 
     <Tabs>
+      <Tab title="Cloudflare">
+        **Step 2: Import to Cloudflare**
+
+        1. Go to your Cloudflare dashboard and select your domain
+        2. Navigate to **DNS > Records**
+
+        <Frame caption="This is what the page looks like">
+          <img src="file:1fb7b8c5-abf2-40f4-8580-8b50008be7b5" alt="Cloudflare BIND Import" />
+        </Frame>
+
+        3. Click **"Import and Export"**
+
+        <Frame caption="You should be able to just drop the file in">
+          <img src="file:f1d72f77-daad-4cab-af9d-7ed652ff7d03" alt="Cloudflare BIND Import" />
+        </Frame>
+
+        4. Upload the downloaded BIND zone file as is
+      </Tab>
+
       <Tab title="AWS Route 53">
         **Step 2: Import to Route 53**
 
@@ -1992,35 +2011,32 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Click **"Import zone file"** in the top right corner
 
         <Frame caption="Importing BIND zone file in AWS Route 53">
-          <img src="file:328d8c68-88cf-42ea-bce3-5630206b406d" alt="AWS Route 53 BIND Import" />
+          <img src="file:1902dcea-b3a3-4d84-a2ae-c368b1e7f573" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         3. Paste the CONTENTS of downloaded BIND zone file
 
         <Frame caption="Open the file with text editor and paste the contents. It should look similar to what we have in this image.">
-          <img src="file:35f3a2a1-77a9-4a1f-932d-1e580a86eae2" alt="AWS Route 53 BIND Import" />
+          <img src="file:253c47aa-4c82-4d30-8dd6-21f74cb60b8d" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         4. Review the records and click **"Import"**
-      </Tab>
 
-      <Tab title="Cloudflare">
-        **Step 2: Import to Cloudflare**
+        <Warning title="CRITICAL: Route 53 TXT Record 255 Character Limit">
+          **AWS Route 53 has a 255 character maximum per string.** It will get angry at the DKIM record since it is longer than 255 chars (we use more secure encryption key so we get better deliverability with Gmail!)
 
-        1. Go to your Cloudflare dashboard and select your domain
-        2. Navigate to **DNS > Records**
+          **When entering TXT values in the Route 53 UI, you MUST do the following.**
 
-        <Frame caption="This is what the page looks like">
-          <img src="file:0caf7073-c006-46c3-aa5b-67ea84d2cf76" alt="Cloudflare BIND Import" />
-        </Frame>
+          1. Split the value into two quoted strings.
+             a. e.g.: "abcd" -> "ab""cd"
+          2. Ensure there is NO SPACE between the quoted strings. This will make or break validation.
 
-        3. Click **"Import and Export"**
+          **Correct:** `"first-part-of-value""second-part-of-value"`
 
-        <Frame caption="You should be able to just drop the file in">
-          <img src="file:6ed60e97-c0e8-448d-a7e7-220170cdda24" alt="Cloudflare BIND Import" />
-        </Frame>
+          **Wrong:** `"first-part-of-value" "second-part-of-value"` (space between strings)
 
-        4. Upload the downloaded BIND zone file as is
+          If you accidentally include a space or click enter, Route 53 will create **two separate TXT records** instead of one concatenated record. This will cause email authentication to fail, and providers like **Gmail will reject your emails**.
+        </Warning>
       </Tab>
 
       <Tab title="Porkbun">
@@ -2030,13 +2046,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Navigate to the **DNS** subtab of the domain you want to send from
 
         <Frame caption="Click on this button!">
-          <img src="file:9fe338be-7731-4fb0-b136-c2b6fa86a7de" alt="Porkbun DNS Management" />
+          <img src="file:7a037d10-18ee-46d3-82bf-ffd2ce684655" alt="Porkbun DNS Management" />
         </Frame>
 
         3. Scroll down to the quick upload section
 
         <Frame caption="Upload your BIND zone file here">
-          <img src="file:db814e7e-4737-488a-bccc-2d581772369b" alt="Porkbun Zone File Import" />
+          <img src="file:f1a1b25e-e3c4-41ef-afce-e16d23a491e5" alt="Porkbun Zone File Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -2054,7 +2070,7 @@ Configuring your domain is a three-step process: add the domain via API, copy th
     </Tabs>
 
     <Callout type="info" title="BIND Zone File Format">
-      Check that all records (CNAME, TXT, MX) have been correctly imported in the
+      Check that all records (TXT, MX) have been correctly imported in the
       console(the console will show in real time if we can find the records,
       typically within seconds).
     </Callout>
@@ -2068,38 +2084,46 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         If you created your domain through the [AgentMail Console](https://console.agentmail.to), the DNS records are displayed in a simplified format that's ready for copy-paste into your DNS provider.
 
         <Tabs>
+          <Tab title="Cloudflare">
+            In the dashboard (**DNS > Records**), click **"Add record"**.
+
+            * **TXT (DMARC/SPF/DKIM):**
+              * **Name:** Copy the **Name** value directly from the console.
+              * **Content:** Copy the **Value** from the console.
+
+            * **MX:**
+              * **Name:** Enter `@` to apply the record to the root domain.
+              * **Mail server:** Copy the **Value** from the console.
+              * **Priority:** Use the priority shown in the console.
+          </Tab>
+
           <Tab title="AWS Route 53">
             In your hosted zone, click **"Create record"**.
 
-            * **CNAME (DKIM):**
-              * **Record name:** Copy the **Name** value directly from the console (e.g., `abc123._domainkey`).
-              * **Value:** Copy the **Value** from the console (e.g., `abc123.dkim.amazonses.com`).
-
             * **TXT (DMARC/SPF):**
-              * **Record name:** Copy the **Name** value directly from the console (e.g., `_dmarc` or `mail`).
+              * **Record name:** Copy the **Name** value directly from the console (e.g., `_dmarc` or `mail` or `agentmail._domainkey`).
               * **Value:** Copy the **Value** from the console, ensuring it is enclosed in quotes.
 
-            * **MX:**
-              * **Record name:** Enter the value exactly as we return it, whether its `@` or the subdomain.
-              * **Value:** Copy the **Value** from the console (e.g., `inbound-smtp.us-east-1.amazonaws.com`).
-              * **Priority:** Use the priority shown in the console (typically `10`).
-          </Tab>
+            <Warning title="CRITICAL: Route 53 TXT Record 255 Character Limit">
+              **AWS Route 53 has a 255 character maximum per string.** It will get angry at the DKIM record since it is longer than 255 chars (we use more secure encryption key so we get better deliverability with Gmail!)
 
-          <Tab title="Cloudflare">
-            In the dashboard (**DNS > Records**), click **"Add record"**.
+              **When entering TXT values in the Route 53 UI, you MUST do the following.**
 
-            * **CNAME (DKIM):**
-              * **Name:** Copy the **Name** value directly from the console.
-              * **Target:** Copy the **Value** from the console.
+              1. Split the value into two quoted strings.
+                 a. e.g.: "abcd" -> "ab""cd"
+              2. Ensure there is NO SPACE between the quoted strings. This will make or break validation.
 
-            * **TXT (DMARC/SPF):**
-              * **Name:** Copy the **Name** value directly from the console.
-              * **Content:** Copy the **Value** from the console.
+              **Correct:** `"first-part-of-value""second-part-of-value"`
+
+              **Wrong:** `"first-part-of-value" "second-part-of-value"` (space between strings)
+
+              If you accidentally include a space or click enter, Route 53 will create **two separate TXT records** instead of one concatenated record. This will cause email authentication to fail, and providers like **Gmail will reject your emails**.
+            </Warning>
 
             * **MX:**
-              * **Name:** Enter `@` to apply the record to the root domain.
-              * **Mail server:** Copy the **Value** from the console.
-              * **Priority:** Use the priority shown in the console.
+              * **Record name:** Enter the value exactly as we return it, whether its `@` or the subdomain.
+              * **Value:** Copy the **Value** from the console (e.g., `inbound-smtp.us-east-1.amazonaws.com`).
+              * **Priority:** Use the priority shown in the console (typically `10`).
           </Tab>
         </Tabs>
 
@@ -2112,41 +2136,45 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         If you're using the API directly, the DNS records are returned as fully qualified domain names (FQDNs) that require some manual parsing.
 
         <Tabs>
+          <Tab title="Cloudflare">
+            In the dashboard (**DNS > Records**), click **"Add record"**.
+
+            * **TXT (DMARC/SPF/DKIM):**
+              * **Name:** Enter the part of the `name` before your root domain (e.g. `_dmarc`).
+              * **Content:** Copy paste the `value` from the API response.
+
+            * **MX:**
+              * **Name:** Enter the part of the name before your root domain
+              * **Mail server:** Enter the `value` from the API.
+              * **Priority:** Enter the `priority` from the API.
+          </Tab>
+
           <Tab title="AWS Route 53">
             In your hosted zone, click **"Create record"**.
 
-            * **CNAME (DKIM):**
-              * **Record name:** Enter the part of the `name` before your root domain (e.g., `{random_letters_numbers}._domainkey` for a `name` of `{random_letters_numbers}._domainkey.domain.com`).
-              * **Value:** Can directly copy paste the `value` from the API response (e.g., `{random_letters_numbers}.dkim.amazonses.com`).
+            * **TXT (DMARC/SPF/DKIM):**
+              * **Record name:** Enter the part of the `name` before your root domain (e.g., `_dmarc` for a `name` of `_dmarc.domain.com`, or `mail` for a `name` of `mail.domain.com`, or `agentmail._domainkey` for a `name` of agentmail.\_domainkey.agents.com).
+              * **Value:** Can copy paste the`value` from the API, ensuring it is enclosed in quotes.
 
-            <Frame caption="Example of adding a CNAME record in Route 53. Notice that AWS already appends the root domain (agentmail.cc) to the end of the name value!">
-              <img src="file:97040bb3-e526-420e-b804-9043ccec9a68" alt="AWS Route 53 Record Configuration" />
-            </Frame>
+            <Warning title="CRITICAL: Route 53 TXT Record 255 Character Limit">
+              **AWS Route 53 has a 255 character maximum per string.** It will get angry at the DKIM record since it is longer than 255 chars (we use more secure encryption key so we get better deliverability with Gmail!)
 
-            * **TXT (DMARC/SPF):**
-              * **Record name:** Enter the part of the `name` before your root domain (e.g., `_dmarc` for a `name` of `_dmarc.domain.com`, or `mail` for a `name` of `mail.domain.com`).
-              * **Value:** Can copy paste the`value` from the API, ensuring it is enclosed in quotes.
+              **When entering TXT values in the Route 53 UI, you MUST do the following.**
 
-            * **MX:**
-              * **Record name:** Leave this field blank to apply the record to the root domain.
-              * **Value:** This is critical. You must combine the `priority` and `value` from the API into a single string, separated by a space. For example: `10 inbound-smtp.us-east-1.amazonaws.com`.
-          </Tab>
+              1. Split the value into two quoted strings.
+                 a. e.g.: "abcd" -> "ab""cd"
+              2. Ensure there is NO SPACE between the quoted strings. This will make or break validation.
 
-          <Tab title="Cloudflare">
-            In the dashboard (**DNS > Records**), click **"Add record"**.
+              **Correct:** `"first-part-of-value""second-part-of-value"`
 
-            * **CNAME (DKIM):**
-              * **Name:** Enter the part of the `name` before your root domain (e.g., `{random_letters_numbers}._domainkey`).
-              * **Target:** Copy paste the `value` from the API response.
+              **Wrong:** `"first-part-of-value" "second-part-of-value"` (space between strings)
 
-            * **TXT (DMARC/SPF):**
-              * **Name:** Enter the part of the `name` before your root domain (e.g. `_dmarc`).
-              * **Content:** Copy paste the `value` from the API response.
+              If you accidentally include a space or click enter, Route 53 will create **two separate TXT records** instead of one concatenated record. This will cause email authentication to fail, and providers like **Gmail will reject your emails**.
+            </Warning>
 
             * **MX:**
-              * **Name:** Enter the part of the name before your root domain
-              * **Mail server:** Enter the `value` from the API.
-              * **Priority:** Enter the `priority` from the API.
+              * **Record name:** Leave this field blank to apply the record to the root domain.
+              * **Value:** This is critical. You must combine the `priority` and `value` from the API into a single string, separated by a space. For example: `10 inbound-smtp.us-east-1.amazonaws.com`.
           </Tab>
         </Tabs>
       </Tab>
@@ -2176,15 +2204,15 @@ Configuring your domain is a three-step process: add the domain via API, copy th
 
 Here are instructions for some common DNS providers. This list is not exhaustive, so please consult your provider's documentation if you don't see it here.
 
-| DNS/Hosting Provider | Documentation Link                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| :------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **GoDaddy**          | [CNAME: Add a CNAME record](https://www.godaddy.com/help/add-a-cname-record-19236) <br /> [MX: Add an MX record](https://www.godaddy.com/help/add-an-mx-record-19234) <br /> [TXT: Add a TXT record](https://www.godaddy.com/help/add-a-txt-record-19232)                                                                                                                                                                                                                                                                                                   |
-| **DreamHost**        | [CNAME/MX/TXT: How do I add custom DNS records?](https://help.dreamhost.com/hc/en-us/articles/215414867-How-do-I-add-custom-DNS-records)                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| **Cloudflare**       | [MX: How do I add or edit mail or MX records?](https://support.cloudflare.com/hc/en-us/articles/200168806-Managing-DNS-records-in-Cloudflare) <br /> [TXT: Managing DNS records in Cloudflare](https://support.cloudflare.com/hc/en-us/articles/200168806-Managing-DNS-records-in-Cloudflare)                                                                                                                                                                                                                                                               |
-| **HostGator**        | [CNAME/MX/TXT: Manage DNS Records with HostGator/eNom](https://www.hostgator.com/help/article/manage-dns-records-with-hostgator-enom)                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| **Namecheap**        | [CNAME: How to create a CNAME record](https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-to-create-a-cname-record-for-your-domain/) <br /> [MX: How can I set up MX records required for mail service?](https://www.namecheap.com/support/knowledgebase/article.aspx/434/2237/how-can-i-set-up-mx-records-required-for-mail-service) <br /> [TXT: How do I add TXT/SPF/DKIM/DMARC records for my domain?](https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add-txtspfdkimdmarc-records-for-my-domain) |
-| **Names.co.uk**      | [CNAME/MX/TXT: Changing your domain's DNS settings](https://www.names.co.uk/support/articles/changing-your-domains-dns-settings/)                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| **Wix**              | [CNAME: Adding or Updating CNAME Records](https://support.wix.com/en/article/adding-or-updating-cname-records-in-your-wix-account) <br /> [MX: Adding or Updating MX Records in Your Wix Account](https://support.wix.com/en/article/adding-or-updating-mx-records-in-your-wix-account) <br /> [TXT: Adding or Updating TXT Records in Your Wix Account](https://support.wix.com/en/article/adding-or-updating-txt-records-in-your-wix-account)                                                                                                             |
+| DNS/Hosting Provider | Documentation Link                                                                                                                                                                                                                                                                                                                                                                       |
+| :------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **GoDaddy**          | [MX: Add an MX record](https://www.godaddy.com/help/add-an-mx-record-19234) <br /> [TXT: Add a TXT record](https://www.godaddy.com/help/add-a-txt-record-19232)                                                                                                                                                                                                                          |
+| **DreamHost**        | [How do I add custom DNS records?](https://help.dreamhost.com/hc/en-us/articles/215414867-How-do-I-add-custom-DNS-records)                                                                                                                                                                                                                                                               |
+| **Cloudflare**       | [MX: How do I add or edit mail or MX records?](https://support.cloudflare.com/hc/en-us/articles/200168806-Managing-DNS-records-in-Cloudflare) <br /> [TXT: Managing DNS records in Cloudflare](https://support.cloudflare.com/hc/en-us/articles/200168806-Managing-DNS-records-in-Cloudflare)                                                                                            |
+| **HostGator**        | [Manage DNS Records with HostGator/eNom](https://www.hostgator.com/help/article/manage-dns-records-with-hostgator-enom)                                                                                                                                                                                                                                                                  |
+| **Namecheap**        | [MX: How can I set up MX records required for mail service?](https://www.namecheap.com/support/knowledgebase/article.aspx/434/2237/how-can-i-set-up-mx-records-required-for-mail-service) <br /> [TXT: How do I add TXT/SPF/DKIM/DMARC records for my domain?](https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add-txtspfdkimdmarc-records-for-my-domain) |
+| **Names.co.uk**      | [Changing your domain's DNS settings](https://www.names.co.uk/support/articles/changing-your-domains-dns-settings/)                                                                                                                                                                                                                                                                      |
+| **Wix**              | [MX: Adding or Updating MX Records in Your Wix Account](https://support.wix.com/en/article/adding-or-updating-mx-records-in-your-wix-account) <br /> [TXT: Adding or Updating TXT Records in Your Wix Account](https://support.wix.com/en/article/adding-or-updating-txt-records-in-your-wix-account)                                                                                    |
 
 <Callout type="success" title="Ready to Go!" icon="fa-solid fa-rocket">
   Once your domain status is `ready`, you can start creating `Inboxes` with your
@@ -2842,13 +2870,13 @@ Ngrok creates a secure tunnel from a public URL to your local development server
 
 Visit [ngrok.com](https://ngrok.com/) and click "Sign up" to create a free account.
 
-<img src="file:cacdfa4e-696b-4485-8833-67280879d17d" alt="Ngrok homepage" />
+<img src="file:6fac6217-a180-4bb3-8d3b-d7d7bda85343" alt="Ngrok homepage" />
 
 ### 1.2 Choose your platform and install
 
 After logging in, ngrok will guide you through the setup process. Select your operating system and follow the installation instructions.
 
-<img src="file:def52365-4003-4d3f-9b50-b9abb02ecd4b" alt="Ngrok setup instructions" />
+<img src="file:dcf53b09-c6e2-494c-afdb-4be04830d89b" alt="Ngrok setup instructions" />
 
 For macOS, you can install ngrok via Homebrew:
 
@@ -2894,7 +2922,7 @@ ngrok http 3000
 
 You should see output similar to this:
 
-<img src="file:2894d030-381a-4542-96a8-38db296ce8d5" alt="Ngrok terminal output" />
+<img src="file:8b6e039d-c311-41d5-99c4-054c326bd107" alt="Ngrok terminal output" />
 
 Copy the **Forwarding URL** (e.g., `https://your-subdomain.ngrok-free.app`). This is the public URL that AgentMail will use to send webhooks.
 
@@ -2991,7 +3019,7 @@ python webhook_receiver.py
 
 Open your browser and visit `http://127.0.0.1:3000` to see the status page confirming your webhook receiver is running:
 
-<img src="file:3615403f-ba34-4b46-8b25-c654950bca80" alt="Webhook receiver status page" />
+<img src="file:01ea6d2c-542b-44a1-b485-1fdc62145b1e" alt="Webhook receiver status page" />
 
 ## Testing Your Setup
 
@@ -3488,7 +3516,7 @@ How you send your emails is just as important as what you send. If you're sendin
     more natural to email providers. AgentMail's ability to create inboxes at
     scale makes this strategy easy to implement.
 
-    <img src="file:3af96ac6-1192-4d7c-9c5c-faefe4c6dc84" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
+    <img src="file:c8e83af7-6444-48c7-be8b-8b8531b5bb9d" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
   </Step>
 
   <Step title="Protect Your Reputation with Multiple Domains">
@@ -5507,7 +5535,7 @@ Done
 
 Go to your AgentMail inbox and filter by labels to organize your emails:
 
-<img src="file:d68eacab-1cee-4bd4-96b5-0e2a1aed4774" alt="Test image" />
+<img src="file:80803caa-05f7-4aea-8dd0-1d65380cd6ba" alt="Test image" />
 
 **Filter by sentiment:**
 
@@ -7630,6 +7658,11 @@ paths:
           required: false
           schema:
             $ref: '#/components/schemas/type_:Ascending'
+        - name: include_spam
+          in: query
+          required: false
+          schema:
+            $ref: '#/components/schemas/type_:IncludeSpam'
         - name: Authorization
           in: header
           description: >-
@@ -7668,6 +7701,8 @@ components:
       format: date-time
     type_:Ascending:
       type: boolean
+    type_:IncludeSpam:
+      type: boolean
     type_:Count:
       type: integer
     type_threads:ThreadId:
@@ -8794,6 +8829,11 @@ paths:
           required: false
           schema:
             $ref: '#/components/schemas/type_:Ascending'
+        - name: include_spam
+          in: query
+          required: false
+          schema:
+            $ref: '#/components/schemas/type_:IncludeSpam'
         - name: Authorization
           in: header
           description: >-
@@ -8832,6 +8872,8 @@ components:
       format: date-time
     type_:Ascending:
       type: boolean
+    type_:IncludeSpam:
+      type: boolean
     type_:Count:
       type: integer
     type_threads:ThreadId:
@@ -13196,6 +13238,11 @@ paths:
           required: false
           schema:
             $ref: '#/components/schemas/type_:Ascending'
+        - name: include_spam
+          in: query
+          required: false
+          schema:
+            $ref: '#/components/schemas/type_:IncludeSpam'
         - name: Authorization
           in: header
           description: >-
@@ -13232,6 +13279,8 @@ components:
       format: date-time
     type_:Ascending:
       type: boolean
+    type_:IncludeSpam:
+      type: boolean
     type_:Count:
       type: integer
     type_inboxes:InboxId:
@@ -16126,7 +16175,11 @@ components:
       type: array
       items:
         $ref: '#/components/schemas/type_events:EventType'
-    type_webhooks:InboxIds:
+    type_events:PodIds:
+      type: array
+      items:
+        type: string
+    type_events:InboxIds:
       type: array
       items:
         type: string
@@ -16141,14 +16194,16 @@ components:
           $ref: '#/components/schemas/type_webhooks:Url'
         event_types:
           $ref: '#/components/schemas/type_events:EventTypes'
+        pod_ids:
+          $ref: '#/components/schemas/type_events:PodIds'
         inbox_ids:
-          $ref: '#/components/schemas/type_webhooks:InboxIds'
+          $ref: '#/components/schemas/type_events:InboxIds'
         secret:
           type: string
           description: Secret for webhook signature verification.
         enabled:
           type: boolean
-          description: Whether the webhook is enabled.
+          description: Webhook is enabled.
         updated_at:
           type: string
           format: date-time
@@ -16373,7 +16428,11 @@ components:
       type: array
       items:
         $ref: '#/components/schemas/type_events:EventType'
-    type_webhooks:InboxIds:
+    type_events:PodIds:
+      type: array
+      items:
+        type: string
+    type_events:InboxIds:
       type: array
       items:
         type: string
@@ -16388,14 +16447,16 @@ components:
           $ref: '#/components/schemas/type_webhooks:Url'
         event_types:
           $ref: '#/components/schemas/type_events:EventTypes'
+        pod_ids:
+          $ref: '#/components/schemas/type_events:PodIds'
         inbox_ids:
-          $ref: '#/components/schemas/type_webhooks:InboxIds'
+          $ref: '#/components/schemas/type_events:InboxIds'
         secret:
           type: string
           description: Secret for webhook signature verification.
         enabled:
           type: boolean
-          description: Whether the webhook is enabled.
+          description: Webhook is enabled.
         updated_at:
           type: string
           format: date-time
@@ -16604,7 +16665,11 @@ components:
       type: array
       items:
         $ref: '#/components/schemas/type_events:EventType'
-    type_webhooks:InboxIds:
+    type_events:PodIds:
+      type: array
+      items:
+        type: string
+    type_events:InboxIds:
       type: array
       items:
         type: string
@@ -16617,8 +16682,10 @@ components:
           $ref: '#/components/schemas/type_webhooks:Url'
         event_types:
           $ref: '#/components/schemas/type_events:EventTypes'
+        pod_ids:
+          $ref: '#/components/schemas/type_events:PodIds'
         inbox_ids:
-          $ref: '#/components/schemas/type_webhooks:InboxIds'
+          $ref: '#/components/schemas/type_events:InboxIds'
         client_id:
           $ref: '#/components/schemas/type_webhooks:ClientId'
       required:
@@ -16635,14 +16702,16 @@ components:
           $ref: '#/components/schemas/type_webhooks:Url'
         event_types:
           $ref: '#/components/schemas/type_events:EventTypes'
+        pod_ids:
+          $ref: '#/components/schemas/type_events:PodIds'
         inbox_ids:
-          $ref: '#/components/schemas/type_webhooks:InboxIds'
+          $ref: '#/components/schemas/type_events:InboxIds'
         secret:
           type: string
           description: Secret for webhook signature verification.
         enabled:
           type: boolean
-          description: Whether the webhook is enabled.
+          description: Webhook is enabled.
         updated_at:
           type: string
           format: date-time
@@ -18172,6 +18241,14 @@ components:
       type: array
       items:
         $ref: '#/components/schemas/type_events:EventType'
+    type_events:InboxIds:
+      type: array
+      items:
+        type: string
+    type_events:PodIds:
+      type: array
+      items:
+        type: string
     type_websockets:Subscribed:
       type: object
       properties:
@@ -18183,15 +18260,9 @@ components:
         event_types:
           $ref: '#/components/schemas/type_events:EventTypes'
         inbox_ids:
-          type: array
-          items:
-            type: string
-          description: IDs of the inboxes that have been subscribed to.
+          $ref: '#/components/schemas/type_events:InboxIds'
         pod_ids:
-          type: array
-          items:
-            type: string
-          description: IDs of the pods that have been subscribed to.
+          $ref: '#/components/schemas/type_events:PodIds'
       required:
         - type
     type_events:EventId:
@@ -18826,15 +18897,9 @@ components:
         event_types:
           $ref: '#/components/schemas/type_events:EventTypes'
         inbox_ids:
-          type: array
-          items:
-            type: string
-          description: IDs of the inboxes to subscribe to.
+          $ref: '#/components/schemas/type_events:InboxIds'
         pod_ids:
-          type: array
-          items:
-            type: string
-          description: IDs of the pods to subscribe to.
+          $ref: '#/components/schemas/type_events:PodIds'
       required:
         - type
 
@@ -20589,26 +20654,6 @@ paths:
           required: false
           schema:
             $ref: '#/components/schemas/type_:PageToken'
-        - name: labels
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:Labels'
-        - name: before
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:Before'
-        - name: after
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:After'
-        - name: ascending
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:Ascending'
         - name: Authorization
           in: header
           description: >-
@@ -20635,18 +20680,6 @@ components:
       type: integer
     type_:PageToken:
       type: string
-    type_:Labels:
-      type: array
-      items:
-        type: string
-    type_:Before:
-      type: string
-      format: date-time
-    type_:After:
-      type: string
-      format: date-time
-    type_:Ascending:
-      type: boolean
     type_:Count:
       type: integer
     type_inboxes:InboxId:
@@ -21522,6 +21555,11 @@ paths:
           required: false
           schema:
             $ref: '#/components/schemas/type_:Ascending'
+        - name: include_spam
+          in: query
+          required: false
+          schema:
+            $ref: '#/components/schemas/type_:IncludeSpam'
         - name: Authorization
           in: header
           description: >-
@@ -21560,6 +21598,8 @@ components:
       format: date-time
     type_:Ascending:
       type: boolean
+    type_:IncludeSpam:
+      type: boolean
     type_:Count:
       type: integer
     type_inboxes:InboxId:
@@ -23154,26 +23194,6 @@ paths:
           required: false
           schema:
             $ref: '#/components/schemas/type_:PageToken'
-        - name: labels
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:Labels'
-        - name: before
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:Before'
-        - name: after
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:After'
-        - name: ascending
-          in: query
-          required: false
-          schema:
-            $ref: '#/components/schemas/type_:Ascending'
         - name: Authorization
           in: header
           description: >-
@@ -23200,18 +23220,6 @@ components:
       type: integer
     type_:PageToken:
       type: string
-    type_:Labels:
-      type: array
-      items:
-        type: string
-    type_:Before:
-      type: string
-      format: date-time
-    type_:After:
-      type: string
-      format: date-time
-    type_:Ascending:
-      type: boolean
     type_:Count:
       type: integer
     type_domains:DomainId: