@opusdns/api 1.12.0 → 1.14.0

package/src/openapi.yaml

@@ -2125,6 +2125,16 @@ components:
       type: object
     CreateReportReq:
       properties:
+        registrar_credential_id:
+          anyOf:
+          - examples:
+            - registrar_credential_01h45ytscbebyvny4gc8cr8ma2
+            format: typeid
+            pattern: ^registrar_credential_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+            type: string
+            x-typeid-prefix: registrar_credential
+          - type: 'null'
+          title: Registrar Credential Id
         report_type:
           $ref: '#/components/schemas/ReportType'
           default: domain_inventory
@@ -6436,6 +6446,113 @@ components:
       - licensee
       title: HolderEntitlement
       type: string
+    HostCreate:
+      properties:
+        hostname:
+          description: Hostname of the host object
+          examples:
+          - ns1.example.com
+          title: Hostname
+          type: string
+        ip_addresses:
+          description: List of IP addresses for the host object
+          examples:
+          - - 192.0.2.53
+            - 2001:db8::53
+          items:
+            format: ipvanyaddress
+            type: string
+          minItems: 1
+          title: Ip Addresses
+          type: array
+      required:
+      - hostname
+      - ip_addresses
+      title: HostCreate
+      type: object
+    HostIpSchema:
+      properties:
+        address:
+          description: IP address of the host object
+          format: ipvanyaddress
+          title: Address
+          type: string
+        created_on:
+          description: The date/time the entry was created on
+          format: date-time
+          title: Created On
+          type: string
+        host_id:
+          default: None
+          examples:
+          - host_01h45ytscbebyvny4gc8cr8ma2
+          format: typeid
+          pattern: ^host_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+          title: Host Id
+          type: string
+          x-typeid-prefix: host
+        host_ip_id:
+          examples:
+          - host_ip_01h45ytscbebyvny4gc8cr8ma2
+          format: typeid
+          pattern: ^host_ip_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+          title: Host Ip Id
+          type: string
+          x-typeid-prefix: host_ip
+        type:
+          $ref: '#/components/schemas/IPAddressType'
+          description: IP address type
+        updated_on:
+          description: The date/time the entry was last updated on
+          format: date-time
+          title: Updated On
+          type: string
+      required:
+      - address
+      - type
+      title: HostIpSchema
+      type: object
+    HostResponse:
+      properties:
+        created_on:
+          description: Timestamp when the host was created
+          format: date-time
+          title: Created On
+          type: string
+        host_id:
+          description: Unique identifier of the host object
+          examples:
+          - host_01h45ytscbebyvny4gc8cr8ma2
+          format: typeid
+          pattern: ^host_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+          title: Host Id
+          type: string
+          x-typeid-prefix: host
+        hostname:
+          description: Hostname of the host object
+          examples:
+          - ns1.example.com
+          title: Hostname
+          type: string
+        ip_addresses:
+          description: The ip addresses of the Host Object
+          items:
+            format: ipvanyaddress
+            type: string
+          title: Ip Addresses
+          type: array
+        updated_on:
+          description: Timestamp when the host was last updated
+          format: date-time
+          title: Updated On
+          type: string
+      required:
+      - host_id
+      - hostname
+      - created_on
+      - updated_on
+      title: HostResponse
+      type: object
     HostSchema:
       properties:
         created_on:
@@ -6498,6 +6615,23 @@ components:
       - pending_delete
       title: HostStatus
       type: string
+    HostUpdate:
+      properties:
+        ip_addresses:
+          description: List of IP addresses for the host object
+          examples:
+          - - 192.0.2.53
+            - 2001:db8::53
+          items:
+            format: ipvanyaddress
+            type: string
+          minItems: 1
+          title: Ip Addresses
+          type: array
+      required:
+      - ip_addresses
+      title: HostUpdate
+      type: object
     HttpProtocol:
       enum:
       - http
@@ -6622,6 +6756,12 @@ components:
       - request_hostname
       title: HttpRedirectUpsert
       type: object
