Get Signed Document

Endpoint Overview

GET /api/v1/esign/get-signed-document/{client_id}

Description

This API endpoint retrieves the download link for an electronically signed document associated with a specific client. It allows you to access the final signed document that was processed through the Surepass eSign service, enabling you to download, store, or share the legally binding document with relevant stakeholders.

Key Benefits

Instant access to legally binding signed documents

Secure document retrieval through authenticated API calls

Simplified document management workflow through programmatic access

Seamless integration with existing document storage systems

Use Cases

Financial Services

Real Estate

Insurance

Retrieve signed loan agreements for record-keeping and compliance

Access completed account opening documents for customer onboarding

Obtain signed investment advisory agreements for portfolio management

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token authentication using JWT format
Content-Type	Yes	Application/json

URL Parameters

Parameter	Type	Required	Description
client_id	String	Yes	The unique identifier of the client whose signed document is being requested

This endpoint does not require a request body.

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Container for the response data
data.url	String	Secure URL to download the signed document
status_code	Integer	HTTP status code indicating the result of the request
message_code	String	Short code indicating the outcome of the request
message	String	Human-readable description of the response
success	Boolean	Indicates whether the request was successful

Example Successful Response

{
    "data": {
        "url": "https://esign.s3.amazonaws.com/esign_Cdtsfgsfdgsfbsfnsfnsfnsfbsf"
    },
    "status_code": 200,
    "message_code": "success",
    "message": "Download link generated successfully",
    "success": true
}

Possible Error Responses

Invalid Client ID

Authentication Error

{
    "status_code": 404,
    "message_code": "not_found",
    "message": "No signed document found for the provided client ID",
    "success": false
}

This error occurs when the provided client_id does not match any records in the system.

Integration Best Practices

Security Recommendations

Store downloaded documents securely with appropriate access controls

Implement document expiration policies for downloaded files

Use HTTPS for all communications with the API

Rotate JWT tokens regularly and never hardcode them in client-side applications

User Experience Guidelines

Provide clear download options for users accessing the signed document

Implement proper error handling to guide users when documents are unavailable

Consider implementing document preview functionality before download

Include document metadata (date signed, parties involved) when presenting to users

Code Samples

cURL

Python

Node.js

Related APIs

Create eSign Request - Initiates the electronic signature process for documents

Get eSign Status - Checks the current status of an electronic signature request

Cancel eSign Request - Cancels a pending electronic signature request

Compliance and Legal Considerations

Electronic signatures obtained through this API are compliant with the Information Technology Act and equivalent electronic signature regulations. Documents retrieved through this API maintain their legal validity and can be used as evidence in legal proceedings. Ensure proper consent was obtained during the signing process and maintain appropriate records of the complete transaction.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

{ "data": { "url": "https://esign.s3.amazonaws.com/esign_Cdtsfgsfdgsfbsfnsfnsfnsfbsf" }, "status_code": 200, "message_code": "success", "message": "Download link generated successfully", "success": true }

Get Signed Document

Get Signed Document#

Description#

Use Cases#

Technical Implementation#

Request Headers#

URL Parameters#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

Get Signed Document

Description

Use Cases

Technical Implementation

Request Headers

URL Parameters

Response Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples