The Spanish version is the authoritative reference. View in Spanish
Nomination event
Nomination Event is the action of assigning a receiver to a previously selected electronic invoice using the selection checkboxes from the issued documents inbox.
To start a request for this method, take the following criteria into account:
| ChangeDocumentStatus for nomination (request) | |||||
|---|---|---|---|---|---|
| Parameter | Parameter type | Data type | Description | Allowed values | Length |
| countryDocumentId | String | Numeric | Country-level tax identifier of the document, also known as CUFE, CLAVE, UUID, ID | See the Country Document ID Structure table | 44 characters |
| status* | Integer | Numeric | Code of the event to generate. | 34 | 1-2 characters |
| description | String | Alphanumeric | Reason for the nomination. | Example: Authorized | 5-500 characters |
| receiverType* | String | Numeric | Nature of the receiver. | Examples: Taxpayer: 1 Non-taxpayer: 2 | 1 character |
| operationType* | String | Numeric | Type of transaction. | 1: B2B 2: B2C 4: B2F | 1 character |
| receiverCountry* | String | Alphanumeric | Receiver's country code. | According to the Country Coding XSD | 3 characters |
| receiverDocumentType* | String | Numeric | Receiver's identity document type. This field is required when receiverType = 2 | 1: Paraguayan ID card 2: Passport 3: Foreign ID card 4: Residency card 5: Diplomatic tax exemption card 9: Other | 1 character |
| receiverCode* | String | Alphanumeric | This field is required when receiverType = 2 | Identity document number. | 1-20 characters |
| receiverName* | String | Alphanumeric | Name or business name of the DTE receiver. | 4-255 characters | |
| receiverTypeTaxpayer | String | Numeric | Type of receiving taxpayer. This field is required when receiverType = 1 | 1: Natural Person 2: Legal Entity | 1 character |
| receiverCode | String | Alphanumeric | This field is required when receiverType = 1 | Receiver's RUC | 2-8 characters |
| receiverCodeDV | String | Numeric | This field is required when receiverType = 1 | Check digit of the receiver's RUC | 1 character |
| receiverFantasyName | String | Alphanumeric | Trade name. | 4-255 characters | |
| receiverAddress | String | Alphanumeric | Receiver's address | 1-255 characters | |
| receiverHouseNumber | String | Numeric | This field is required when receiverAddress is provided | Receiver's house number. | 1-6 characters |
| receiverDepartmentCode | String | Numeric | Receiver's department code. | According to the Departments XSD | 1-2 characters |
| receiverDepartmentName | String | Alphanumeric | Description of the receiver's department. | Corresponding to receiverDepartmentCode | 6-16 characters |
| receiverDistrictCode | String | Numeric | Receiver's district code. | 1-4 characters | |
| receiverDistrictName | String | Alphanumeric | Description of the receiver's district. | This field is required when receiverDistrictCode is provided | 1-30 characters |
| receiverCityCode | String | Numeric | Receiver's city code. | 1-5 characters | |
| receiverCityName | String | Alphanumeric | Description of the receiver's city. | Corresponding to receiverDepartmentCode | 1-30 characters |
| receiverPhone | String | Numeric | Receiver's phone number. | Must include the city prefix if receiverDepartmentCode = PRY | 6-15 characters |
| receiverCellPhone | String | Alphanumeric | Receiver's mobile number. | 10-20 characters | |
| receiverEmail | String | Alphanumeric | Receiver's email address. | 3-15 characters | |
| customerCode | String | Alphanumeric | Customer code. | 3-80 characters |
*Required
*Required
Request example

Note: Remember that before using the method, you must authenticate within the Authorization tab.
For this method we use the Params tab in Postman.
- Select the method type. In this case, you must select POST.
- Enter the method URL.
- Enter the parameters shown in the table above with their corresponding values.
- Click Send.
Response example
