@epilot/customer-portal-client 0.49.0 → 0.50.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@epilot/customer-portal-client",
-  "version": "0.49.0",
+  "version": "0.50.0",
   "description": "API Client for epilot portal API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/src/openapi-runtime.json

@@ -1488,6 +1488,13 @@
     "/v2/portal/contract/by-identifiers": {
       "post": {
         "operationId": "addContractByIdentifiers",
+        "parameters": [
+          {
+            "in": "query",
+            "name": "correlation_id",
+            "required": false
+          }
+        ],
         "requestBody": {
           "required": true,
           "content": {
@@ -2944,6 +2951,16 @@
           "application/json": {}
         }
       },
+      "ContractAssignmentNotFound": {
+        "content": {
+          "application/json": {}
+        }
+      },
+      "ContactAmbiguousMatch": {
+        "content": {
+          "application/json": {}
+        }
+      },
       "NotFound": {
         "content": {
           "application/json": {}

package/src/openapi.json

@@ -4011,6 +4011,17 @@
                         "NOT_FOUND"
                       ],
                       "description": "Present only when exists is false. NOT_FOUND means the given identifiers did\nnot match any contact (definitive - the client should not retry). TIMEOUT\nmeans the contact was not found within the processing window but may still be\ningesting; the client may retry (ideally with trigger_identifiers_check=false).\n"
+                    },
+                    "correlation_id": {
+                      "type": "string",
+                      "minLength": 1,
+                      "maxLength": 255,
+                      "pattern": "^[A-Za-z0-9_-]+$",
+                      "description": "Correlation id of the triggered ERP sync. Present only for portals waiting on\nthe Integration Toolkit (`wait_for_toolkit`). Send it back with\n`trigger_identifiers_check: false` to keep waiting on the same correlation.\n"
+                    },
+                    "message": {
+                      "type": "string",
+                      "description": "Human-readable reason the identifiers did not resolve, when the portal knows\none. Set when the ERP finished sending for this correlation without the\nentities the portal needs (e.g. \"account data arrived, no contract\"), so\nsupport can tell a silent timeout from an incomplete delivery.\n"
                     }
                   }
                 }
@@ -4023,6 +4034,9 @@
           "404": {
             "$ref": "#/components/responses/NotFound"
           },
+          "409": {
+            "$ref": "#/components/responses/ContactAmbiguousMatch"
+          },
           "429": {
             "$ref": "#/components/responses/TooManyRequests"
           },
