Skip to main content

Retrieve Process and Attachments

GET /attachments

This service allows you to retrieve the attachments uploaded by signers within a process. The response structure varies depending on whether the userId parameter is included.


Authentication

Include your public key in the Authorization header.

Authorization: puk_xxx...

Query Parameters

NameTypeRequiredDescription
packagestringConditionalID of the process package. Required if code is not provided.
codestringConditionalDocument code of the process. Required if package is not provided.
userIdstringOptionalID of the user to retrieve individual attachments and status.

⚠️ Exactly one of package or code must be sent. If both are provided, the request is rejected with a 400 error.


Valid Usage Combinations

MethodPathDescription
GET/attachments?package={packageId}General process query
GET/attachments?code={code}General process query
GET/attachments?package={packageId}&userId={userId}Query attachments by signer using package
GET/attachments?code={code}&userId={userId}Query attachments by signer using code

🧪 Usage Examples

tip

You can copy any of the examples depending on your preferred language.

🔹 Get general process information

curl --location 'https://api.auco.ai/v1.5/ext/attachments?package=package123' \
--header 'Authorization: puk_yourPublicKey'

🔸 Get signer attachments using package and userId

curl --location 'https://api.auco.ai/v1.5/ext/attachments?package=package456&userId=userX' \
--header 'Authorization: puk_yourPublicKey'

🔸 Get signer attachments using code and userId

curl --location 'https://api.auco.ai/v1.5/ext/attachments?code=codeABC&userId=userY' \
--header 'Authorization: puk_yourPublicKey'

📥 Response Examples

🔹 Without userId

{
"package": "package123",
"name": "Signing Process 001",
"finish": true,
"signers": [
{
"userId": "01",
"email": "user1@example.com",
"name": "User One"
}
]
}

🔸 With userId

{
"package": "package123",
"name": "Signing Process 001",
"finish": true,
"signer": {
"userId": "01",
"email": "user1@example.com",
"name": "User One",
"files": [
{
"name": "ID Document",
"url": "https://..."
},
{
"name": "Proof",
"url": "https://..."
}
],
"status": "approved"
}
}

🔄 Signer Status (status)

StatusDescription
pendingThe user has not uploaded any documents yet.
uploadedThe user has uploaded documents, but they have not been approved yet.
approvedAll documents have been uploaded and approved.

File URLs (url) are only included if the status is not pending. They are temporary signed URLs valid for 5 minutes (300 seconds); once expired, call the endpoint again to obtain fresh links.


🔚 Field finish

The finish: true field means the process has been fully completed and no further actions are expected.


⚠️ Error Responses

CodeDescription
400Missing package or code, or process not found (ATTACHMENT_NOT_FOUND)
401Invalid or missing authentication