19.05.2026
07:55
Hi everyone,
I’m facing a challenge when calling a REST API from WEBCON and I’m hoping someone has encountered something similar.
The API expects the payload in the following format:
{
"InterchangeToken": "NEWABC123",
"SupplierInvoiceCheck": {
"SupplierCode": "string",
"SupplierDocumentNumber": "string",
"SupplierDocumentDate": "2026-05-18T16:22:35.392Z",
"InvoiceEntityType": "PassiveInvoice",
"TotalTaxableAmountToCheck": 0,
"TotalInvoiceAmount": 0,
"ChangeRate": 0,
"TaxableIRPFAmount": 0,
"TotalIRPFAmount": 0,
"IsBlocked": true,
"ReversalDocumentNumber": "string",
"ReversalDocumentDate": "2026-05-18T16:22:35.392Z",
"AccountingRegistrationDate": "2026-05-18T16:22:35.392Z",
"AccountingMovementYear": 0,
"AccountingMovementNumber": 0,
"AccountingMovementID": "string",
"CreatedByUserID": "string",
"AssignmentByUserID": "string",
"BranchCode": "stri",
"CurrencyCode": "EUR",
"IRPFCode": "string",
"PaymentTermCode": "str",
"AccountingReasonCode": "string"
},
"DocumentAttachments": [
{
"DocumentContentExtension": ".PDF",
"DocumentContent": "",
"DocumentDescription": "",
"DocumentNumber": "",
"DocumentDate": "",
"DocumentType": "string"
}
]
}
Everything works fine until I need to send more than one document in DocumentAttachments.
The issue is with DocumentContent, which is expected to be a Base64 string. No matter which approach I try, WEBCON escapes forward slashes (/) into escaped slashes (\/) in the JSON payload, which causes the receiving API to reject the request.
I’ve already tried multiple approaches:
- Direct SQL query
- Business Rule
- Populating a technical field
- Storing attachment data in an item list
- Building the JSON in different ways
In all cases, the same escaping happens.
Has anyone dealt with this before or found a workaround using out-of-the-box WEBCON functionality? Ideally, I’d like to avoid using PowerShell or a custom intermediary service, although PowerShell is still an option if there’s no clean alternative.
Any ideas would be greatly appreciated.