@@ -4074,7 +4088,7 @@
         },
         "responses": {
           "200": {
-            "description": "The identification result. On a match, `contact_id` and `token` are present. When no\ncontact matched, only `reason` is present - the response is deliberately shaped the same\nway for every negative outcome so it cannot be used to enumerate contacts.\n",
+            "description": "The identification result. On a match, `contact_id` and `token` are present. When no\ncontact matched, only `reason` is present - the response is deliberately shaped the same\nway for every negative outcome so it cannot be used to enumerate contacts. The one\naddition is `correlation_id` on a TIMEOUT from a portal waiting on the Integration\nToolkit, which a retry needs; what the ERP did or did not send is never part of it.\nThat includes an ERP delivery of several matching contacts: unlike\n`checkContactExistsV3`, which answers it with 409 `AMBIGUOUS_MATCH`, this endpoint\nanswers it as `NOT_FOUND`, because the 409 would confirm that the ERP knows the\nidentifiers.\n",
             "content": {
               "application/json": {
                 "schema": {
@@ -6262,7 +6276,7 @@
       "post": {
         "operationId": "addContractByIdentifiers",
         "summary": "addContractByIdentifiers",
-        "description": "Self-assign contract(s) by pre-configured identifiers.",
+        "description": "Self-assign contract(s) by pre-configured identifiers.\n\nWhen the portal is configured to wait on the Integration Toolkit\n(`extension_hooks.contractIdentification.wait_for_toolkit`) and the ERP has not finished\nsending within the request budget, the call fails with 404 and `reason: TIMEOUT`, carrying\nthe `correlation_id` of the triggered sync. Repeating the call with that `correlation_id`\nkeeps waiting on the same correlation without calling the third party again.\n",
         "tags": [
           "ECP"
         ],
@@ -6271,6 +6285,20 @@
             "PortalAuth": []
           }
         ],
+        "parameters": [
+          {
+            "in": "query",
+            "name": "correlation_id",
+            "required": false,
+            "schema": {
+              "type": "string",
+              "minLength": 1,
+              "maxLength": 255,
+              "pattern": "^[A-Za-z0-9_-]+$"
+            },
+            "description": "Correlation id of an already triggered ERP sync, as returned by a previous call that\nfailed with `reason: TIMEOUT`. Keeps waiting on the same correlation instead of calling\nthe contract identification hook again. Ignored unless the portal is configured with\n`extension_hooks.contractIdentification.wait_for_toolkit`. At most 255 letters, digits,\nhyphens and underscores: the toolkit's bound for a correlation id and the charset it\nenforces on its identifiers.\n"
+          }
+        ],
         "requestBody": {
           "description": "Identifiers to search by. Have to be pre-configured in Portal Configuration Permissions.",
           "required": true,
@@ -6332,6 +6360,9 @@
           "403": {
             "$ref": "#/components/responses/Forbidden"
           },
+          "404": {
+            "$ref": "#/components/responses/ContractAssignmentNotFound"
+          },
           "409": {
             "$ref": "#/components/responses/ContractAssignmentConflict"
           },
@@ -12198,13 +12229,31 @@
                 },
                 {
                   "properties": {
+                    "status": {
+                      "type": "integer",
+                      "description": "The HTTP status code, repeated in the body.",
+                      "example": 409
+                    },
+                    "error": {
+                      "type": "string",
+                      "description": "Human-readable error message. For support, not for display to end customers."
+                    },
                     "reason": {
                       "type": "string",
-                      "description": "Reason why the contract is not assignable. If the reason is \"MULTIPLE\", the contract is not assignable because multiple contracts were found and the business logic does not allow it.",
+                      "description": "Reason why the contract is not assignable.\n- `DRAFT`: the contract is still a draft.\n- `MULTIPLE`: multiple contracts were found and the business logic does not allow it.\n- `SELF_ASSIGNMENT_DISABLED`: the contract already has a contact assigned and\n  self-assignment is disabled.\n- `AMBIGUOUS_MATCH`: the portal waited on the Integration Toolkit and the ERP\n  delivered entities it cannot tell apart (several matching the selector, or\n  contracts naming different customers). Nothing was assigned, and retrying\n  will not help.\n",
                       "enum": [
                         "DRAFT",
-                        "MULTIPLE"
+                        "MULTIPLE",
+                        "SELF_ASSIGNMENT_DISABLED",
+                        "AMBIGUOUS_MATCH"
                       ]
+                    },
+                    "correlation_id": {
+                      "type": "string",
+                      "minLength": 1,
+                      "maxLength": 255,
+                      "pattern": "^[A-Za-z0-9_-]+$",
+                      "description": "Correlation id of the ERP sync that was waited on. Present only with `AMBIGUOUS_MATCH`."
                     }
                   },
                   "required": [
@@ -12216,6 +12265,84 @@
           }
         }
       },
+      "ContractAssignmentNotFound": {
+        "description": "No contract could be assigned. Without a `reason`, the identifiers matched nothing. With\n`reason`, the portal waited on the Integration Toolkit\n(`extension_hooks.contractIdentification.wait_for_toolkit`):\n- `TIMEOUT`: the ERP has not finished sending yet. Repeat the request with the\n  `correlation_id` query parameter set to the `correlation_id` of this body to keep waiting\n  on the same ERP sync without calling the third party again.\n- `INCOMPLETE`: the ERP finished sending without the data needed. Definitive; `error` names\n  what was missing, for support, not for display to end customers.\n",
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "status": {
+                  "type": "integer",
+                  "description": "The HTTP status code, repeated in the body.",
+                  "example": 404
+                },
+                "error": {
+                  "type": "string",
+                  "description": "Human-readable error message. For support, not for display to end customers."
+                },
+                "reason": {
+                  "type": "string",
+                  "enum": [
+                    "TIMEOUT",
+                    "INCOMPLETE"
+                  ]
+                },
+                "correlation_id": {
+                  "type": "string",
+                  "minLength": 1,
+                  "maxLength": 255,
+                  "pattern": "^[A-Za-z0-9_-]+$",
+                  "description": "Correlation id of the ERP sync that was waited on. Present with `TIMEOUT` and `INCOMPLETE`."
+                }
+              },
+              "required": [
+                "status",
+                "error"
+              ]
+            }
+          }
+        }
+      },
+      "ContactAmbiguousMatch": {
+        "description": "The portal waited on the Integration Toolkit\n(`extension_hooks.registrationIdentifiersCheck.wait_for_toolkit`) and the ERP delivered\nseveral contacts matching the identifiers. Nothing was linked; retrying will not help.\n",
+        "content": {
+          "application/json": {
+            "schema": {
+              "type": "object",
+              "properties": {
+                "status": {
+                  "type": "integer",
+                  "description": "The HTTP status code, repeated in the body.",
+                  "example": 409
+                },
+                "error": {
+                  "type": "string",
+                  "description": "Human-readable error message. For support, not for display to end customers."
+                },
+                "reason": {
+                  "type": "string",
+                  "enum": [
+                    "AMBIGUOUS_MATCH"
+                  ]
+                },
+                "correlation_id": {
+                  "type": "string",
+                  "minLength": 1,
+                  "maxLength": 255,
+                  "pattern": "^[A-Za-z0-9_-]+$",
+                  "description": "Correlation id of the ERP sync that was waited on."
+                }
+              },
+              "required": [
+                "status",
+                "error",
+                "reason"
+              ]
+            }
+          }
+        }
+      },
       "NotFound": {
         "description": "The specified resource was not found",
         "content": {
@@ -13591,15 +13718,6 @@
               }
             ]
           },
