Papersign

Papersign is Paperform's e-signature product. Its API lets you manage documents, folders, and spaces, send documents out for signature, and register webhooks that fire on signature-status events.

Power end-to-end data operations for your Papersign API with Nexla. Our bi-directional Papersign connector is purpose-built for Papersign, 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 Papersign or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Papersign 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 Papersign credential, you need a Papersign API key. Papersign is part of Paperform, and the API uses bearer token authentication: your API key is sent in the Authorization header as Bearer <token> on every request.

To obtain your Papersign API key, follow these steps:

1. Confirm that your Paperform subscription includes API access. Papersign API access requires an eligible Papersign or Paperform plan. Check the Paperform pricing pages to verify your plan.

2. Sign in to your Paperform account at paperform.co.

3. Navigate to your account developer settings at paperform.co/account/developer.

4. Generate a new API key.

5. Copy the API key and store it securely. You will provide this key when creating your Nexla credential.

For details on authentication and the available endpoints, see the Papersign API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key used to authenticate requests to the Papersign API.

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.

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

3. Enter your Papersign API key in the API Key field. This key is sent in the Authorization header as a bearer token on all requests to the Papersign API and must be kept confidential.

   If your API key is compromised, revoke it in your Paperform developer settings and generate a new one.

   For detailed information about authentication and available endpoints, see the Papersign API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

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 Papersign connector tile, then select the credential that will be used to connect to Papersign, and click Next; or, create a new Papersign 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 Papersign 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.

List Documents

Retrieve documents.

• This endpoint returns a list of Papersign documents in your account. The endpoint is paginated, and Nexla automatically fetches subsequent pages until no further records are returned.

For details about documents and the response structure, see the Papersign API documentation.

List Folders

Retrieve folders.

• This endpoint returns the folders in your Papersign account. Use the folder IDs it returns to configure the List Webhooks source and the Create Webhook destination.

For details about folders and the response structure, see the Papersign API documentation.

List Spaces

Retrieve spaces.

• This endpoint returns the spaces in your Papersign account.

For details about spaces and the response structure, see the Papersign API documentation.

List Webhooks

Retrieve webhooks.

• This endpoint returns the webhooks registered on a Papersign folder. Provide the Folder ID of the folder whose webhooks you want to list. You can obtain folder IDs from the List Folders endpoint.

For details about webhooks and the response structure, see the Papersign 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

Papersign data sources can also be manually configured to ingest data from any valid Papersign API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. 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.

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 Papersign 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Papersign destination, and select the Send to Destination option from the menu. Select the Papersign connector from the list of available destination connectors, then select the credential that will be used to connect to Papersign, and click Next; or, create a new Papersign credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Papersign endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Folder

Create a new Papersign folder within a space or parent folder.

• Each record from your Nexset is sent as a JSON request body to create a new folder. The record should contain the folder properties expected by the Papersign API.

For details about folder creation and the required request body, see the Papersign API documentation.

Create Webhook

Create a webhook on a Papersign folder that fires for signature-status events on documents in that folder.

• Provide the Folder ID of the folder the webhook should be attached to. Each record from your Nexset is sent as a JSON request body containing the webhook configuration.

For details about webhook creation and the required request body, see the Papersign API documentation.

Send Document

Send a Papersign document to its recipients/signers for signature.

• Provide the Document ID of the document to send. Each record from your Nexset is sent as a JSON request body containing any send options expected by the Papersign API.

For details about sending documents and the required request body, see the Papersign API documentation.

Manual configuration

Papersign destinations can also be manually configured to send data to any valid Papersign API endpoint. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Papersign endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Papersign endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.