+    IPAddressType:
+      enum:
+      - v4
+      - v6
+      title: IPAddressType
+      type: string
     IdnBase:
       properties:
         idn_capable:
@@ -9989,6 +10129,7 @@ components:
       - domain_forwards
       - expiring_domains
       - email_forwards
+      - registrar_portfolio_pdf
       - billing_transactions
       - billing_transactions_monthly
       title: ReportType
@@ -12001,7 +12142,7 @@ info:
     \n\n"
   summary: OpusDNS - your gateway to a seamless domain management experience.
   title: OpusDNS API
-  version: 2026-06-11-173831
+  version: 2026-06-12-181220
   x-logo:
     altText: OpusDNS API Reference
     url: https://d24lr4zqs1tgqh.cloudfront.net/c9505a20-5ae1-406c-b060-d392569caebf.jpg
@@ -21938,6 +22079,346 @@ paths:
       - event
       x-required-permissions:
       - events:manage
+  /v1/hosts:
+    post:
+      description: Create a new host object
+      operationId: create_host_v1_hosts_post
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/HostCreate'
+        required: true
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HostResponse'
+          description: Successful Response
+        '401':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_AUTHENTICATION
+                detail: Additional error context.
+                status: 401
+                title: Authentication Error
+                type: authentication
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Unauthorized
+        '403':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_PERMISSION_DENIED
+                detail: Additional error context.
+                status: 403
+                title: Permission Denied
+                type: permission-denied
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Forbidden
+        '404':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_PARENT_DOMAIN_NOT_FOUND
+                detail: Parent domain not found for host 'Additional error context.'
+                hostname: Additional error context.
+                parent_domain: ''
+                status: 404
+                title: Host Management Error
+                type: parent-domain-not-found
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Not Found
+        '409':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_HOST_ALREADY_EXISTS
+                detail: Host already exists
+                hostname: Additional error context.
+                status: 409
+                title: Host Management Error
+                type: host-already-exists
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Conflict
+        '422':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_HOST_OBJECTS_NOT_SUPPORTED
+                detail: Host objects are not supported for this tld
+                status: 422
+                title: Host Management Error
+                tld: Additional error context.
+                type: host-object-not-supported
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Unprocessable Content
+      security:
+      - OAuth2PasswordBearer: []
+      - APIKeyHeader: []
+      summary: Create a Host Object
+      tags:
+      - host
+      x-required-permissions:
+      - hosts:manage
+  /v1/hosts/{host_reference}:
+    delete:
+      description: Deletes a host object; only possible if the host is not in use
+      operationId: delete_host_v1_hosts__host_reference__delete
+      parameters:
+      - in: path
+        name: host_reference
+        required: true
+        schema:
+          anyOf:
+          - examples:
+            - host_01h45ytscbebyvny4gc8cr8ma2
+            format: typeid
+            pattern: ^host_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+            type: string
+            x-typeid-prefix: host
+          - type: string
+          title: Host Reference
+      responses:
+        '204':
+          description: Successful Response
+        '401':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_AUTHENTICATION
+                detail: Additional error context.
+                status: 401
+                title: Authentication Error
+                type: authentication
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Unauthorized
+        '403':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_PERMISSION_DENIED
+                detail: Additional error context.
+                status: 403
+                title: Permission Denied
+                type: permission-denied
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Forbidden
+        '404':
+          content:
+            application/problem+json:
+              examples:
+                Host Management Error:
+                  value:
+                    code: ERROR_PARENT_DOMAIN_NOT_FOUND
+                    detail: Parent domain not found for host 'Additional error context.'
+                    hostname: Additional error context.
+                    parent_domain: ''
+                    status: 404
+                    title: Host Management Error
+                    type: parent-domain-not-found
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Not Found
+        '409':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_HOST_IN_USE
+                detail: Host is linked to one or more domains
+                host_reference: Additional error context.
+                status: 409
+                title: Host Management Error
+                type: host-in-use
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Conflict
+        '422':
+          content:
+            application/problem+json:
+              schema:
+                $ref: '#/components/schemas/HTTPValidationError'
+          description: Validation Error
+      security:
+      - OAuth2PasswordBearer: []
+      - APIKeyHeader: []
+      summary: Delete a Host Object
+      tags:
+      - host
+      x-required-permissions:
+      - hosts:delete
+    get:
+      description: Retrieves a host object by either its ID or hostname
+      operationId: get_host_v1_hosts__host_reference__get
+      parameters:
+      - in: path
+        name: host_reference
+        required: true
+        schema:
+          anyOf:
+          - examples:
+            - host_01h45ytscbebyvny4gc8cr8ma2
+            format: typeid
+            pattern: ^host_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+            type: string
+            x-typeid-prefix: host
+          - type: string
+          title: Host Reference
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HostResponse'
+          description: Successful Response
+        '401':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_AUTHENTICATION
+                detail: Additional error context.
+                status: 401
+                title: Authentication Error
+                type: authentication
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Unauthorized
+        '403':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_PERMISSION_DENIED
+                detail: Additional error context.
+                status: 403
+                title: Permission Denied
+                type: permission-denied
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Forbidden
+        '404':
+          content:
+            application/problem+json:
+              examples:
+                Host Management Error:
+                  value:
+                    code: ERROR_PARENT_DOMAIN_NOT_FOUND
+                    detail: Parent domain not found for host 'Additional error context.'
+                    hostname: Additional error context.
+                    parent_domain: ''
+                    status: 404
+                    title: Host Management Error
+                    type: parent-domain-not-found
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Not Found
+        '422':
+          content:
+            application/problem+json:
+              schema:
+                $ref: '#/components/schemas/HTTPValidationError'
+          description: Validation Error
+      security:
+      - OAuth2PasswordBearer: []
+      - APIKeyHeader: []
+      summary: Retrieve a Host Object
+      tags:
+      - host
+      x-required-permissions:
+      - hosts:read
+    put:
+      description: Updates the IP addresses of a host object, referenced by either
+        its ID or hostname
+      operationId: update_host_v1_hosts__host_reference__put
+      parameters:
+      - in: path
+        name: host_reference
+        required: true
+        schema:
+          anyOf:
+          - examples:
+            - host_01h45ytscbebyvny4gc8cr8ma2
+            format: typeid
+            pattern: ^host_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+            type: string
+            x-typeid-prefix: host
+          - type: string
+          title: Host Reference
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/HostUpdate'
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HostResponse'
+          description: Successful Response
+        '401':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_AUTHENTICATION
+                detail: Additional error context.
+                status: 401
+                title: Authentication Error
+                type: authentication
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Unauthorized
+        '403':
+          content:
+            application/problem+json:
+              example:
+                code: ERROR_PERMISSION_DENIED
+                detail: Additional error context.
+                status: 403
+                title: Permission Denied
+                type: permission-denied
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Forbidden
+        '404':
+          content:
+            application/problem+json:
+              examples:
+                Host Management Error:
+                  value:
+                    code: ERROR_PARENT_DOMAIN_NOT_FOUND
+                    detail: Parent domain not found for host 'Additional error context.'
+                    hostname: Additional error context.
+                    parent_domain: ''
+                    status: 404
+                    title: Host Management Error
+                    type: parent-domain-not-found
+              schema:
+                $ref: '#/components/schemas/Problem'
+          description: Not Found
+        '422':
+          content:
+            application/problem+json:
+              schema:
+                $ref: '#/components/schemas/HTTPValidationError'
+          description: Validation Error
+      security:
+      - OAuth2PasswordBearer: []
+      - APIKeyHeader: []
+      summary: Update a Host Object
+      tags:
+      - host
+      x-required-permissions:
+      - hosts:manage
   /v1/job/{job_id}:
     delete:
       operationId: delete_job_v1_job__job_id__delete