-          "self_assignment_mode": {
-            "type": "string",
-            "enum": [
-              "contracts",
-              "customer_to_portal_user"
-            ],
-            "default": "contracts",
-            "description": "What the built-in self-assignment (without a contractIdentification hook) assigns once the `contract_identifiers` match a Contract:\n  - `contracts`: the user's Contact is added as a customer of the Contract.\n  - `customer_to_portal_user`: the Contract's customers (Contacts and Accounts) are added to the Portal User's `represents`. The Portal User sees all their data, including Contracts, transitively. Mirrors the `contact_to_portal_user` assignment mode of the contractIdentification hook.\n"
-          },
           "contract_selector_config": {
             "type": "object",
             "description": "Configuration for contract selector in the portal",
@@ -14338,6 +14456,14 @@
             "type": "boolean",
             "default": true,
             "description": "Whether to (re)trigger the registration identifiers check hook, which issues a request\nto the connected ERP to (re)sync the contact, in addition to waiting for the entity to\narrive. Defaults to true to preserve existing behaviour. Set to false on retry attempts\nto only poll for an already-triggered sync to land, without issuing another upstream\nrequest to the ERP.\n"
+          },
+          "correlation_id": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 255,
+            "pattern": "^[A-Za-z0-9_-]+$",
+            "description": "Correlation id of an already triggered ERP sync, as returned by a previous call that\nanswered `reason: TIMEOUT`. Sent together with `trigger_identifiers_check: false` on a\nretry so the portal keeps waiting on the same correlation instead of starting over.\nOnly used by portals configured with\n`extension_hooks.registrationIdentifiersCheck.wait_for_toolkit`; ignored otherwise.\nAt most 255 letters, digits, hyphens and underscores: the toolkit's bound for a\ncorrelation id and the charset it enforces on its identifiers.\n",
+            "example": "0199c0d5-6f1c-7a3b-9e21-9a9ce1d1b2c3"
           }
         }
       },
