You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 4, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: site/Getting-started.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ You will receive the fileId or UUID, store this data to create visible elements.
76
76
77
77
Get data of a specific file, you can use `file_id` or `uuid` on path, both data you will receive after request to `POST /request-signature`
78
78
79
-
The association between user and file will result on a `fileUserId`. You will need this to sign the document or define the page and coordinates of place that the signature of the user will be filled.
79
+
The association between user and file will result on a `signRequestId`. You will need this to sign the document or define the page and coordinates of place that the signature of the user will be filled.
80
80
81
81
```bash
82
82
curl --request GET \
@@ -113,14 +113,14 @@ curl --request POST \
113
113
"page": 1
114
114
},
115
115
"type": "signature",
116
-
"fileUserId": 51
116
+
"signRequestId": 51
117
117
}'
118
118
```
119
119
120
120
#### Update
121
121
PATCH /file/{uuid}/elements/{elementId}
122
122
123
-
The UUID you will receive when you will do a request to `POST /request-signature` and the `fileUserId` is the relation between an user and the file to sign. You can check the `fileUserId` doing a request to /validate
123
+
The UUID you will receive when you will do a request to `POST /request-signature` and the `signRequestId` is the relation between an user and the file to sign. You can check the `signRequestId` doing a request to /validate
0 commit comments