@@ -26546,6 +27027,31 @@ tags:
     '
   name: domain_search
   x-displayName: Domain search
+- description: "Endpoints for managing host objects (nameserver glue records).\n\n\
+    ### What is a host object?\n\nA host object represents a nameserver hostname registered\
+    \ at a registry. When a nameserver hostname is subordinate to a domain in your\
+    \ portfolio (e.g. `ns1.example.com` under `example.com`), the registry requires\
+    \ a host object carrying one or more IP addresses \u2014 commonly known as glue\
+    \ records \u2014 so that resolvers can reach the nameserver even though its address\
+    \ lives inside the zone it serves.\n\nThese endpoints manage **subordinate** host\
+    \ objects: the parent domain of the hostname must be managed in your OpusDNS account.\
+    \ Hostnames whose parent domain is not in your account are rejected with `ERROR_PARENT_DOMAIN_NOT_FOUND`.\
+    \ External nameservers (e.g. your DNS provider's hostnames) do not need host objects\
+    \ \u2014 simply reference them by hostname when setting a domain's nameservers.\n\
+    \n### Referencing a host\n\n`GET`, `PUT` and `DELETE` accept either the host ID\
+    \ (`host_...`) or the hostname as the `{host_reference}` path parameter.\n\n###\
+    \ Lifecycle\n\n- **Create** \u2014 `POST /v1/hosts` with the hostname and at least\
+    \ one IP address. The host object is created at the registry of the parent domain.\
+    \ Creating a host that already exists returns `ERROR_HOST_ALREADY_EXISTS`.\n-\
+    \ **Update** \u2014 `PUT /v1/hosts/{host_reference}` replaces the host's IP addresses\
+    \ with the provided list. If the provided addresses match the current state at\
+    \ the registry, the request succeeds without performing a registry update.\n-\
+    \ **Delete** \u2014 `DELETE /v1/hosts/{host_reference}` removes the host object.\
+    \ A host that is still in use as a nameserver by one or more domains cannot be\
+    \ deleted and returns `ERROR_HOST_IN_USE`.\n\nNot all TLDs use host objects; for\
+    \ TLDs without host object support, creation is rejected with `ERROR_HOST_OBJECTS_NOT_SUPPORTED`.\n"
+  name: host
+  x-displayName: Hosts
 - description: 'Endpoints for creating and managing email forwards.
 
     '