@@ -14416,6 +14542,13 @@
               "NOT_FOUND"
             ],
             "description": "Present only when no token was issued. NOT_FOUND means the given identifiers did not\nmatch any contact (definitive - the client should not retry). TIMEOUT means the contact\nwas not found within the processing window but may still be ingesting; the client may\nretry (ideally with trigger_identifiers_check=false).\n"
+          },
+          "correlation_id": {
+            "type": "string",
+            "minLength": 1,
+            "maxLength": 255,
+            "pattern": "^[A-Za-z0-9_-]+$",
+            "description": "Correlation id of the triggered ERP sync. Present only with `reason: TIMEOUT`, for\nportals waiting on the Integration Toolkit (`wait_for_toolkit`). Send it back with\n`trigger_identifiers_check: false` to keep waiting on the same correlation.\n"
           }
         }
       },
@@ -17494,6 +17627,36 @@
           "hook_id": {
             "type": "string",
             "description": "The ID of the selected hook."
+          },
+          "wait_for_toolkit": {
+            "type": "boolean",
+            "default": false,
+            "description": "Opt in to waiting on the Integration Toolkit instead of polling entity search for the\ndata the ERP pushes after the hook returns. When true, the portal hands the hook a\ncorrelation id (`{{CorrelationId}}`) and then asks the toolkit whether the entities it\nneeds have landed under that correlation. Off by default: a portal that does not set it\nkeeps polling entity search exactly as before.\n\nOnly effective for hooks whose partner pushes through the Integration Toolkit and\nechoes the correlation id. A hook that answers with an epilot contact id is fetched\ndirectly, as today, whatever this flag says.\n"
+          },
+          "wait_for_entities": {
+            "type": "object",
+            "description": "The entities the portal waits for, keyed by entity slug. Configured explicitly per\nhook: nothing is derived from the hook type or from the portal's identifier\nconfiguration, and a hook that configures no requirement for the entity the portal\nlinks does not wait at all - it keeps polling entity search exactly as before.\n\nA selector may only name an attribute that is literally a member of that entity\ntarget's configured `unique_ids` in the inbound use case, because the toolkit reports\nexactly those and nothing else. A selector on any other attribute can never match. A\ntoolkit that validates selectors rejects such a wait (400) with the slug, the key and\nthe keys it accepts; the portal logs that at error level with the hook it came from\nand polls entity search for the request, so the customer is unaffected and never told.\n\nThe slug the portal resolves its link target from is fixed by the hook, and a\nrequirement for it must be configured for the wait to happen at all:\n`registrationIdentifiersCheck` resolves the contact, every `contractIdentification`\nassignment mode resolves the contract (in the contact modes the linked contact is the\ndelivered contract's `customer`). Every other configured slug is evidence that the push\ncarried what it promised, and is never linked.\n\nIgnored unless `wait_for_toolkit` is true.\n\nWorked examples, verified against the live integration configuration. Each block is the\n`wait_for_entities` of one hook selection, and each names the slug that hook links.\n\nRatingen / Wilken add-contract hook (`contractIdentification`, `contact_to_portal_user`).\nNo value the user types is a unique id anywhere in the org - every one is a Wilken\nsurrogate `external_id` - so the contact cannot be selected by attribute at all. Wait on\nthe contract and link its `customer`; the identity-keyed contact is evidence that the\nbusiness partner landed, and is never linked.\n\n```yaml\ncontract: {}\ncontact:\n  key: external_id            # the PROFILE contact's unique id is external_id\n  from_caller_contact: external_id\n```\n\nWEMAG registration hook (`registrationIdentifiersCheck`). The contact's unique ids are\n`customer_pin` and `reenumber`; `meter.external_id` and `meter.meter_number` are both\nthe `ZNR` the user types.\n\n```yaml\ncontact:\n  key: reenumber\n  from_identifier: contact.complete_customer_number\n  split_on: \"-\"               # \"0002-<customer_pin>-<reenumber>\"\n  part: 2\nmeter:\n  key: external_id\n  from_identifier: meter.meter_number\n```\n\nWEMAG add-contract hook (`contractIdentification`, `contact_to_portal_user`). The\ncontract's unique ids are `billing_account_number` (the `reenumber`, the same third\npart of `complete_customer_number`) and `customer_number` (the PIN). Wait on the\ncontract of the typed Rechnungseinheit and link its `customer`.\n\n```yaml\ncontract:\n  key: billing_account_number\n  from_identifier: contact.complete_customer_number\n  split_on: \"-\"               # \"0002-<customer_pin>-<reenumber>\"\n  part: 2\nmeter:\n  key: external_id\n  from_identifier: meter.meter_number\n```\n\nNever `complete_customer_number` or `customer_number` on a WEMAG contact - neither is a\nunique id there - and never `customer_pin` alone on a contact or `customer_number` alone\non a contract, both of which are the PIN and ambiguous, because one person has one\ncontact and one contract per Rechnungseinheit. Never a key-less `contract` either: WEMAG's\n`EKM Anlagedaten` writes contracts of its own, keyed on `contract_number`.\n",
+            "additionalProperties": {
+              "$ref": "#/components/schemas/WaitForEntityRule"
+            },
+            "example": {
+              "contract": {},
+              "contact": {
+                "key": "external_id",
+                "from_caller_contact": "external_id"
+              }
+            }
+          },
+          "wait_for_use_cases": {
+            "type": "array",
+            "description": "Inbound use case slugs the portal additionally waits for. A requirement is met once at\nleast one event of that use case slug has finished processing, whether or not it\nproduced an entity, so it covers pushes whose entity set varies and pushes whose\noutcome is a file or a relation rather than an entity.\n\nEntity requirements stay primary - the portal links by entity id, so it always waits\nfor the entity it links. Use case slugs are an additional bar: when both are\nconfigured, both must be met. Empty by default. Ignored unless `wait_for_toolkit` is\ntrue.\n",
+            "items": {
+              "type": "string"
+            },
+            "default": [],
+            "example": [
+              "wilken_contract_changed"
+            ]
           }
         },
         "required": [
@@ -17502,6 +17665,39 @@
           "hook_id"
         ]
       },
