Get Signed File

API reference

curl -X GET "https://__mock__/esign/v1/esign/get/signed-file/"

{
  "s3_url": "string",
  "success": true
}

{
  "detail": {},
  "message": "string"
}

{
  "detail": {},
  "message": "string"
}

{
  "error": "string"
}

Overview

Call GET /esign/v1/esign/get/signed-file/{txn_id} from your backend with Authorization: Bearer <token> after the user has finished the flow started from Send Request. Replace {txn_id} with the transaction id your integration receives for that signing job.

On 200 OK, read s3_url (HTTPS URL string) and success. Treat s3_url as opaque and sensitive; download server-side and stream to your vault.

Key features

• Artifact retrieval without embedding long-lived public URLs in clients.
• Boolean success flag for quick branching.

Implementation

Step 1: Call from your backend

GET /esign/v1/esign/get/signed-file/<txn_id> HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>

Step 2: Download the PDF

Fetch s3_url immediately; URLs may expire.

Error handling

Security notes

• Do not return s3_url to anonymous users; bind to your authenticated session.

Benefits

• Clean handoff from hosted signing to durable storage.

Next steps

• Send Request
• Verification API index