Zatca Error for CLEARANCE_EINVOICE API

Dear Team,

We have been encountering an issue with the CLEARANCE_EINVOICE API provided by Zatca. Since last night, around 23:30 PM GMT, all responses from the API have been returning an HTML page with the title “Request Rejected.” Below is the complete response we are receiving:

<title> Request Rejected </title>
<link rel="shortcut icon"
    href="https://zatca.gov.sa//Style%20Library/GAZTinternet/img/favicons/apple-touch-icon.png"
    type="image/vnd.microsoft.icon" id="favicon" />

<style>
    /* Font-face rule to define the custom font */
    @font-face {
        font-family: 'Somar';
        src: url('fonts/Somar-Regular.eot');
        src: url('fonts/Somar-Regular.eot?') format('embedded-opentype'),
            url('fonts/Somar-Regular.woff2') format('woff2'),
            url('fonts/Somar-Regular.woff') format('woff'),
            url('fonts/Somar-Regular.ttf') format('truetype');
        font-weight: normal;
        font-style: normal;
        font-display: swap;
    }

    @font-

This issue is affecting all of our clients, and we can confirm that there have been no changes to the requests on our end. Due to our information security policy, we are unable to share the exact request details.

Do you have any information regarding this issue? Kindly assist here asap.

1 Like

@idaoud @Lina-alrehaili1 please check this on priority

Please address this issue with utmost urgency, as it has resulted in a blockade for all our clients, bringing their business operations to a standstill.

Dear @Soumya_48,

Thank you for reaching out and sharing the details of the issue you are encountering.

Please note that the CLEARANCE_EINVOICE API is functioning correctly on both production and simulation environments on our side. If the issue persists, kindly provide the following details via email to the SP support team (sp_support@zatca.gov.sa) by sharing the below asap for further investigation:

• The specific endpoint being used.

• Request headers (excluding authorizing header).

• The full API request including the response (in HTML For one of the infected invoice).

Once we have these details, we will investigate further to assist you. If you have additional concerns, please feel free to reach out.

Best regards,

We can see another thread where recommendation of the change is given.

Important Breaking Change (decommissioning gw-apic-gov.gazt.gov.sa) - Announcements - Fatoora Developer Community

the current error could be happening due to that?

Guys, we are facing the same issue as well, we are getting HTML response for some invoices, did anyone understand what is the issue?

Our Customers are also facing the same issue.

<title> Request Rejected </title>
<link rel="shortcut icon"
    href="https://zatca.gov.sa//Style%20Library/GAZTinternet/img/favicons/apple-touch-icon.png"
    type="image/vnd.microsoft.icon" id="favicon" />

<style>
    /* Font-face rule to define the custom font */
    @font-face {
        font-family: 'Somar';
        src: url('fonts/Somar-Regular.eot');
        src: url('fonts/Somar-Regular.eot?') format('embedded-opentype'),
            url('fonts/Somar-Regular.woff2') format('woff2'),
            url('fonts/Somar-Regular.woff') format('woff'),
            url('fonts/Somar-Regular.ttf') format('truetype');
        font-weight: normal;
        font-style: normal;
        font-display: swap;
    }

    @font-face {
        font-family: 'Somar';
        src: url('fonts/Somar-SemiBold.eot');
        src: url('fonts/Somar-SemiBold.eot') format('embedded-opentype'),
            url('fonts/Somar-SemiBold.woff2') format('woff2'),
            url('fonts/Somar-SemiBold.woff') format('woff'),
            url('fonts/Somar-SemiBold.ttf') format('truetype');
        font-weight: bold;
        font-style: normal;
        font-display: swap;
    }


    /* CSS styles */
    body {
        font-family: 'Somar', sans-serif !important;
        /* Custom font */
        margin: 0;
        padding: 0;
        background-color: #1D3761;

    }

    /* Start Helpers Classes */
    .container {
        max-width: 1022px;
        margin: auto;
    }

    .flex-reverse {
        flex-direction: row-reverse;
    }

    .dir-ar {
        direction: rtl;
    }

    /* End Helpers Classes */

    header {
        height: 100px;
    }

    header .logo img {
        height: 80px;
        max-width: 245px;
        margin: 10px 0;
    }

    .info {
        padding: 5rem 0;

    }

    .info h2 {
        font-size: 28px;
        color: #4FBBBD;

    }

    .info p {
        font-size: 16px;
        font-weight: 500;
        line-height: 28px;
        color: #fff;
    }

    .info p a {
        color: #63c3c4;
        text-decoration: none;
    }

    .info p a:hover {
        color: #0996D4;
        text-decoration: none;
    }

    .info hr {
        border: none;
        height: 2px;
        background-color: #fff;
        margin: 4rem 0;
    }


    .actions .submit-action {
        display: flex;
        flex-wrap: wrap;
        justify-content: space-between;
        padding: 10px 20px;
        align-items: center;
        font-size: 18px;
        font-weight: 500;
        margin-bottom: 50px;
        border-radius: 15px;
        background: linear-gradient(rgba(25, 87, 157, 0.2) 100%, rgba(24, 134, 196, 0.2) 100%)
    }

    .actions .submit-action p {
        color: #fff;
    }

    .actions .submit-action a {
        transition: all .3s ease-in-out;
        text-align: center;
        color: #fff;
        background-color: #0996D4;
        border: 1px solid transparent;
        width: 18%;
        padding: 10px 0;
        border-radius: 15px;
        text-decoration: none;
        font-weight: 700;
        display: inline-block;
        font-size: 16px;
    }


    .actions .submit-action a:hover {
        background-color: transparent;
        color: #fff;
        border-color: #fff;
    }

    /* Media queries for responsiveness */
    @media screen and (max-width: 1200px) {
        body {
            text-align: center;
        }

        .container {
            max-width: 460px;
            padding: 0 20px;
        }

        .info p a {
            display: block;
        }

        .actions .submit-action {
            justify-content: center;
        }

        .actions .submit-action p {
            font-size: .8em;
        }

        .actions .submit-action a {
            width: 40%;
            margin: auto;
            padding: 8px;
            font-size: .8em;
            margin-bottom: 10px;
        }
    }