+      "WaitForEntityRule": {
+        "type": "object",
+        "description": "One requirement of a hook's correlation wait, for the entity slug it is configured under.\n\nWithout `key` the requirement is satisfied by any entity of that slug. That is safe for\nevidence, and for a linked slug only where the inbound use case writes exactly one entity\nof it per push - Wilken's `BusinessPartnerChanged` always writes two contacts, and WEMAG's\n`DocumentChange` / `D3Metadata` write contacts under the same unique-id keys a registration\npush uses - so a second match answers 409 rather than linking a guess.\n\nWith `key`, the value comes from exactly one declared source, `from_identifier` or\n`from_caller_contact`. A rule whose source has no value produces no wait at all, so the\nhook keeps polling rather than waiting on a requirement that cannot be met.\n",
+        "properties": {
+          "key": {
+            "type": "string",
+            "description": "Unique-id attribute the selector matches on. Must be a member of that entity target's\nconfigured `unique_ids` in the inbound use case; the toolkit reports nothing else.\n",
+            "example": "reenumber"
+          },
+          "from_identifier": {
+            "type": "string",
+            "description": "Identifier the user submitted to take the value from, as `<schema>.<name>` - the same\nschema and name the portal's `registration_identifiers` / `contract_identifiers` use.\nMutually exclusive with `from_caller_contact`.\n",
+            "example": "contact.complete_customer_number"
+          },
+          "from_caller_contact": {
+            "type": "string",
+            "description": "Attribute of the calling portal user's own contact to take the value from. Only\navailable to hooks called by a signed-in user. Mutually exclusive with\n`from_identifier`.\n",
+            "example": "external_id"
+          },
+          "split_on": {
+            "type": "string",
+            "description": "Separator the source value is split on before `part` is taken, for identifiers that\ncarry a unique id inside a larger value the user types. WEMAG's\n`complete_customer_number` is `\"0002-<customer_pin>-<reenumber>\"`, so splitting on `-`\nand taking part 2 yields the contact's `reenumber` unique id.\n",
+            "example": "-"
+          },
+          "part": {
+            "type": "integer",
+            "minimum": 0,
+            "default": 0,
+            "description": "Zero-based index of the part to use after splitting on `split_on`.",
+            "example": 2
+          }
+        }
+      },
       "PublicExtensionCapabilities": {
         "type": "object",
         "properties": {
@@ -18240,6 +18436,10 @@
                 "type": "string",
                 "deprecated": true,
                 "description": "Deprecated. Use `resolved.result` instead. Contact ID usually retrieved from the response body, e.g. `{{CallResponse.data.contact_id}}`. If no result is passed and the request suceeds, we attempt to resolve the Contact ID automatically. Supports variable interpolation."
+              },
+              "result_correlation_id": {
+                "type": "string",
+                "description": "Correlation id to wait for inbound ERP events under, resolved from the third-party\nresponse, e.g. `{{CallResponse.data.acknowledgeId}}`. Only read when the portal is\nconfigured to wait on the Integration Toolkit\n(`extension_hooks.<hook>.wait_for_toolkit`).\n\nThere is no default: unless a hook declares this, the portal waits on the id it\nminted and handed the hook as `{{CorrelationId}}`, whatever the response carries. A\npartner that pushes under that id leaves this unset; only a partner that pushes\nunder an id of its own declares where the response carries it. A declared id that\nis absent from the response falls back to the minted one; one that is not a valid\ncorrelation id (at most 255 letters, digits, `-` and `_`) is not waited on, and\nthe portal polls entity search instead.\n"
               }
             },
             "required": [
@@ -18254,6 +18454,10 @@
                 "type": "string",
                 "description": "Contact ID usually retrieved from the response body, e.g. `{{CallResponse.data.contact_id}}`. If no result is passed and the request suceeds, we attempt to resolve the Contact ID automatically. Supports variable interpolation. Supersedes the deprecated `call.result`."
               },
