invoicetronic_sdk 1.9 → 1.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 26528c2b72851b8fb80fa975a54ec6ce01f0fcaa22ec0e857f35ae63d9c57a4a
-  data.tar.gz: 1917ebcb258bf9d1c47283766f831962d56eb16d53dd6402fe055f8bbddab890
+  metadata.gz: d8b8c56e3407502c2b0e473a367f599c8c43fad3ddc125a9c09fb6a360441d96
+  data.tar.gz: e617daf1be23b5569ed7ee4188fabd072ef7fe2547c1b73bb616b0704725a053
 SHA512:
-  metadata.gz: 546eb1877c9bc3ad20524bb3dabe8937aa80be36c2bdb61801e31271ba0b0b67a1b8fc1b1f3e5a33796894d8d7c3adeda23528226af256df235c9c0d44266d69
-  data.tar.gz: af27a9504e4d19069967b21071e6f7913b20c52b9b74f6425d1763a774b9bc1bb3430a189b6d65805294c3192a5d729b06143c0d3b329cbf16afd906b54ec53a
+  metadata.gz: 4b0356a5c293866f838de6f6f6d5418b5e764b12146af045c8636e294e523146c8e85e7eb783090425f4af7a31f622713233d5304677108a70ce095609cf9809
+  data.tar.gz: 9e800d7c1930a02ddfc1c74c4b6b0bdfe220da539d786178d837d5cfd1f7504966e95f0e6ac8e93dd82d7fc37b8b832e119a4609e8be7c76ef26c67f291a0e93

data/CHANGELOG.md

@@ -1 +1 @@
-# Changelog\n\n## [1.9.0] - 2026-07-07\nSee main repository changelog for details.
+# Changelog\n\n## [1.11.0] - 2026-09-23\nSee main repository changelog for details.

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    invoicetronic_sdk (1.9)
+    invoicetronic_sdk (1.11)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM
@@ -27,12 +27,12 @@ GEM
     ffi (1.17.4-x86_64-darwin)
     ffi (1.17.4-x86_64-linux-gnu)
     ffi (1.17.4-x86_64-linux-musl)
-    io-console (0.8.2)
+    io-console (0.9.4)
     jaro_winkler (1.5.6)
     logger (1.7.0)
     method_source (1.1.0)
     parallel (1.28.0)
-    parser (3.3.11.1)
+    parser (3.3.12.0)
       ast (~> 2.4.1)
       racc
     pry (0.16.0)
@@ -42,13 +42,13 @@ GEM
     pry-byebug (3.12.0)
       byebug (~> 13.0)
       pry (>= 0.13, < 0.17)
-    psych (5.4.0)
+    psych (5.5.0)
       date
       stringio
     racc (1.8.1)
     rainbow (3.1.1)
     rake (13.0.6)
-    reline (0.6.3)
+    reline (0.7.0)
       io-console (~> 0.5)
     rspec (3.13.2)
       rspec-core (~> 3.13.0)

data/README.md

