HelloSign

HelloSign is a comprehensive electronic signature platform that enables businesses to send, sign, and manage documents digitally, providing secure document workflows, legal compliance features, and seamless integration capabilities to streamline contract management and approval processes.

Power end-to-end data operations for your HelloSign API with Nexla. Our bi-directional HelloSign connector is purpose-built for HelloSign, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to HelloSign or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your HelloSign workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a HelloSign credential, you need to obtain authentication credentials from your HelloSign account. HelloSign supports two authentication methods: API Key authentication and OAuth2 authentication.

For API Key authentication, you need to obtain an API key from your HelloSign account settings. The API key is used as the username in Basic authentication.

For OAuth2 authentication, you need to have a HelloSign account and create an OAuth2 application in your HelloSign account settings to obtain OAuth2 credentials (Client ID and Client Secret).

For detailed information about HelloSign API authentication and setup, refer to the HelloSign API authentication documentation.

Authenticate

Credentials required

Api Key

Field	Required	Secret	Description
API Key	Yes	Yes	Your API Key from API Settings page

OAuth2

Field	Required	Secret	Description
Client ID	Yes	Yes	HelloSign Client ID
Client Secret	Yes	Yes	HelloSign Client Secret for Token URL

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – HelloSign

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. HelloSign supports two authentication methods: API Key authentication and OAuth2 authentication. Choose the method that best suits your needs.

HelloSign Authentication Methods

API Key

API Key authentication uses your HelloSign API key as the username in Basic authentication. This is the simplest authentication method and is suitable for most use cases.

1. Enter your HelloSign API key in the **API Key** field. This is the API key you obtained from your HelloSign API Settings page. The API key is used as the username in Basic authentication for all API requests to the HelloSign API.

OAuth2

OAuth2 authentication provides secure access to your HelloSign account using industry-standard OAuth2 authorization. This method is recommended for applications that need to access HelloSign on behalf of users.

1. Enter your HelloSign Client ID in the **Client ID** field. This is the Client ID you obtained from your HelloSign OAuth2 application settings.
2. Enter your HelloSign Client Secret in the **Client Secret** field. This is the Client Secret you obtained from your HelloSign OAuth2 application settings.
3. Click the **Authorize** button to begin the OAuth2 authorization flow. This will redirect you to HelloSign's authorization page where you will be asked to sign in with your HelloSign account and grant permissions to Nexla.
4. After completing the OAuth2 authorization flow, Nexla will automatically obtain and store the access token and refresh token needed to authenticate API requests. The access token is used to authenticate each API request, and the refresh token is used to obtain new access tokens when the current access token expires.

For API Key authentication, you can obtain your API key from your HelloSign account in the API Settings page. The API key is used as the username in Basic authentication. For OAuth2 authentication, you need to create an OAuth2 application in your HelloSign account settings to obtain Client ID and Client Secret. OAuth2 access tokens expire after a certain period for security reasons. Nexla automatically refreshes expired access tokens using the refresh token, so you typically do not need to re-authorize unless you revoke access or the refresh token expires. For detailed information about HelloSign API authentication methods, see the HelloSign API authentication documentation.

4. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the HelloSign connector tile, then select the credential that will be used to connect to the HelloSign account, and click Next; or, create a new HelloSign credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common HelloSign endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Download files as Data URI

Obtain a copy of the current documents specified by the signature_request_id parameter.

• Enter the signature request ID you want to download files for in the Signature Request ID field. This should be the unique identifier for the signature request whose documents you want to retrieve.
• The endpoint uses GET requests to https://api.hellosign.com/v3/signature_request/files_as_data_uri/{signature_request_id} where {signature_request_id} is the Signature Request ID you provide. The endpoint URL is automatically constructed based on the HelloSign API base URL and the signature request ID.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $, which extracts the entire root-level object from the API response. The response contains the document files encoded as data URIs.

This endpoint retrieves a copy of the current documents for a specific signature request, with the files encoded as data URIs. Data URIs allow the document content to be embedded directly in the response as base64-encoded data. The signature request must exist in your HelloSign account, and you must have permission to access it. For detailed information about the API response format and available fields, see the HelloSign API documentation.

Get Signature Request List

Returns a list of SignatureRequests that you can access.

• Enter the account ID for which you want to retrieve signature requests in the Account ID field. This should be the account ID of the team member whose signature requests you want to retrieve. Use all to indicate all team members. The default value is all if not specified.
• The endpoint uses GET requests to https://api.hellosign.com/v3/signature_request/list?account_id={account_id} where {account_id} is the Account ID you provide. The endpoint URL is automatically constructed based on the HelloSign API base URL and the account ID query parameter.
• The endpoint uses incrementing page-based pagination (iteration.type: paging.incrementing) starting from page 1. The response data path is $.signature_requests[*], which extracts all items from the signature_requests array in the API response.
• The endpoint fetches 20 records per page by default and automatically fetches additional pages until all signature requests have been retrieved.

This endpoint retrieves a list of signature requests that you can access in your HelloSign account. You can specify an account ID to retrieve signature requests for a specific team member, or use all to retrieve signature requests for all team members. The endpoint supports pagination through incrementing page numbers, which allows you to retrieve large lists of signature requests efficiently. The response includes pagination metadata that indicates the current page and total pages available. For detailed information about the API response format and available fields, see the HelloSign API documentation.

Download Files as File Url

Obtain a copy of the current documents specified by the signature_request_id parameter.

• Enter the signature request ID you want to download files for in the Signature Request ID field. This should be the unique identifier for the signature request whose documents you want to retrieve.
• The endpoint uses GET requests to https://api.hellosign.com/v3/signature_request/files_as_file_url/{signature_request_id} where {signature_request_id} is the Signature Request ID you provide. The endpoint URL is automatically constructed based on the HelloSign API base URL and the signature request ID.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $, which extracts the entire root-level object from the API response. The response contains URLs to download the document files.

This endpoint retrieves a copy of the current documents for a specific signature request, with the files provided as download URLs. The URLs are temporary and can be used to download the document files. The signature request must exist in your HelloSign account, and you must have permission to access it. For detailed information about the API response format and available fields, see the HelloSign API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

HelloSign data sources can also be manually configured to ingest data from any valid HelloSign API endpoint, including endpoints not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers. HelloSign API endpoints typically follow the pattern https://api.hellosign.com/v3/{endpoint_path} and return data in JSON format.

The endpoint requires authentication via either API Key (Basic authentication) or OAuth2 (Bearer token), which is handled automatically by your credential configuration. For detailed information about HelloSign API endpoints and available APIs, see the HelloSign API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new HelloSign data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.