+              "result_correlation_id": {
+                "type": "string",
+                "description": "Correlation id to wait for inbound ERP events under, resolved from the third-party\nresponse, e.g. `{{CallResponse.data.acknowledgeId}}`. Supersedes\n`call.result_correlation_id`. No default; see `call.result_correlation_id`.\n"
+              },
               "error_message_path": {
                 "type": "string",
                 "description": "Optional path to a human-readable error message in the third-party response body, used when the call fails (non-2xx status).\nIf specified and the path resolves to a string, that message is forwarded to the end user instead of a generic error.\n",
@@ -18325,6 +18529,10 @@
                 "type": "string",
                 "deprecated": true,
                 "description": "Deprecated. Use `resolved.result` instead. Contact ID usually retrieved from the response body, e.g. `{{CallResponse.data.contact_id}}`. If no result is passed and the request suceeds, we attempt to resolve the Contact ID automatically. Supports variable interpolation."
+              },
+              "result_correlation_id": {
+                "type": "string",
+                "description": "Correlation id to wait for inbound ERP events under, resolved from the third-party\nresponse, e.g. `{{CallResponse.data.acknowledgeId}}`. Only read when the portal is\nconfigured to wait on the Integration Toolkit\n(`extension_hooks.<hook>.wait_for_toolkit`).\n\nThere is no default: unless a hook declares this, the portal waits on the id it\nminted and handed the hook as `{{CorrelationId}}`, whatever the response carries. A\npartner that pushes under that id leaves this unset; only a partner that pushes\nunder an id of its own declares where the response carries it. A declared id that\nis absent from the response falls back to the minted one; one that is not a valid\ncorrelation id (at most 255 letters, digits, `-` and `_`) is not waited on, and\nthe portal polls entity search instead.\n"
               }
             },
             "required": [
@@ -18339,6 +18547,10 @@
                 "type": "string",
                 "description": "Contract or Contact ID usually retrieved from the response body, e.g. `{{CallResponse.data.contact_id}}`. If no result is passed and the request suceeds, we attempt to resolve the Contact ID automatically. Supports variable interpolation. Supersedes the deprecated `call.result`."
               },