@@ -23,8 +23,8 @@ For the full integration guide, tutorials, SDKs and quickstarts, see the **[Docu
 
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
-- API version: 1.14.0
-- Package version: 1.9
+- API version: 1.17.0
+- Package version: 1.11
 - Generator version: 7.20.0
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 For more information, please visit [https://invoicetronic.com/en/contact/](https://invoicetronic.com/en/contact/)
@@ -42,16 +42,16 @@ gem build invoicetronic_sdk.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./invoicetronic_sdk-1.9.gem
+gem install ./invoicetronic_sdk-1.11.gem
 ```
 
-(for development, run `gem install --dev ./invoicetronic_sdk-1.9.gem` to install the development dependencies)
+(for development, run `gem install --dev ./invoicetronic_sdk-1.11.gem` to install the development dependencies)
 
 or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
 
 Finally add this to the Gemfile:
 
-    gem 'invoicetronic_sdk', '~> 1.9'
+    gem 'invoicetronic_sdk', '~> 1.11'
 
 ### Install from Git
 
@@ -133,6 +133,12 @@ Class | Method | HTTP request | Description
 *Invoicetronic_Sdk::SendApi* | [**send_validate_xml_post**](docs/SendApi.md#send_validate_xml_post) | **POST** /send/validate/xml | Validate an invoice by xml
 *Invoicetronic_Sdk::SendApi* | [**send_xml_post**](docs/SendApi.md#send_xml_post) | **POST** /send/xml | Add an invoice by xml
 *Invoicetronic_Sdk::StatusApi* | [**status_get**](docs/StatusApi.md#status_get) | **GET** /status | Account status
+*Invoicetronic_Sdk::SubkeyApi* | [**subkey_get**](docs/SubkeyApi.md#subkey_get) | **GET** /subkey | List restricted keys
+*Invoicetronic_Sdk::SubkeyApi* | [**subkey_id_delete**](docs/SubkeyApi.md#subkey_id_delete) | **DELETE** /subkey/{id} | Delete a restricted key
+*Invoicetronic_Sdk::SubkeyApi* | [**subkey_id_get**](docs/SubkeyApi.md#subkey_id_get) | **GET** /subkey/{id} | Get a restricted key by id
+*Invoicetronic_Sdk::SubkeyApi* | [**subkey_id_roll_post**](docs/SubkeyApi.md#subkey_id_roll_post) | **POST** /subkey/{id}/roll | Roll the secrets of a restricted key
+*Invoicetronic_Sdk::SubkeyApi* | [**subkey_post**](docs/SubkeyApi.md#subkey_post) | **POST** /subkey | Add a restricted key
+*Invoicetronic_Sdk::SubkeyApi* | [**subkey_put**](docs/SubkeyApi.md#subkey_put) | **PUT** /subkey | Update a restricted key
 *Invoicetronic_Sdk::UpdateApi* | [**update_get**](docs/UpdateApi.md#update_get) | **GET** /update | List updates
 *Invoicetronic_Sdk::UpdateApi* | [**update_id_get**](docs/UpdateApi.md#update_id_get) | **GET** /update/{id} | Get an update by id
 *Invoicetronic_Sdk::WebhookApi* | [**webhook_get**](docs/WebhookApi.md#webhook_get) | **GET** /webhook | List webhooks
@@ -151,10 +157,15 @@ Class | Method | HTTP request | Description
  - [Invoicetronic_Sdk::Error](docs/Error.md)
  - [Invoicetronic_Sdk::Event](docs/Event.md)
  - [Invoicetronic_Sdk::ModelSend](docs/ModelSend.md)
+ - [Invoicetronic_Sdk::Permissions](docs/Permissions.md)
  - [Invoicetronic_Sdk::ProblemDetails](docs/ProblemDetails.md)
  - [Invoicetronic_Sdk::Receive](docs/Receive.md)
  - [Invoicetronic_Sdk::SendReduced](docs/SendReduced.md)
  - [Invoicetronic_Sdk::Status](docs/Status.md)
+ - [Invoicetronic_Sdk::SubKey](docs/SubKey.md)
+ - [Invoicetronic_Sdk::SubKeyRequest](docs/SubKeyRequest.md)
+ - [Invoicetronic_Sdk::SubKeyUpdate](docs/SubKeyUpdate.md)
+ - [Invoicetronic_Sdk::SubKeyWithSecrets](docs/SubKeyWithSecrets.md)
  - [Invoicetronic_Sdk::Update](docs/Update.md)
  - [Invoicetronic_Sdk::WebHook](docs/WebHook.md)
  - [Invoicetronic_Sdk::WebHookHistory](docs/WebHookHistory.md)

data/docs/CompanyApi.md

@@ -18,7 +18,7 @@ All URIs are relative to *http://localhost*
 
 List companies
 
-Retrieve a paginated list of companies. Results can be filtered by free-text search (`q`) across name, VAT number, and fiscal code.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.
+Retrieve a paginated list of companies. Results can be filtered by free-text search (`q`) across name, VAT number, and fiscal code.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  A company's `vat` and `fiscal_code` are unique platform-wide, not just within your account: incoming invoices are routed to their owner by VAT number alone, so a company belongs to one account at a time. Registering a company that is already active under another account is therefore not possible, and that account is not disclosed to you. Moving a company to your account is a transfer: contact support with the company's written authorization. 
 
 ### Examples
 
@@ -96,7 +96,7 @@ end
 
 Delete a company
 
-Delete a company by its internal id.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  **Warning:** Deleting a company will permanently remove all associated data, including sent invoices, received invoices, invoice updates from SDI, logs, and webhooks.  If the company has any linked invoices, you must explicitly confirm deletion by adding `?force=true` to the request. Without this parameter, the API will return `409 Conflict` with details about the linked data.
+Delete a company by its internal id.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  A company's `vat` and `fiscal_code` are unique platform-wide, not just within your account: incoming invoices are routed to their owner by VAT number alone, so a company belongs to one account at a time. Registering a company that is already active under another account is therefore not possible, and that account is not disclosed to you. Moving a company to your account is a transfer: contact support with the company's written authorization.   **Warning:** Deleting a company will permanently remove all associated data, including sent invoices, received invoices, invoice updates from SDI, logs, and webhooks.  If the company has any linked invoices, you must explicitly confirm deletion by adding `?force=true` to the request. Without this parameter, the API will return `409 Conflict` with details about the linked data.
 
 ### Examples
 
@@ -170,7 +170,7 @@ end
 
 Get a company by id
 
-Retrieve a company by its internal id.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.
+Retrieve a company by its internal id.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  A company's `vat` and `fiscal_code` are unique platform-wide, not just within your account: incoming invoices are routed to their owner by VAT number alone, so a company belongs to one account at a time. Registering a company that is already active under another account is therefore not possible, and that account is not disclosed to you. Moving a company to your account is a transfer: contact support with the company's written authorization. 
 
 ### Examples
 
@@ -240,7 +240,7 @@ end
 
 Add a company
 
-Add a new company.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.
+Add a new company.  When the company is already registered on the platform, the request fails with `400 Bad Request` and a problem details body whose `code` member is `company_already_registered`. Branch on `code`, not on `detail`, which is localized according to the `Accept-Language` header.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  A company's `vat` and `fiscal_code` are unique platform-wide, not just within your account: incoming invoices are routed to their owner by VAT number alone, so a company belongs to one account at a time. Registering a company that is already active under another account is therefore not possible, and that account is not disclosed to you. Moving a company to your account is a transfer: contact support with the company's written authorization. 
 
 ### Examples
 
@@ -301,7 +301,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: application/json
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## company_put
@@ -310,7 +310,7 @@ end
 
 Update a company
 
-Update an existing company.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.
+Update an existing company.  Changing `vat` or `fiscal_code` to a value already registered on the platform fails with `400 Bad Request` and `code` = `company_already_registered`.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  A company's `vat` and `fiscal_code` are unique platform-wide, not just within your account: incoming invoices are routed to their owner by VAT number alone, so a company belongs to one account at a time. Registering a company that is already active under another account is therefore not possible, and that account is not disclosed to you. Moving a company to your account is a transfer: contact support with the company's written authorization. 
 
 ### Examples
 
@@ -371,7 +371,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: application/json
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## company_vat_get
@@ -380,7 +380,7 @@ end
 
 Get a company by vat number
 
-Retrieve a company by its VAT number.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.
+Retrieve a company by its VAT number.  **Companies** are the entities that send and receive invoices. They are automatically created from invoice data when invoices are sent or received.  A company's `vat` and `fiscal_code` are unique platform-wide, not just within your account: incoming invoices are routed to their owner by VAT number alone, so a company belongs to one account at a time. Registering a company that is already active under another account is therefore not possible, and that account is not disclosed to you. Moving a company to your account is a transfer: contact support with the company's written authorization. 
 
 ### Examples
 

data/docs/Permissions.md

@@ -0,0 +1,34 @@
+# Invoicetronic_Sdk::Permissions
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **company** | **String** | Companies: `Read` lists and reads them, `Write` also creates, updates and deletes them. | [optional] |
+| **_send** | **String** | Outgoing invoices: `Read` lists and reads them, `Write` also sends and validates invoices. | [optional] |
+| **receive** | **String** | Incoming invoices: `Read` lists and reads them, `Write` also deletes them. | [optional] |
+| **webhook** | **String** | Webhooks: `Read` lists and reads them, `Write` also creates, updates and deletes them. | [optional] |
+| **update** | **String** | SDI status updates of outgoing invoices. | [optional] |
+| **log** | **String** | Event log. | [optional] |
+| **webhookhistory** | **String** | Webhook delivery history. | [optional] |
+| **export** | **String** | Invoice export. | [optional] |
+| **status** | **String** | Account status (remaining operations and signatures). | [optional] |
+
+## Example
+
+```ruby
+require 'invoicetronic_sdk'
+
+instance = Invoicetronic_Sdk::Permissions.new(
+  company: null,
+  _send: null,
+  receive: null,
+  webhook: null,
+  update: null,
+  log: null,
+  webhookhistory: null,
+  export: null,
+  status: null
+)
+```
+

data/docs/ReceiveApi.md

@@ -113,7 +113,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: Not defined
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## receive_id_delete
@@ -257,7 +257,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: Not defined
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## receive_id_payload_get

data/docs/SendApi.md

@@ -24,7 +24,7 @@ All URIs are relative to *http://localhost*
 
 Add an invoice by file
 
-Add a new invoice by uploading a file. Supported formats are XML (FatturaPA) and P7M (signed). The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
+Add a new invoice by uploading a file. Supported formats are XML (FatturaPA) and P7M (signed). The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. A replayed response carries the `Idempotent-Replayed: true` header, so you can tell it apart from a freshly processed one. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
 
 ### Examples
 
@@ -43,7 +43,7 @@ file = File.new('/path/to/some/file') # File |
 opts = {
   validate: true, # Boolean | Validate the document first, and reject it on failure.
   signature: 'None', # String | Whether to digitally sign the document.
-  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice.
+  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header.
 }
 
 begin
@@ -80,7 +80,7 @@ end
 | **file** | **File** |  |  |
 | **validate** | **Boolean** | Validate the document first, and reject it on failure. | [optional][default to false] |
 | **signature** | **String** | Whether to digitally sign the document. | [optional][default to 'Auto'] |
-| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. | [optional] |
+| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header. | [optional] |
 
 ### Return type
 
@@ -93,7 +93,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: multipart/form-data
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_get
@@ -427,7 +427,7 @@ end
 
 Add an invoice by json
 
-Add a new invoice using a FatturaPA JSON representation. Property names mirror the FatturaPA XML schema (PascalCase, e.g. `FatturaElettronicaHeader`). The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
+Add a new invoice using a FatturaPA JSON representation. Property names mirror the FatturaPA XML schema (PascalCase, e.g. `FatturaElettronicaHeader`). The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. A replayed response carries the `Idempotent-Replayed: true` header, so you can tell it apart from a freshly processed one. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
 
 ### Examples
 
@@ -446,7 +446,7 @@ body = { ... } # Object |
 opts = {
   validate: true, # Boolean | Validate the document first, and reject it on failure.
   signature: 'None', # String | Whether to digitally sign the document.
-  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice.
+  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header.
 }
 
 begin
@@ -483,7 +483,7 @@ end
 | **body** | **Object** |  |  |
 | **validate** | **Boolean** | Validate the document first, and reject it on failure. | [optional][default to false] |
 | **signature** | **String** | Whether to digitally sign the document. | [optional][default to 'Auto'] |
-| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. | [optional] |
+| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header. | [optional] |
 
 ### Return type
 
@@ -496,7 +496,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: application/json
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_post
@@ -505,7 +505,7 @@ end
 
 Add an invoice
 
-Add a new invoice using a structured Send object. The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
+Add a new invoice using a structured Send object. The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. A replayed response carries the `Idempotent-Replayed: true` header, so you can tell it apart from a freshly processed one. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
 
 ### Examples
 
@@ -524,7 +524,7 @@ model_send = Invoicetronic_Sdk::ModelSend.new({payload: 'PD94bWwgdmVyc2lvbj0iMS4
 opts = {
   validate: true, # Boolean | Validate the document first, and reject it on failure.
   signature: 'None', # String | Whether to digitally sign the document.
-  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice.
+  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header.
 }
 
 begin
@@ -561,7 +561,7 @@ end
 | **model_send** | [**ModelSend**](ModelSend.md) |  |  |
 | **validate** | **Boolean** | Validate the document first, and reject it on failure. | [optional][default to false] |
 | **signature** | **String** | Whether to digitally sign the document. | [optional][default to 'Auto'] |
-| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. | [optional] |
+| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header. | [optional] |
 
 ### Return type
 
@@ -574,7 +574,7 @@ end
 ### HTTP request headers
 
 - **Content-Type**: application/json
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_validate_file_post
@@ -643,7 +643,7 @@ nil (empty response body)
 ### HTTP request headers
 
 - **Content-Type**: multipart/form-data
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_validate_json_post
@@ -712,7 +712,7 @@ nil (empty response body)
 ### HTTP request headers
 
 - **Content-Type**: application/json
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_validate_post
@@ -781,7 +781,7 @@ nil (empty response body)
 ### HTTP request headers
 
 - **Content-Type**: application/json
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_validate_xml_post
@@ -850,7 +850,7 @@ nil (empty response body)
 ### HTTP request headers
 
 - **Content-Type**: application/xml
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 
 
 ## send_xml_post
@@ -859,7 +859,7 @@ nil (empty response body)
 
 Add an invoice by xml
 
-Add a new invoice using a raw XML document in FatturaPA format. The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
+Add a new invoice using a raw XML document in FatturaPA format. The invoice will be signed (if requested), validated (if requested), and queued for delivery to SDI. Status updates from SDI will be available in the `update` endpoint.  **Send** invoices are outbound sales invoices transmitted to customers through Italy's SDI (Sistema di Interscambio). Preserved for two years in the live environment and 15 days in the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).  You can also upload invoices via the [Dashboard](https://dashboard.invoicetronic.com).  ### Idempotency  To protect against duplicate submissions caused by network retries, you can send an optional `Idempotency-Key` header with any unique, client-generated value (up to 255 characters).  - The first request with a given key is processed normally, and its response (status, body and `Location`) is stored for 24 hours. - Any subsequent request that reuses the same key within that window replays the original response instead of sending a second invoice to SDI. A replayed response carries the `Idempotent-Replayed: true` header, so you can tell it apart from a freshly processed one. - If a request with the same key is still being processed, the retry receives `409 Conflict`. - If the same key is reused with a **different** invoice payload, the request is rejected with `422 Unprocessable Entity`: a given key must always map to the same request.  Keys are scoped per account, so different accounts can use the same key value without interfering. If the idempotency store is temporarily unavailable, the request is processed normally without idempotency protection.
 
 ### Examples
 
@@ -878,7 +878,7 @@ body = { ... } # Object |
 opts = {
   validate: true, # Boolean | Validate the document first, and reject it on failure.
   signature: 'None', # String | Whether to digitally sign the document.
-  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice.
+  idempotency_key: 'idempotency_key_example' # String | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header.
 }
 
 begin
@@ -915,7 +915,7 @@ end
 | **body** | **Object** |  |  |
 | **validate** | **Boolean** | Validate the document first, and reject it on failure. | [optional][default to false] |
 | **signature** | **String** | Whether to digitally sign the document. | [optional][default to 'Auto'] |
-| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. | [optional] |
+| **idempotency_key** | **String** | Optional client-generated key that makes the submission idempotent. Retrying the same request with the same key within 24 hours returns the original response instead of creating a duplicate invoice. A replayed response carries the `Idempotent-Replayed: true` header. | [optional] |
 
 ### Return type
 
@@ -928,5 +928,5 @@ end
 ### HTTP request headers
 
 - **Content-Type**: application/xml
-- **Accept**: application/json
+- **Accept**: application/json, application/problem+json
 

data/docs/StatusApi.md

@@ -13,7 +13,7 @@ All URIs are relative to *http://localhost*
 
 Account status
 
-Retrieve the number of operations (invoices + validations) and signatures left on your account.  When `signature_left` is 0, you will receive a `403 Forbidden` response when trying to sign an invoice. Likewise, if `operation_left` is 0, you will receive a `403 Forbidden` response when storing or validating an invoice.  You can also check your account status from the [Dashboard](https://dashboard.invoicetronic.com), where you can purchase additional operations and/or signatures.  **Please note** that these values are not enforced if you are on the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).
+Retrieve the number of operations (invoices + validations) and signatures left on your account.  When `signature_left` is 0, you will receive a `403 Forbidden` response when trying to sign an invoice. Likewise, if `operation_left` is 0, you will receive a `403 Forbidden` response when storing or validating an invoice.  These responses carry a problem details body whose `code` member tells them apart from other `403 Forbidden` responses: `usage_limit_exceeded` when you are out of operations, `signature_limit_exceeded` when you are out of signatures. Branch on `code`, not on `detail`, which is localized according to the `Accept-Language` header.  You can also check your account status from the [Dashboard](https://dashboard.invoicetronic.com), where you can purchase additional operations and/or signatures.  **Please note** that these values are not enforced if you are on the [Sandbox](https://invoicetronic.com/en/docs/sandbox/).
 
 ### Examples
 

data/docs/SubKey.md

@@ -0,0 +1,34 @@
+# Invoicetronic_Sdk::SubKey
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **Integer** | Unique identifier. | [optional] |
+| **created** | **Time** | Creation date. | [optional][readonly] |
+| **version** | **Integer** | Row version, for optimistic concurrency. | [optional][readonly] |
+| **description** | **String** | Human-readable label. | [optional] |
+| **active** | **Boolean** | Whether the key can authenticate. | [optional] |
+| **permissions** | [**Permissions**](Permissions.md) |  | [optional] |
+| **company_ids** | **Array<Integer>** | Companies the key can access. Empty means all the companies of the account. | [optional] |
+| **cors_origins** | **Array<String>** | Browser origins allowed to call the API with this key (CORS). | [optional] |
+| **previous_key_expires_at** | **Time** | When the secrets replaced by the last roll stop working; null when there are none still valid. | [optional] |
+
+## Example
+
+```ruby
+require 'invoicetronic_sdk'
+
+instance = Invoicetronic_Sdk::SubKey.new(
+  id: null,
+  created: null,
+  version: null,
+  description: null,
+  active: null,
+  permissions: null,
+  company_ids: null,
+  cors_origins: null,
+  previous_key_expires_at: null
+)
+```
+

data/docs/SubKeyRequest.md

@@ -0,0 +1,26 @@
+# Invoicetronic_Sdk::SubKeyRequest
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **description** | **String** | Human-readable label, e.g. the name of the tenant the key is for. |  |
+| **active** | **Boolean** | Whether the key can authenticate. Defaults to true. | [optional] |
+| **permissions** | [**Permissions**](Permissions.md) |  | [optional] |
+| **company_ids** | **Array<Integer>** | Companies the key can access. When omitted or empty, the key can access all the companies of the account, including the ones created later. | [optional] |
+| **cors_origins** | **Array<String>** | Browser origins allowed to call the API with this key (CORS), e.g. `https://app.example.com` or `*.example.com`. A key used from a browser is public: keep its permissions and companies minimal. | [optional] |
+
+## Example
+
+```ruby
+require 'invoicetronic_sdk'
+
+instance = Invoicetronic_Sdk::SubKeyRequest.new(
+  description: Studio Rossi Srl,
+  active: null,
+  permissions: null,
+  company_ids: null,
+  cors_origins: null
+)
+```
+

data/docs/SubKeyUpdate.md

@@ -0,0 +1,30 @@
+# Invoicetronic_Sdk::SubKeyUpdate
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **description** | **String** | Human-readable label, e.g. the name of the tenant the key is for. |  |
+| **active** | **Boolean** | Whether the key can authenticate. Defaults to true. | [optional] |
+| **permissions** | [**Permissions**](Permissions.md) |  | [optional] |
+| **company_ids** | **Array<Integer>** | Companies the key can access. When omitted or empty, the key can access all the companies of the account, including the ones created later. | [optional] |
+| **cors_origins** | **Array<String>** | Browser origins allowed to call the API with this key (CORS), e.g. `https://app.example.com` or `*.example.com`. A key used from a browser is public: keep its permissions and companies minimal. | [optional] |
+| **id** | **Integer** | Id of the restricted key to update. | [optional] |
+| **version** | **Integer** | Row version read with the key, for optimistic concurrency: a stale version fails with 422. | [optional] |
+
+## Example
+
+```ruby
+require 'invoicetronic_sdk'
+
+instance = Invoicetronic_Sdk::SubKeyUpdate.new(
+  description: Studio Rossi Srl,
+  active: null,
+  permissions: null,
+  company_ids: null,
+  cors_origins: null,
+  id: null,
+  version: null
+)
+```
+

data/docs/SubKeyWithSecrets.md

@@ -0,0 +1,38 @@
+# Invoicetronic_Sdk::SubKeyWithSecrets
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **id** | **Integer** | Unique identifier. | [optional] |
+| **created** | **Time** | Creation date. | [optional][readonly] |
+| **version** | **Integer** | Row version, for optimistic concurrency. | [optional][readonly] |
+| **description** | **String** | Human-readable label. | [optional] |
+| **active** | **Boolean** | Whether the key can authenticate. | [optional] |
+| **permissions** | [**Permissions**](Permissions.md) |  | [optional] |
+| **company_ids** | **Array<Integer>** | Companies the key can access. Empty means all the companies of the account. | [optional] |
+| **cors_origins** | **Array<String>** | Browser origins allowed to call the API with this key (CORS). | [optional] |
+| **previous_key_expires_at** | **Time** | When the secrets replaced by the last roll stop working; null when there are none still valid. | [optional] |
+| **test_key** | **String** | Sandbox secret. | [optional] |
+| **live_key** | **String** | Production secret. | [optional] |
+
+## Example
+
+```ruby
+require 'invoicetronic_sdk'
+
+instance = Invoicetronic_Sdk::SubKeyWithSecrets.new(
+  id: null,
+  created: null,
+  version: null,
+  description: null,
+  active: null,
+  permissions: null,
+  company_ids: null,
+  cors_origins: null,
+  previous_key_expires_at: null,
+  test_key: null,
+  live_key: null
+)
+```
+