@opusdns/api 1.137.0 → 1.139.0

package/README.md

@@ -61,34 +61,69 @@ import {
 
 ## Documentation
 
-There are two documentation setups in this repository:
-
-### Legacy: GitHub Pages API Reference (production)
-
-The `docs/` folder is a static site that embeds
-[`@scalar/api-reference`](https://github.com/scalar/scalar) and is published
-via GitHub Pages on [developers.opusdns.com](https://developers.opusdns.com/).
-Source of truth: [`docs/index.html`](./docs/index.html). Do **not** put
-guides/Markdown content here.
-
-### Scalar Docs 2.0 (local preview)
-
-A more sophisticated documentation setup using
-[Scalar Docs 2.0](https://scalar.com/products/docs/getting-started) is
-contained in [`scalar/`](./scalar/). The Scalar project config lives at
-[`scalar/scalar.config.json`](./scalar/scalar.config.json), guide content lives
-under [`scalar/content/`](./scalar/content/), and the API reference is
-fetched from the raw GitHub copy of [`src/openapi.yaml`](./src/openapi.yaml).
-
-To preview locally:
+[developers.opusdns.com](https://developers.opusdns.com/) is served by
+[Scalar Docs 2.0](https://scalar.com/products/docs/getting-started) from
+[`scalar/`](./scalar/) in this repository.
+
+### How publishing works
+
+**Merging to `main` publishes.** Scalar's GitHub integration builds `main`; there
+is no deploy workflow in this repo and no Scalar token. The custom domain is
+declared in the config itself
+([`scalar/scalar.config.json`](./scalar/scalar.config.json), `siteConfig.customDomain`),
+not in CI. Nothing in the repository shows this connection, so it is written down
+here: if publishing ever stops, the integration in the Scalar dashboard is where
+to look.
+
+**Every PR gets a preview.** The same integration builds each pull request and
+posts a throwaway URL as a comment (`…--opusdns-api-spec.apidocumentation.com`),
+so you can read a change as rendered before merging it. Use it — a bad `filepath`
+or an icon name Scalar does not know renders as nothing rather than failing, and
+merging is what makes that public.
+
+The preview does not, however, cover the bots' own PRs: GitHub suppresses
+workflow runs for pull requests opened with a token rather than by a person, so
+both bots validate the config inline before opening theirs.
+
+### Layout
+
+| Path | What |
+| --- | --- |
+| `scalar/scalar.config.json` | The whole site: tabs, sidebar routes, theme. Every page's title, icon and URL live here — content files carry no frontmatter |
+| `scalar/content/` | Guide Markdown |
+| `scalar/content/tld-knowledge-base/` | **Generated** from `OpusDNS/tld-specifications` by `scripts/generate_tld_knowledge_base.py` |
+| `scalar/content/mcp-server/` | **Generated** in `OpusDNS/opusdns-mcp`, which opens a PR here carrying the diff. `scripts/sync_mcp_docs.py` lives here but is run from there — see [`scripts/mcp_docs/`](./scripts/mcp_docs/) |
+| `src/openapi.yaml` | The spec. The API Reference tab is fetched by Scalar from the raw GitHub URL at build time, so it is eventually consistent rather than bundled |
+
+Two bots write `scalar.config.json`: **Generate TLD Knowledge Base**, a workflow
+in this repo, and **Publish MCP docs to api-spec**, a workflow in
+`OpusDNS/opusdns-mcp` that opens its PR here. Each rebuilds only the subtree it
+owns and both serialise identically (`json.dumps(..., indent=2,
+ensure_ascii=False)` plus a trailing newline), so hand edits should match that
+style — otherwise the next bot PR reformats your lines.
+
+### Local preview
 
 ```bash
 npm install
 npm --prefix scalar install
 npm run docs:preview
 # → http://localhost:7970
+
+npm --prefix scalar run check   # validate scalar.config.json
 ```
 
+Run `check` before pushing anything that touches the config. A `filepath`
+pointing at a file that does not exist, or an icon name Scalar does not know,
+renders as nothing — and merging is what publishes.
+
+### The legacy `docs/` folder
+
+[`docs/`](./docs/) is a static GitHub Pages site that embeds
+[`@scalar/api-reference`](https://github.com/scalar/scalar). GitHub Pages is
+still configured for it, but DNS points at Scalar, so **it is not what serves the
+domain**. Treat it as vestigial; do not put content there.
+
 ### Links
 
 - [Main website](https://www.opusdns.com/)

package/package.json

@@ -3,7 +3,7 @@
     "@opusdns/api-spec-ts-generator": "^1.5.0"
   },
   "name": "@opusdns/api",
-  "version": "1.137.0",
+  "version": "1.139.0",
   "description": "TypeScript types for the OpusDNS OpenAPI specification",
   "main": "./src/index.ts",
   "module": "./src/index.ts",

package/src/helpers/constants.ts

@@ -56,6 +56,7 @@ import type {
   HostStatus,
   HttpProtocol,
   IPAddressType,
+  InvoiceDocumentType,
   InvoiceResponsePaymentStatus,
   InvoiceResponseStatus,
   InvoiceResponseType,
@@ -1095,6 +1096,16 @@ export const IP_ADDRESS_TYPE_VALUES = [
   'v6',
 ] as const satisfies ReadonlyArray<IPAddressType>;
 
+export const INVOICE_DOCUMENT_TYPE = {
+  INVOICE: "invoice",
+  RECEIPT: "receipt",
+} as const satisfies Record<string, InvoiceDocumentType>;
+
+export const INVOICE_DOCUMENT_TYPE_VALUES = [
+  'invoice',
+  'receipt',
+] as const satisfies ReadonlyArray<InvoiceDocumentType>;
+
 export const INVOICE_RESPONSE_PAYMENT_STATUS = {
   PENDING: "pending",
   FAILED: "failed",

package/src/helpers/endpoints.ts

@@ -110,6 +110,7 @@ export const ORGANIZATIONS_USERS_ENDPOINT = '/v1/organizations/users';
 export const ORGANIZATIONS_BY_ORGANIZATION_ID_ENDPOINT = '/v1/organizations/{organization_id}';
 export const ORGANIZATIONS_BY_ORGANIZATION_ID_ATTRIBUTES_ENDPOINT = '/v1/organizations/{organization_id}/attributes';
 export const ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_INVOICES_ENDPOINT = '/v1/organizations/{organization_id}/billing/invoices';
+export const ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_RECEIPTS_ENDPOINT = '/v1/organizations/{organization_id}/billing/receipts';
 export const ORGANIZATIONS_BY_ORGANIZATION_ID_PRICING_PRODUCT_TYPE_BY_PRODUCT_TYPE_ENDPOINT = '/v1/organizations/{organization_id}/pricing/product-type/{product_type}';
 export const ORGANIZATIONS_BY_ORGANIZATION_ID_TRANSACTIONS_ENDPOINT = '/v1/organizations/{organization_id}/transactions';
 export const ORGANIZATIONS_BY_ORGANIZATION_ID_TRANSACTIONS_BY_TRANSACTION_ID_ENDPOINT = '/v1/organizations/{organization_id}/transactions/{transaction_id}';
@@ -263,6 +264,7 @@ export type Endpoint =
   | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_ENDPOINT
   | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_ATTRIBUTES_ENDPOINT
   | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_INVOICES_ENDPOINT
+  | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_RECEIPTS_ENDPOINT
   | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_PRICING_PRODUCT_TYPE_BY_PRODUCT_TYPE_ENDPOINT
   | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_TRANSACTIONS_ENDPOINT
   | typeof ORGANIZATIONS_BY_ORGANIZATION_ID_TRANSACTIONS_BY_TRANSACTION_ID_ENDPOINT

package/src/helpers/keys.ts

@@ -3651,6 +3651,7 @@ export const KEYS_IDN_BASE = [
 
 export const KEY_INVOICE_AMOUNT = 'amount' satisfies keyof Invoice;
 export const KEY_INVOICE_CURRENCY = 'currency' satisfies keyof Invoice;
+export const KEY_INVOICE_DOCUMENT_TYPE = 'document_type' satisfies keyof Invoice;
 export const KEY_INVOICE_EXTERNAL_ID = 'external_id' satisfies keyof Invoice;
 export const KEY_INVOICE_FEES_AMOUNT = 'fees_amount' satisfies keyof Invoice;
 export const KEY_INVOICE_FILE_URL = 'file_url' satisfies keyof Invoice;
@@ -3666,6 +3667,7 @@ export const KEY_INVOICE_TAXES_AMOUNT = 'taxes_amount' satisfies keyof Invoice;
 export const KEYS_INVOICE = [
   KEY_INVOICE_AMOUNT,
   KEY_INVOICE_CURRENCY,
+  KEY_INVOICE_DOCUMENT_TYPE,
   KEY_INVOICE_EXTERNAL_ID,
   KEY_INVOICE_FEES_AMOUNT,
   KEY_INVOICE_FILE_URL,

package/src/helpers/permissions.ts

@@ -106,6 +106,7 @@ import {
   ORGANIZATIONS_ATTRIBUTES_ENDPOINT,
   ORGANIZATIONS_BY_ORGANIZATION_ID_ATTRIBUTES_ENDPOINT,
   ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_INVOICES_ENDPOINT,
+  ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_RECEIPTS_ENDPOINT,
   ORGANIZATIONS_BY_ORGANIZATION_ID_ENDPOINT,
   ORGANIZATIONS_BY_ORGANIZATION_ID_PRICING_PRODUCT_TYPE_BY_PRODUCT_TYPE_ENDPOINT,
   ORGANIZATIONS_BY_ORGANIZATION_ID_TRANSACTIONS_BY_TRANSACTION_ID_ENDPOINT,
@@ -949,6 +950,13 @@ export const REQUIRED_PERMISSIONS = {
     patch: [],
     delete: [],
   },
+  [ORGANIZATIONS_BY_ORGANIZATION_ID_BILLING_RECEIPTS_ENDPOINT]: {
+    get: [PUBLIC_PERMISSION.BILLING_MANAGE],
+    post: [],
+    put: [],
+    patch: [],
+    delete: [],
+  },
   [ORGANIZATIONS_BY_ORGANIZATION_ID_ENDPOINT]: {
     get: [PUBLIC_PERMISSION.ORGANIZATION_READ],
     post: [],

package/src/helpers/requests.d.ts

@@ -880,6 +880,12 @@ export type GET_OrganizationsByOrganizationIdBillingInvoices_Request = {
 export type GET_OrganizationsByOrganizationIdBillingInvoices_Request_Query = GET_OrganizationsByOrganizationIdBillingInvoices_Request['parameters']['query'];
 export type GET_OrganizationsByOrganizationIdBillingInvoices_Request_Path = GET_OrganizationsByOrganizationIdBillingInvoices_Request['parameters']['path'];
 
+export type GET_OrganizationsByOrganizationIdBillingReceipts_Request = {
+  parameters: operations['list_receipts_v1_organizations__organization_id__billing_receipts_get']['parameters'];
+};
+export type GET_OrganizationsByOrganizationIdBillingReceipts_Request_Query = GET_OrganizationsByOrganizationIdBillingReceipts_Request['parameters']['query'];
+export type GET_OrganizationsByOrganizationIdBillingReceipts_Request_Path = GET_OrganizationsByOrganizationIdBillingReceipts_Request['parameters']['path'];
+
 export type GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Request = {
   parameters: operations['get_pricing_plans_v1_organizations__organization_id__pricing_product_type__product_type__get']['parameters'];
 };

package/src/helpers/responses.d.ts

@@ -679,6 +679,11 @@ export type GET_OrganizationsByOrganizationIdBillingInvoices_Response = GET_Orga
 export type GET_OrganizationsByOrganizationIdBillingInvoices_Response_200 = Pagination_Invoice;
 export type GET_OrganizationsByOrganizationIdBillingInvoices_Response_422 = HTTPValidationError;
 
+export type GET_OrganizationsByOrganizationIdBillingReceipts_Response = GET_OrganizationsByOrganizationIdBillingReceipts_Response_200 | GET_OrganizationsByOrganizationIdBillingReceipts_Response_422;
+
+export type GET_OrganizationsByOrganizationIdBillingReceipts_Response_200 = Pagination_Invoice;
+export type GET_OrganizationsByOrganizationIdBillingReceipts_Response_422 = HTTPValidationError;
+
 export type GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Response = GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Response_200 | GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Response_401 | GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Response_403 | GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Response_422;
 
 export type GET_OrganizationsByOrganizationIdPricingProductTypeByProductType_Response_200 = GetPrices;

package/src/helpers/schemas.d.ts

@@ -327,6 +327,7 @@ export type HttpRedirectRequest = components['schemas']['HttpRedirectRequest'];
 export type HttpRedirectUpsert = components['schemas']['HttpRedirectUpsert'];
 export type IPAddressType = components['schemas']['IPAddressType'];
 export type IdnBase = components['schemas']['IdnBase'];
+export type InvoiceDocumentType = components['schemas']['InvoiceDocumentType'];
 export type Invoice = components['schemas']['InvoiceResponse'];
 export type InvoiceResponsePaymentStatus = components['schemas']['InvoiceResponsePaymentStatus'];
 export type InvoiceResponseStatus = components['schemas']['InvoiceResponseStatus'];

package/src/openapi.yaml

@@ -8302,6 +8302,17 @@ components:
       - idn_capable
       title: IdnBase
       type: object
+    InvoiceDocumentType:
+      description: 'Customer-facing document class. Orthogonal to `InvoiceResponseType`:
+        prepaid-credit invoices are receipts,
+
+        everything else billable is an invoice. Documents billing classifies as neither
+        are never returned.'
+      enum:
+      - invoice
+      - receipt
+      title: InvoiceDocumentType
+      type: string
     InvoiceResponse:
       properties:
         amount:
@@ -8312,6 +8323,9 @@ components:
         currency:
           $ref: '#/components/schemas/Currency'
           description: Invoice currency
+        document_type:
+          $ref: '#/components/schemas/InvoiceDocumentType'
+          description: Customer-facing document class
         external_id:
           description: Lago ID (external) for this invoice
           title: External Id
@@ -8365,6 +8379,7 @@ components:
       - issuing_date
       - payment_due_date
       - invoice_type
+      - document_type
       - status
       - payment_status
       - payment_overdue
@@ -15765,7 +15780,7 @@ info:
     \n\n"
   summary: OpusDNS - your gateway to a seamless domain management experience.
   title: OpusDNS API
-  version: 2026-08-26-021624
+  version: 2026-08-27-083857
   x-logo:
     altText: OpusDNS API Reference
     url: https://d24lr4zqs1tgqh.cloudfront.net/c9505a20-5ae1-406c-b060-d392569caebf.jpg
@@ -23423,18 +23438,33 @@ paths:
       - domain_forwards:manage
   /v1/domain-search/suggest:
     get:
-      description: Get a list of domain suggestions based on a search query
+      description: "Get a list of domain suggestions based on a search query.\n\n\
+        Suggestions are generated and ranked by relevance rather than enumerated from\
+        \ a fixed list, so the\nresults depend on the shape of `query`:\n\n- **Keyword\
+        \ or phrase** (e.g. `bluewidgets`) \u2014 every result is a generated name,\
+        \ and its `available`\n  flag is best-effort.\n- **Full domain name** (e.g.\
+        \ `bluewidgets.de`) \u2014 the queried domain is always returned as the first\n\
+        \  result, with availability checked directly against the registry.\n\nUse\
+        \ a full domain name, or `GET /v1/availability`, whenever you need a definitive\
+        \ answer about a\nspecific domain."
       operationId: suggest_v1_domain_search_suggest_get
       parameters:
-      - description: The primary keyword or phrase for the domain search
+      - description: The primary keyword or phrase for the domain search. A full domain
+          name is always returned as the first result, with registry-checked availability.
         in: query
         name: query
         required: true
         schema:
-          description: The primary keyword or phrase for the domain search
+          description: The primary keyword or phrase for the domain search. A full
+            domain name is always returned as the first result, with registry-checked
+            availability.
           title: Query
           type: string
-      - description: The TLDs to include in the search
+      - description: 'Restricts results to these TLDs. This is a filter, not a guarantee:
+          suggestions are ranked by relevance across the whole requested set, so a
+          listed TLD may be absent from the results even when available names exist
+          in it, and raising `limit` does not change that. To guarantee a TLD is represented,
+          query it on its own.'
         examples:
           list:
             summary: A list of TLDs
@@ -23451,7 +23481,11 @@ paths:
               type: string
             type: array
           - type: 'null'
-          description: The TLDs to include in the search
+          description: 'Restricts results to these TLDs. This is a filter, not a guarantee:
+            suggestions are ranked by relevance across the whole requested set, so
+            a listed TLD may be absent from the results even when available names
+            exist in it, and raising `limit` does not change that. To guarantee a
+            TLD is represented, query it on its own.'
           title: Tlds
       - description: The maximum number of domain suggestions to return
         in: query
@@ -30456,6 +30490,61 @@ paths:
       - organization
       x-required-permissions:
       - billing:manage
+  /v1/organizations/{organization_id}/billing/receipts:
+    get:
+      description: Retrieves a paginated list of all payment receipts for the organization
+      operationId: list_receipts_v1_organizations__organization_id__billing_receipts_get
+      parameters:
+      - in: path
+        name: organization_id
+        required: true
+        schema:
+          examples:
+          - organization_01h45ytscbebyvny4gc8cr8ma2
+          format: typeid
+          pattern: ^organization_[0-7][0-9a-hjkmnpq-tv-z]{25}$
+          title: Organization Id
+          type: string
+          x-typeid-prefix: organization
+      - in: query
+        name: page
+        required: false
+        schema:
+          default: 1
+          minimum: 1
+          title: Page
+          type: integer
+      - in: query
+        name: page_size
+        required: false
+        schema:
+          default: 10
+          maximum: 1000
+          minimum: 1
+          title: Page Size
+          type: integer
+      - $ref: '#/components/parameters/DatetimeFormatHeader'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/Pagination_InvoiceResponse_'
+          description: Successful Response
+        '422':
+          content:
+            application/problem+json:
+              schema:
+                $ref: '#/components/schemas/HTTPValidationError'
+          description: Validation Error
+      security:
+      - OAuth2PasswordBearer: []
+      - APIKeyHeader: []
+      summary: List all payment receipts for the organization
+      tags:
+      - organization
+      x-required-permissions:
+      - billing:manage
   /v1/organizations/{organization_id}/pricing/product-type/{product_type}:
     get:
       description: Retrieves pricing data for a specific product type. If a product
@@ -33664,9 +33753,33 @@ tags:
 - description: ''
   name: domain_tld_specific
   x-displayName: TLD specific domain management
-- description: 'Endpoints for searching domains.
-
-    '
+- description: "Endpoints for searching domains.\n\n### Keyword queries vs. full domain\
+    \ names\n\n`GET /v1/domain-search/suggest` behaves differently depending on the\
+    \ shape of the `query` value:\n\n- **Keyword or phrase** (e.g. `bluewidgets`)\
+    \ \u2014 every result is a name produced by our suggestion engine, which generates\
+    \ candidates and ranks them by relevance. No particular name is guaranteed to\
+    \ appear.\n- **Full domain name** (e.g. `bluewidgets.de`) \u2014 the queried domain\
+    \ is always returned as the first result, and its availability is checked directly\
+    \ against the registry rather than coming from the suggestion engine.\n\nUse a\
+    \ full domain name whenever you need a definitive answer about one specific domain.\
+    \ To check several specific domains at once, use `GET /v1/availability` instead.\n\
+    \n### `tlds` restricts results, it does not guarantee them\n\nThe `tlds` parameter\
+    \ is a filter: results are limited to the TLDs you list, but a TLD you list may\
+    \ still be absent from the response. Suggestions are ranked by relevance across\
+    \ the whole requested set, so a keyword whose strongest candidates are `.com`/`.net`/`.org`\
+    \ names can return no `.de` results even though available `.de` names exist for\
+    \ that keyword.\n\nThis is consistent for a given keyword rather than random \u2014\
+    \ the same query returns the same TLD mix each time \u2014 and raising `limit`\
+    \ does not change it.\n\nTo guarantee that a TLD is represented, query it on its\
+    \ own:\n\n```\nGET /v1/domain-search/suggest?query=bluewidgets&tlds=de&limit=5\n\
+    ```\n\nIssuing one request per TLD is the reliable way to build a per-TLD view\
+    \ in a search interface.\n\n### Availability of suggestions\n\nThe `available`\
+    \ flag on a generated suggestion is best-effort. Our suggestion engine's data\
+    \ is not authoritative for every TLD, and it is less accurate for some ccTLDs,\
+    \ so a suggestion can occasionally be shown as available when it is not.\n\nAvailability\
+    \ is authoritative in two cases: when the query is a full domain name (the first\
+    \ result), and for domains checked via `GET /v1/availability`. Always confirm\
+    \ with one of those before presenting a domain as purchasable.\n"
   name: domain_search
   x-displayName: Domain search
 - description: "Endpoints for managing host objects (nameserver glue records).\n\n\

package/src/schema.d.ts

@@ -1063,7 +1063,18 @@ export interface paths {
         };
         /**
          * Suggest domains
-         * @description Get a list of domain suggestions based on a search query
+         * @description Get a list of domain suggestions based on a search query.
+         *
+         *     Suggestions are generated and ranked by relevance rather than enumerated from a fixed list, so the
+         *     results depend on the shape of `query`:
+         *
+         *     - **Keyword or phrase** (e.g. `bluewidgets`) — every result is a generated name, and its `available`
+         *       flag is best-effort.
+         *     - **Full domain name** (e.g. `bluewidgets.de`) — the queried domain is always returned as the first
+         *       result, with availability checked directly against the registry.
+         *
+         *     Use a full domain name, or `GET /v1/availability`, whenever you need a definitive answer about a
+         *     specific domain.
          */
         get: operations["suggest_v1_domain_search_suggest_get"];
         put?: never;
@@ -2293,6 +2304,26 @@ export interface paths {
         patch?: never;
         trace?: never;
     };
+    "/v1/organizations/{organization_id}/billing/receipts": {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List all payment receipts for the organization
+         * @description Retrieves a paginated list of all payment receipts for the organization
+         */
+        get: operations["list_receipts_v1_organizations__organization_id__billing_receipts_get"];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     "/v1/organizations/{organization_id}/pricing/product-type/{product_type}": {
         parameters: {
             query?: never;
@@ -8460,6 +8491,13 @@ export interface components {
              */
             idn_tables?: string[] | null;
         };
+        /**
+         * InvoiceDocumentType
+         * @description Customer-facing document class. Orthogonal to `InvoiceResponseType`: prepaid-credit invoices are receipts,
+         *     everything else billable is an invoice. Documents billing classifies as neither are never returned.
+         * @enum {string}
+         */
+        InvoiceDocumentType: "invoice" | "receipt";
         /** InvoiceResponse */
         InvoiceResponse: {
             /**
@@ -8469,6 +8507,8 @@ export interface components {
             amount: string;
             /** @description Invoice currency */
             currency: components["schemas"]["Currency"];
+            /** @description Customer-facing document class */
+            document_type: components["schemas"]["InvoiceDocumentType"];
             /**
              * External Id
              * @description Lago ID (external) for this invoice
@@ -19178,9 +19218,9 @@ export interface operations {
     suggest_v1_domain_search_suggest_get: {
         parameters: {
             query: {
-                /** @description The primary keyword or phrase for the domain search */
+                /** @description The primary keyword or phrase for the domain search. A full domain name is always returned as the first result, with registry-checked availability. */
                 query: string;
-                /** @description The TLDs to include in the search */
+                /** @description Restricts results to these TLDs. This is a filter, not a guarantee: suggestions are ranked by relevance across the whole requested set, so a listed TLD may be absent from the results even when available names exist in it, and raising `limit` does not change that. To guarantee a TLD is represented, query it on its own. */
                 tlds?: string[] | null;
                 /** @description The maximum number of domain suggestions to return */
                 limit?: number | null;
@@ -25181,6 +25221,46 @@ export interface operations {
             };
         };
     };
+    list_receipts_v1_organizations__organization_id__billing_receipts_get: {
+        parameters: {
+            query?: {
+                page?: number;
+                page_size?: number;
+            };
+            header?: {
+                /**
+                 * @description Opt in to RFC 3339 datetime serialization. When set to `rfc3339`, response datetimes are normalized to UTC and serialized with a `Z` suffix. This is opt-in until the announced default cutover date, after which RFC 3339 becomes the default and this header is accepted as a no-op. Any other value or omission uses the current default serialization.
+                 * @example rfc3339
+                 */
+                "X-Datetime-Format"?: components["parameters"]["DatetimeFormatHeader"];
+            };
+            path: {
+                organization_id: TypeId<"organization">;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["Pagination_InvoiceResponse_"];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/problem+json": components["schemas"]["HTTPValidationError"];
+                };
+            };
+        };
+    };
     get_pricing_plans_v1_organizations__organization_id__pricing_product_type__product_type__get: {
         parameters: {
             query?: {