401 Unauthorized /invoices/reporting/single

[jawadzahoor72]

Hi,
I am using sandbox account and testing apis using postman
https://gw-fatoora.zatca.gov.sa/e-invoicing/developer-portal/compliance this API is working fine with CSR in body and gives me successful response including requestID,binarySecurityToken,secret and etc

now when I am trying to use
https://gw-fatoora.zatca.gov.sa/e-invoicing/developer-portal/invoices/reporting/single
binarySecurityToken as Username in Basic Auth
secret as Password in Basic Auth

response is 401 Unauthorized

[fuadhasni]

This is a loooong standing bug in developer portal. It uses a hard coded production certificate I believe. You can only check reporting / clearance API either with simulation mode of production or the production itself.

[jawadzahoor72]

@fuadhasni
thanks

[tifa-show]

Hi,
I'm trying to call the reporting API from the simulation environment put also give me 401 unauthorized too. please help me

[fuadhasni]

What’s the process you are doin before calling Reporting API? Were you able to create a production certificate in simulation environment?

…

On Mon, 3 Jul 2023 at 17:04, Mustafa ***@***.***> wrote: Hi, I'm trying to call the reporting API from the simulation environment put also give me 401 unauthorized too. please help me — Reply to this email directly, view it on GitHub <#42 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPK2CNKDHSOHGVA4F74H33XOKYNDANCNFSM6AAAAAAZJEN5AQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[wasimriaz]

Hi Fuadhasni,
From https://gw-apic-gov.gazt.gov.sa/e-invoicing/developer-portal'
I am able to call 'compliance' api and then able to call 'compliance/invoices' for compliance checks.

From https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal'
I am able to call 'compliance' api BUT am not able to call 'compliance/invoices' API. I get the message 'Unauthorized'.
Can you guide me what can be wrong ?

[fuadhasni]

Hi. both urls are same. what’s the difference?

…

On Sun, Dec 31, 2023 at 2:41 AM, wasimriaz ***@***.***> wrote: Hi Fuadhasni, *From https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal <https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal>'* I am able do call 'compliance' api and then able to call 'compliance/invoices' for compliance checks. *From https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal <https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal>'* I am able to call 'compliance' api BUT am not able to call 'compliance/invoices' api Can you guide me what can be wrong ? — Reply to this email directly, view it on GitHub <#42 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPK2CIKZ3NQTVI3XWQIUE3YMCDBPAVCNFSM6AAAAAAZJEN5ASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGYYTEMJWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[wasimriaz]

It says Authentication error.... If you could help me in this understanding ? Regards.

________________________________ From: Fuad ***@***.***> Sent: Sunday, December 31, 2023 8:27 AM To: wes4m/zatca-xml-js ***@***.***> Cc: wasimriaz ***@***.***>; Comment ***@***.***> Subject: Re: [wes4m/zatca-xml-js] 401 Unauthorized /invoices/reporting/single (Issue #42) Hi. both urls are same. what’s the difference?

On Sun, Dec 31, 2023 at 2:41 AM, wasimriaz ***@***.***> wrote: Hi Fuadhasni, *From https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal <https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal>'* I am able do call 'compliance' api and then able to call 'compliance/invoices' for compliance checks. *From https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal <https://gw-fatoora.zatca.gov.sa/e-invoice/developer-portal>'* I am able to call 'compliance' api BUT am not able to call 'compliance/invoices' api Can you guide me what can be wrong ? — Reply to this email directly, view it on GitHub <#42 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPK2CIKZ3NQTVI3XWQIUE3YMCDBPAVCNFSM6AAAAAAZJEN5ASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGYYTEMJWGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#42 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMJBNAYOI3622VI6NPYHRWTYMEOXVAVCNFSM6AAAAAAZJEN5ASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSHA2DSMRZGA>. You are receiving this because you commented.Message ID: ***@***.***>