starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

[GH-ISSUE #1745] Getting an issue on load of document #503

New issue

Closed

opened 2026-02-26 18:47:19 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 18:47:19 +03:00

Owner

Originally created by @krupali-clavier on GitHub (Apr 14, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1745

Issue Description

I'm using V1 to implement document service in our system with apis
When I create document with console using template it works well
but When I create document with apis which is having an endpoint api/v1/documents with base url of https://app.documenso.com/ it's getting an issue on click of the URL which is being sent on recipient's mail

Steps to Reproduce

No response

Expected Behavior

It should load document on click of link which is being sent to recipient's email address

Current Behavior

It's getting an issue on load of document

I've checked in network

<Error

<Code

NoSuchKey
</Code

<Message

The specified key does not exist.
</Message

<Key

2mn712jxi0jj/document-for-test.pdf
</Key

<RequestId

05K0YPNNGF0P3686
</RequestId

<HostId

4xcuDbM3eawfkfNlGpjQN3qjXdQbj3jIpOHiLXavy7napeG4ZG5RYMHHEqKi5GAE7ttQnqp87IrEoPszRBCtLg==
</HostId

Screenshots (optional)

Operating System [e.g., Windows 10]

MacBook

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @krupali-clavier on GitHub (Apr 14, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1745 ### Issue Description I'm using V1 to implement document service in our system with apis When I create document with console using template it works well but When I create document with apis which is having an endpoint api/v1/documents with base url of https://app.documenso.com/ it's getting an issue on click of the URL which is being sent on recipient's mail ### Steps to Reproduce _No response_ ### Expected Behavior It should load document on click of link which is being sent to recipient's email address ### Current Behavior It's getting an issue on load of document I've checked in network <Error > <Code > NoSuchKey </Code > <Message > The specified key does not exist. </Message > <Key > 2mn712jxi0jj/document-for-test.pdf </Key > <RequestId > 05K0YPNNGF0P3686 </RequestId > <HostId > 4xcuDbM3eawfkfNlGpjQN3qjXdQbj3jIpOHiLXavy7napeG4ZG5RYMHHEqKi5GAE7ttQnqp87IrEoPszRBCtLg== </HostId > </Error> ### Screenshots (optional) <img width="1470" alt="Image" src="https://github.com/user-attachments/assets/5122805b-97c5-447c-b34a-b47350b99aef" /> ### Operating System [e.g., Windows 10] MacBook ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [ ] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [x] I have included any relevant screenshots. - [ ] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:19 +03:00

closed this issue
added the
Stale

status: triage
labels

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 14, 2025):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Apr 14, 2025): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:47:20 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

The issue occurs because the Documenso API requires a two-step process for document creation, and the second step (uploading the PDF) is being skipped.

When you create a document via the console/web interface, the PDF is uploaded automatically, when using the API, you must manually upload the PDF to the presigned URL. If you skip the upload step, the database has a document record but S3 doesn't have the actual PDF file. This causes the "NoSuchKey" error when recipients try to view the document

Step 1: Create Document

POST /api/v1/documents

This returns:

uploadUrl - A presigned S3 URL for uploading your PDF
documentId - The ID of the created document
recipients - Recipient information with signing URLs

Step 2: Upload PDF (REQUIRED - This step is being missed)

PUT {uploadUrl}
Content-Type: application/pdf
Body: [Your PDF file binary data]

@ephraimduncan commented on GitHub (Aug 23, 2025): The issue occurs because the Documenso API requires a **two-step process** for document creation, and the second step (uploading the PDF) is being skipped. When you create a document via the console/web interface, the PDF is uploaded automatically, when using the API, you must manually upload the PDF to the presigned URL. If you skip the upload step, the database has a document record but S3 doesn't have the actual PDF file. This causes the "NoSuchKey" error when recipients try to view the document #### Step 1: Create Document ```bash POST /api/v1/documents ``` This returns: - `uploadUrl` - A presigned S3 URL for uploading your PDF - `documentId` - The ID of the created document - `recipients` - Recipient information with signing URLs #### Step 2: Upload PDF (REQUIRED - This step is being missed) ```bash PUT {uploadUrl} Content-Type: application/pdf Body: [Your PDF file binary data] ```

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#503

No description provided.

Rows
Columns