+              "result_correlation_id": {
+                "type": "string",
+                "description": "Correlation id to wait for inbound ERP events under, resolved from the third-party\nresponse, e.g. `{{CallResponse.data.acknowledgeId}}`. Supersedes\n`call.result_correlation_id`. No default; see `call.result_correlation_id`.\n"
+              },
               "error_message_path": {
                 "type": "string",
                 "description": "Optional path to a human-readable error message in the third-party response body, used when the call fails (non-2xx status).\nIf specified and the path resolves to a string, that message is forwarded to the end user instead of a generic error.\n",
@@ -20690,15 +20902,6 @@
               }
             ]
           },
-          "self_assignment_mode": {
-            "type": "string",
-            "enum": [
-              "contracts",
-              "customer_to_portal_user"
-            ],
-            "default": "contracts",
-            "description": "What the built-in self-assignment (without a contractIdentification hook) assigns once the `contract_identifiers` match a Contract:\n  - `contracts`: the user's Contact is added as a customer of the Contract.\n  - `customer_to_portal_user`: the Contract's customers (Contacts and Accounts) are added to the Portal User's `represents`. The Portal User sees all their data, including Contracts, transitively. Mirrors the `contact_to_portal_user` assignment mode of the contractIdentification hook.\n"
-          },
           "contract_selector_config": {
             "type": "object",
             "description": "Configuration for contract selector in the portal",
@@ -21145,29 +21348,6 @@
           }
         }
       },
-      "PortalUsingDesign": {
-        "type": "object",
-        "description": "A portal whose design_id is the design asked about.",
-        "required": [
-          "portal_id"
-        ],
-        "properties": {
-          "portal_id": {
-            "$ref": "#/components/schemas/PortalId"
-          },
-          "name": {
-            "type": "string",
-            "example": "Kundenportal"
-          },
-          "origin": {
-            "$ref": "#/components/schemas/Origin"
-          },
-          "design_id": {
-            "type": "string",
-            "example": "9ba94f20-b872-11ed-b30a-b3e3bf2dc8ab"
-          }
-        }
-      },
       "PortalConfigSummaryV3": {
         "type": "object",
         "description": "Lightweight view of a portal config for lists and pickers. Carries the identifying,\ndisplay and registration fields only. Pages, email templates, grants, feature flags,\nidentity providers and certificate details are left out; read them per portal with\n`getPortalConfigV3`.\n",
@@ -21357,12 +21537,6 @@
           "design_id": {
             "type": "string",
             "description": "Design of the portal, used to preload it from the served document"
-          },
-          "design": {
-            "type": "object",
-            "additionalProperties": true,
-            "nullable": true,
-            "description": "The portal design as returned by design-builder parse (theme=NEW), for the served document; absent when the design could not be read"
           }
         }
       },