# Merge XFDF API giving \[502\] Internal error on merge request

**URL:** <https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716>\
**Category:** Technical Support\
**Created:** [July 18, 2023, 6:36am UTC](https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716 "2023-07-18T06:36:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanoop](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@sanoop](https://pdfjs.community/u/sanoop)\
**Post date:** [July 18, 2023, 6:36am UTC](https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716/1 "2023-07-18T06:36:05Z")

</div>

PDF.js Express Viewer  
version :6.3.4

 ![pdfjs](https://canada1.discourse-cdn.com/flex031/uploads/pdfjscommunity/original/2X/a/ad61bfb626285d932d4cabad027bb52bf304334f.jpeg)

[https://api.pdfjs.express/xfdf/merge](https://api.pdfjs.express/xfdf/merge) is getting 502 errors when sending requests to Merge XFDF. Please fix this issue as a priority.

```javascript
 var xfdf = await annotManager.exportAnnotations({ links: false, widgets: false });
                        var fileData = await docViewer.getDocument().getFileData({});
   
                        var data = new FormData();
                        data.append('xfdf', xfdf);
                        data.append('file',file_name);
                        data.append('license','');

                        // Process the file
                        var response = await fetch('https://api.pdfjs.express/xfdf/merge', {
                            method: 'post',
                            // mode: 'no-cors',
                            body: data
                        }).then(resp => resp.json());

                        var { url, key, id } = response;

                        // Download the file
                        var mergedFileBlob = await fetch(url, {
                            headers: {
                                Authorization: key
                            }
                        }).then(resp => resp.blob())

                        var data_PDF = new FormData();
                        data_PDF.append('data' , mergedFileBlob);

```

---

<div class="post-metadata">

**Author:** ![hoai.pham](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@hoai.pham](https://pdfjs.community/u/hoai.pham)\
**Post date:** [July 18, 2023, 9:03am UTC](https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716/3 "2023-07-18T09:03:42Z")

</div>

We had the same problem, still not resolved.

---

<div class="post-metadata">

**Author:** ![elvisdosreis](https://yyz1.discourse-cdn.com/flex031/user_avatar/pdfjs.community/elvisdosreis/32/311_2.png) [@elvisdosreis](https://pdfjs.community/u/elvisdosreis)\
**Post date:** [July 18, 2023, 2:05pm UTC](https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716/4 "2023-07-18T14:05:42Z")

</div>

I’ve been having the same problem for over 4 hours, do you have any predictions for a solution?  
I use the system commercially, I cannot take this kind of risk.

---

<div class="post-metadata">

**Author:** ![Bitbean](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@Bitbean](https://pdfjs.community/u/Bitbean)\
**Post date:** [July 18, 2023, 3:00pm UTC](https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716/5 "2023-07-18T15:00:08Z")

</div>

Same problem here as well. We’ve been encountering this issue for close to 24 hours by now. We use this API in production and a resolution is critical. Is there any timeframe for when this will be addressed?

---

<div class="post-metadata">

**Author:** ![tgordon](https://avatars.discourse-cdn.com/v4/letter/t/aca169/32.png) [@tgordon](https://pdfjs.community/u/tgordon)\
**Post date:** [July 18, 2023, 3:25pm UTC](https://pdfjs.community/t/merge-xfdf-api-giving-502-internal-error-on-merge-request/2716/6 "2023-07-18T15:25:35Z")

</div>

Hello,

Thank you for reaching out. We have discovered the source of the issue and it has been resolved. Please notify us if the issue persists.

Best regards,  
Tyler