</style>
zatca logo
            </a>
        </div>
    </div>
</header>
<section class="info">
    <div class="container">
        <h2>Sorry for inconvenience </h2>
        <p>Something went wrong in your request, please provide us with the used service information by sending the
            support ID #########################
                to the below page in ZATCA webpage : <br> <a
                    href="https://zatca.gov.sa/en/ContactUs/Pages/SuggestionComplaint.aspx#topic_Request"
                    target="_blank">Contact us >> Complaints and Suggestions >> Raise Request.</a>
        </p>

        <hr />
        <div class="dir-ar">
            <h2>نأسف للإزعاج</h2>
            <p>حدث خطأ في طلبك نرجو تزويدنا بمعلومات الخدمة المستخدمة عن طريق إرسال رقم الدعم
                ############################
                    عبر الدخول على الصفحة التالية في بوابة الهيئة: <br> <a
                        href="https://zatca.gov.sa/ar/ContactUs/Pages/SuggestionComplaint.aspx#topic_Request"
                        target="_blank">اتصل بنا >> الشكاوى والاقتراحات >> طلب.</a>
            </p>
        </div>
    </div>
</section>

Error With Some Support Number
Please address this issue with utmost urgency, as it has resulted in a blockade for all our clients, bringing their business operations to a standstill.

Dear @Ankit_Tiwari , any updates?

Dear @Ankit_Tiwari

is the issue occuring due to below thread?

Important Breaking Change (decommissioning gw-apic-gov.gazt.gov.sa) - Announcements - Fatoora Developer Community

Old API host url is already decommissioned?

Hi @Lina-alrehaili1 ,

Please note we have received the same HTML responses for REPORTING_EINVOICE API also so both the API’s are impacted.

@Lina-alrehaili1 @Ankit_Tiwari ,

We are currently utilizing the following endpoints for both reporting and clearance APIs:

Could you please confirm if there have been any changes to the aforementioned endpoints?

Still Error exists for Both Clearance and Reporting .
we are using End Point respectively
https://gw-fatoora.zatca.gov.sa/e-invoicing/core/invoices/clearance/single
https://gw-fatoora.zatca.gov.sa/e-invoicing/core/invoices/reporting/single

Dear @Ankit_Tiwari

Your URL changes mentioned, the change would happen in 1st quarter of 2025. Has the changes already been done and old url is decomissioned? Please let us know if you want to move to new URL. Please respond on urgent basis and businesses are stalled.

@Sachin.Pathare no, old URL is not decommissioned. Team is investigating on top priority basis. Please send detailed request, response and IP address on SP support email.

@idaoud @Lina-alrehaili1 @Ankit_Tiwari please guide and advise

Dear @Soumya_48 and All,

We have received multiple inquiries regarding the HTML response issue. Please note that the API is functioning correctly in both the production and simulation environments on our side.

To ensure proper connectivity, kindly verify that you are using the correct API gateway endpoint from the Fatoora portal. For example, please refer to the attached image for the correct API endpoint in the simulation environment.

If the issue persists, we kindly request you to provide the following details via email to the SP support team at sp_support@zatca.gov.sa for further investigation:
• The specific endpoint being used.
• Request headers (excluding the authorization header).
• The full API request, including the response (In HTML for one of the affected invoices).

Once we have these details, we will investigate further and provide the necessary support.

We appreciate your understanding and cooperation. Please feel free to reach out if you have any additional concerns or questions.

Best regards,

Dear @idaoud @Lina-alrehaili1 @Ankit_Tiwari it appears that Zatca team is addressed the issue. Thank you.

Kindly advise by when we should be doing URL changes safely?

@AsserMaany @Soumya_48 @muneeruc could you please check and confirm if the issue is resolved or not?

1 Like

Dears ,
@Ankit_Tiwari
We are facing also an error . this is the first time since we did the integration since 4 months :

Inner Exception: The request was aborted: Could not create SSL/TLS secure channel.

Any idea

We are using Microsoft Dynamics D365 F&O integration is working fine with this