openapi.yaml - v2025-10-13

I used a tool (openapi-generator-cli) for generating Java classes (api, auth, model) from the openapi.yaml (v2025-10-13). So far all good. The definition of the "Contact" is found at line 7176. I am using that definitin for creating a new Contact using X-B2B-API-Version:2025-10-13 and https://api-staging.b2brouter.net/ via a request like this:

Request{method=POST, url=https://api-staging.b2brouter.net/accounts/77640/contacts, headers=[X-B2B-API-Version:2025-10-13, X-B2B-API-Key:b4a51...[masked_content]...3095bfe8, Accept:application/json, Content-Type:application/json, User-Agent:OpenAPI-Generator/2025-10-13/java]}

{
"tin_value":"DE304950997",
"tin_scheme":"9930",
"name":"Acconsis GmbH Steuerberatungsgesellschaft",
"email":"[email protected]",
"address":"Schloßschmidstrasse 5",
"postalcode":"80639",
"city":"München",
"country":"DE",
"language":"de",
"currency":"EUR",
"is_client":true,
"is_provider":false,
"transport_type_code":"peppol",
"document_type_code":"xml.ubl.invoice.bis3",
"pin_value":"de300725330",
"pin_scheme":"9930",
"payment_method":0,
"terms":"custom",
"public_sector":false
}

When receiving back the response I get:

Response{protocol=h2, code=200, message=, url=https://api-staging.b2brouter.net/accounts/77640/contacts}

{
"id": 1313309250,
"tin_value": "DE304950997",
"tin_scheme": 9930,
"name": "Acconsis GmbH Steuerberatungsgesellschaft",
...,
"edi_code": null,
...,
"created_at": "2025-11-06T13:55:04Z",
"updated_at": "2025-11-06T13:55:04Z"
}

Any idea why I am getting back in the response for a contact the "edi_code" field? That is not defined/described in the openapi.yaml (v2025-10-13) for the Contact object. However is described for a "ContactReduced" object (which I guess it is wrong). Getting "invalid" fields in the response will make not pass the "automatic" validation done in the java classes generated by the openapi-generator-cli based on the openapi.yaml.

Any chance to fix that on your end or better I should find my own solution to that?

Kind regards,

Codrin