@@ -26594,50 +27100,67 @@ tags:
     \ | Summary of all DNS zones and their configuration |\n| `dns_zone_records` |\
     \ Detailed export of all DNS records across zones |\n| `billing_transactions`\
     \ | Billing transactions for the current month to date |\n| `billing_transactions_monthly`\
-    \ | Billing transactions for the previous calendar month |\n\n### Billing Transaction\
-    \ Reports\n\nBilling transaction reports export all completed transactions as\
-    \ a CSV with the following columns: `product_reference`, `action`, `period`, `product_type`,\
-    \ `amount`, `currency`, `completed_on`.\n\nThere are two billing report types:\n\
-    \n- **`billing_transactions`** \u2014 On-demand report covering the current month\
-    \ to date (1st of the month through the time of the request). Request this via\
-    \ the API like any other report type.\n- **`billing_transactions_monthly`** \u2014\
-    \ Automatically generated on the 1st of each month at 5 AM UTC, covering the full\
-    \ previous calendar month. These are scheduled reports and do not need to be manually\
-    \ requested.\n\nBoth types maintain their own retention of 30 reports each, so\
-    \ requesting on-demand reports will not displace the monthly archive.\n\n### Report\
-    \ Lifecycle\n\nA report transitions through the following statuses:\n\n1. **pending**\
-    \ \u2014 Report has been queued for generation\n2. **generating** \u2014 Report\
-    \ is being built\n3. **completed** \u2014 Report is ready for download\n4. **failed**\
-    \ \u2014 Generation failed\n\n### Usage Pattern\n\n1. **Request a report** \u2014\
-    \ `POST /v1/reports` with the desired `report_type`\n2. **Poll for completion**\
-    \ \u2014 `GET /v1/reports/{report_id}` until `status` is `completed`\n3. **Download**\
-    \ \u2014 `GET /v1/reports/{report_id}/download` returns the report as a streamed\
-    \ ZIP file\n\n### Downloading Reports\n\n`GET /v1/reports/{report_id}/download`\
-    \ streams the report file directly to the client. The report **must** have status\
-    \ `completed` before it can be downloaded \u2014 calling this endpoint on a report\
-    \ that is still `pending` or `generating` returns `409 Conflict`.\n\n**Response\
-    \ details:**\n\n| Header | Value |\n|--------|-------|\n| `Content-Type` | `application/zip`\
-    \ |\n| `Content-Disposition` | `attachment; filename={report_type}-{report_id}.zip`\
-    \ |\n| `Content-Length` | File size in bytes (included when known) |\n\nThe response\
-    \ body is streamed in chunks, so clients should read the body incrementally rather\
-    \ than buffering it entirely in memory. When `Content-Length` is present, it can\
-    \ be used to display download progress.\n\n### Trigger Types\n\n| Type | Description\
-    \ |\n|------|-------------|\n| `on_demand` | Manually requested via the API |\n\
-    | `scheduled` | Automatically generated on a recurring schedule |\n\n### Rate\
-    \ Limiting\n\nReport creation is rate-limited at two levels:\n\n- **Cooldown**\
-    \ \u2014 After creating a report, you must wait **5 minutes** before requesting\
-    \ another report of the same type. Requests during the cooldown return `429 Too\
-    \ Many Requests` with a `Retry-After` header.\n- **Hourly limit** \u2014 Only\
-    \ **one report per type per organization per clock hour** (UTC) can be generated.\
-    \ Duplicate requests within the same hour will not produce an additional report.\n\
-    \n### Retention\n\nThe **30 most recent reports** of each type are kept per organization.\
-    \ Older reports and their associated files are automatically deleted when a new\
-    \ report is generated.\n\n### Listing Reports\n\nUse `GET /v1/reports` to list\
-    \ reports with optional filters:\n\n| Parameter | Description |\n|-----------|-------------|\n\
-    | `report_type` | Filter by report type (repeatable) |\n| `status` | Filter by\
-    \ report status (repeatable) |\n| `trigger_type` | Filter by trigger type |\n\
-    | `created_after` | Only reports created after this timestamp |\n| `created_before`\
-    \ | Only reports created before this timestamp |\n"
+    \ | Billing transactions for the previous calendar month |\n| `registrar_portfolio_pdf`\
+    \ | Credential-scoped registrar portfolio report as a PDF inside the ZIP download\
+    \ |\n\n### Billing Transaction Reports\n\nBilling transaction reports export all\
+    \ completed transactions as a CSV with the following columns: `product_reference`,\
+    \ `action`, `period`, `product_type`, `amount`, `currency`, `completed_on`.\n\n\
+    There are two billing report types:\n\n- **`billing_transactions`** \u2014 On-demand\
+    \ report covering the current month to date (1st of the month through the time\
+    \ of the request). Request this via the API like any other report type.\n- **`billing_transactions_monthly`**\
+    \ \u2014 Automatically generated on the 1st of each month at 5 AM UTC, covering\
+    \ the full previous calendar month. These are scheduled reports and do not need\
+    \ to be manually requested.\n\nBoth types maintain their own retention of 30 reports\
+    \ each, so requesting on-demand reports will not displace the monthly archive.\n\
+    \n### Registrar Portfolio PDF Reports\n\nRegistrar portfolio reports are requested\
+    \ with `POST /v1/reports` and require `registrar_credential_id`:\n\n```json\n\
+    {\n  \"report_type\": \"registrar_portfolio_pdf\",\n  \"registrar_credential_id\"\
+    : \"registrar_credential_...\"\n}\n```\n\nThe report uses registrar data from\
+    \ the registrar-elements OpenSearch index, populated by the scheduled daily registrar\
+    \ syncs. Report generation does not trigger a sync; it uses the most recently\
+    \ synced data as-is. If the credential has no portfolio data yet (for example,\
+    \ a credential created since the last sync), generation fails with an error indicating\
+    \ the credential is too new to report on.\n\nThe downloaded ZIP contains `registrar-portfolio-{report_typeid}.pdf`.\
+    \ Before each PDF generation, the report service loads the organization's current\
+    \ available TLD list from the backend and uses it to mark TLDs in the portfolio\
+    \ as available or unavailable. The first version includes the sections backed\
+    \ by indexed data: portfolio overview, domains/statuses/TLDs/nameservers, TLD\
+    \ availability, expiry summaries, contact validation summary, and DNS record summaries.\
+    \ Additional sections that require new OpenSearch fields will be added explicitly\
+    \ when those fields are indexed.\n\n### Report Lifecycle\n\nA report transitions\
+    \ through the following statuses:\n\n1. **pending** \u2014 Report has been queued\
+    \ for generation\n2. **generating** \u2014 Report is being built\n3. **completed**\
+    \ \u2014 Report is ready for download\n4. **failed** \u2014 Generation failed\n\
+    \n### Usage Pattern\n\n1. **Request a report** \u2014 `POST /v1/reports` with\
+    \ the desired `report_type`\n2. **Poll for completion** \u2014 `GET /v1/reports/{report_id}`\
+    \ until `status` is `completed`\n3. **Download** \u2014 `GET /v1/reports/{report_id}/download`\
+    \ returns the report as a streamed ZIP file\n\n### Downloading Reports\n\n`GET\
+    \ /v1/reports/{report_id}/download` streams the report file directly to the client.\
+    \ The report **must** have status `completed` before it can be downloaded \u2014\
+    \ calling this endpoint on a report that is still `pending` or `generating` returns\
+    \ `409 Conflict`.\n\n**Response details:**\n\n| Header | Value |\n|--------|-------|\n\
+    | `Content-Type` | `application/zip` |\n| `Content-Disposition` | `attachment;\
+    \ filename={report_type}-{report_id}.zip` |\n| `Content-Length` | File size in\
+    \ bytes (included when known) |\n\nThe response body is streamed in chunks, so\
+    \ clients should read the body incrementally rather than buffering it entirely\
+    \ in memory. When `Content-Length` is present, it can be used to display download\
+    \ progress.\n\n### Trigger Types\n\n| Type | Description |\n|------|-------------|\n\
+    | `on_demand` | Manually requested via the API |\n| `scheduled` | Automatically\
+    \ generated on a recurring schedule |\n\n### Rate Limiting\n\nReport creation\
+    \ is rate-limited at two levels:\n\n- **Cooldown** \u2014 After creating a report,\
+    \ you must wait **5 minutes** before requesting another report of the same type.\
+    \ Requests during the cooldown return `429 Too Many Requests` with a `Retry-After`\
+    \ header.\n- **Hourly limit** \u2014 Only **one report per type per organization\
+    \ per clock hour** (UTC) can be generated. Duplicate requests within the same\
+    \ hour will not produce an additional report.\n\n### Retention\n\nThe **30 most\
+    \ recent reports** of each type are kept per organization. Older reports and their\
+    \ associated files are automatically deleted when a new report is generated.\n\
+    \n### Listing Reports\n\nUse `GET /v1/reports` to list reports with optional filters:\n\
+    \n| Parameter | Description |\n|-----------|-------------|\n| `report_type` |\
+    \ Filter by report type (repeatable) |\n| `status` | Filter by report status (repeatable)\
+    \ |\n| `trigger_type` | Filter by trigger type |\n| `created_after` | Only reports\
+    \ created after this timestamp |\n| `created_before` | Only reports created before\
+    \ this timestamp |\n"
   name: report
   x-displayName: Reports
 - description: Endpoints for creating new Tags
@@ -26654,6 +27177,7 @@ x-tagGroups:
   - domain
   - domain_tld_specific
   - tld
+  - host
   - contact
   - event
   - availability