starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #2098] API Keys for FormBuilding and Signatures that are Scoped per Document #601

New issue

Closed

opened 2026-02-26 18:47:45 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @schmitch on GitHub (Oct 24, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2098

Feature Description

Currently the API Keys are only for the whole "Tenant" and when creating a token for the form builder and the signing process it's not possible with:

https://openapi.documenso.com/reference#tag/embedding/POST/embedding/create-presign-token

to either say it should only be used for signing or for form building. and it's not possible to scope the token to a specific document.

Use Case

currently when embedding the form builder or signign process it should be possible to have a token only for either of them and to have a token that will be only usable for a specific document.

Proposed Solution

There is a competitor that allows to set some things in the signing/form-builder api token:
https://www.docuseal.com/docs/embedded/builder#javascript.data-token

instead of https://openapi.documenso.com/reference#tag/embedding/POST/embedding/create-presign-token where I can only set the expiresIn it should be possible to say that I can also set a documentId and that the token can only be used for signing or for document building.

currently the api flow would than be like that:

upload a document via api
create a form builder token with the provided documentId
integrate the form builder and save the formular
create a signing token with the provided documentId
provide users with the signing form

Alternatives (optional)

No response

Additional Context

currently we will probably also drop a mail at https://documen.so/question-cta for a possible integration at this feature or if you don't want to work at something like this we would look into providing a PR on our side if that is wished.

Please check the boxes that apply to this feature request.

I have searched the existing feature requests to make sure this is not a duplicate.
I have provided a detailed description of the requested feature.
I have explained the use case or scenario for this feature.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.
I want to work on creating a PR for this issue if approved

Originally created by @schmitch on GitHub (Oct 24, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2098 ### Feature Description Currently the API Keys are only for the whole "Tenant" and when creating a token for the form builder and the signing process it's not possible with: https://openapi.documenso.com/reference#tag/embedding/POST/embedding/create-presign-token to either say it should only be used for signing or for form building. and it's not possible to scope the token to a specific document. ### Use Case currently when embedding the form builder or signign process it should be possible to have a token only for either of them and to have a token that will be only usable for a specific document. ### Proposed Solution There is a competitor that allows to set some things in the signing/form-builder api token: https://www.docuseal.com/docs/embedded/builder#javascript.data-token instead of https://openapi.documenso.com/reference#tag/embedding/POST/embedding/create-presign-token where I can only set the expiresIn it should be possible to say that I can also set a documentId and that the token can only be used for signing or for document building. currently the api flow would than be like that: 1. upload a document via api 2. create a form builder token with the provided documentId 3. integrate the form builder and save the formular 4. create a signing token with the provided documentId 5. provide users with the signing form ### Alternatives (optional) _No response_ ### Additional Context currently we will probably also drop a mail at https://documen.so/question-cta for a possible integration at this feature or if you don't want to work at something like this we would look into providing a PR on our side if that is wished. ### Please check the boxes that apply to this feature request. - [x] I have searched the existing feature requests to make sure this is not a duplicate. - [x] I have provided a detailed description of the requested feature. - [x] I have explained the use case or scenario for this feature. - [x] I have included any relevant technical details or design suggestions. - [x] I understand that this is a suggestion and that there is no guarantee of implementation. - [ ] I want to work on creating a PR for this issue if approved

kerem

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

closed this issue
added the
status: triage
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Oct 24, 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 (Oct 24, 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 referenced this issue

2026-02-26 19:31:43 +03:00

[PR #602] [CLOSED] fix(web): fix stale documents list by forcing refresh after uploading #1072

kerem referenced this issue

2026-02-26 19:31:46 +03:00

[PR #629] [CLOSED] fix: document listing not updating after uploading #1086

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#601

No description provided.

Rows
Columns