EInvoicing/V1/DocumentsApi/DownloadDocument adds a default accept of application/json. This seems to be invalid (at least in my use case for EInvoicing in Mexico). The documentation does suggests that valid Accept header values vary depending on mandate type.
API Response:
{
"error": 406,
"message": "Incorrect Accept Header error",
"supportedAcceptHeaders": [
"application/vnd.oasis.ubl+xml",
"application/xml",
"application/pdf",
"application/zip",
"application/png"
]
}
The endpoint enforces that the caller provides an Accept header value by returning an exception if it is absent. It seems that this value should be used as the header value exclusively.
DocumentsAPI.cs line:363
DocumentsAPI.cs line:439
EInvoicing/V1/DocumentsApi/DownloadDocument adds a default accept of
application/json. This seems to be invalid (at least in my use case for EInvoicing in Mexico). The documentation does suggests that valid Accept header values vary depending on mandate type.API Response:
The endpoint enforces that the caller provides an Accept header value by returning an exception if it is absent. It seems that this value should be used as the header value exclusively.
DocumentsAPI.cs line:363
DocumentsAPI.cs line:439