BoldSign is an electronic signature and document workflow platform that provides a REST API for sending documents for signature, managing reusable templates, tracking document status, downloading signed documents and audit trails, and administering teams, users, contacts, branding, sender identities, and custom fields. The API returns JSON, is stateless, and authenticates every request against an API key, enabling integrations to embed e-signing into upstream applications and to keep signature, template, and account data in sync with downstream systems.
Power end-to-end data operations for your BoldSign API with Nexla. Our bi-directional BoldSign connector is purpose-built for BoldSign, 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 BoldSign or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your BoldSign 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
The BoldSign REST API authenticates each request using an API key. The key is passed in the X-API-KEY header on every call and is tied to the BoldSign account that generated it, so the calling integration acts with the permissions of that account.
Before creating a credential in Nexla, generate an API key from your BoldSign account. API access must be included in your BoldSign plan in order for the key generation option to be available.
In the left navigation pane, click the API menu item, and then select API Key.
Click the Generate API Key button to open the Generate API Key dialog.
Enter a descriptive name for the key (for example, "Nexla Integration") so that the key can be easily identified later.
Choose the environment for the key:
Live: Use a Live key to call BoldSign in production. Live calls operate on real documents, signers, and account data.
Sandbox: Use a Sandbox key while building and testing the integration. Sandbox keys execute against the BoldSign test environment and do not affect production data.
BoldSign allows up to four API keys per account, with no more than two keys in a single environment (Live or Sandbox). Plan the number of keys needed across environments before generating new ones.
Optionally, enable the Token Validity toggle, and select an expiration date. Setting an expiration date is a best practice for keys used by long-running integrations, because it forces a periodic rotation.
Click the Generate Token button. BoldSign displays the new API key value.
Copy the generated API key, and store it securely. This value grants access to your BoldSign account using your account's permissions, so it should be treated like a password.
BoldSign shows the full API key value only at the time of generation. Copy it immediately and store it in a secure secret manager — if the value is lost, a new key must be generated. Existing keys can be revoked at any time from the same API Key screen.
The BoldSign API key grants access to your BoldSign account data, including signed and in-flight documents. Store it in a secure secret manager, never commit it to source control, and revoke and regenerate it immediately if you suspect it has been exposed.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your BoldSign API Key value in the API Key field. This is the key value generated from the API > API Key screen in your BoldSign account, and it is treated as a secret. Nexla passes this value in the X-API-KEY header on every call to the BoldSign API.
Match the key's environment to the BoldSign environment you intend to integrate with. Use a Live key for production document workflows, and a Sandbox key while developing and testing the data flow.
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 and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button. Select the BoldSign connector tile from the list of available connectors, then select the credential that will be used to connect to the BoldSign instance, and click Next; or, create a new BoldSign credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common BoldSign 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Document List
This endpoint retrieves a paginated list of documents from the BoldSign account, including documents in any status (sent, in-progress, signed, declined, expired, revoked). Use this endpoint to sync the full set of e-signature documents and their current status into a warehouse or reporting system.
The Page field is optional and identifies which page of results to retrieve. The default value is 1.
The Pagesize field is optional and controls how many records are returned per page. The default value is 5; increase it to reduce the number of round trips needed to retrieve a large document set.
Document records returned by this endpoint include the document ID. That ID is the input for the Get Document Properties, Download Document, Download Audit Log, and Get Embedded Signing Link endpoints.
Get Document Properties
This endpoint retrieves detailed metadata and status for a single document by ID, including signer activity, timestamps, and current document state. Use it to enrich an existing dataset of document IDs with the latest document details.
Enter the BoldSign document ID in the Document ID field. This field is required. Document IDs can be obtained from the Document List or List Team Documents endpoints or from upstream Nexla data flows.
Download Document
This endpoint downloads the signed or completed document PDF by document ID. Use it to archive executed agreements into a downstream document management system or to attach the executed PDF to records in another system.
Enter the BoldSign document ID in the Document ID field. This field is required. Document IDs can be obtained from the Document List endpoint.
BoldSign only allows the signed PDF to be downloaded after the document has reached a completed state. Filter upstream document records by status before driving this endpoint to avoid unnecessary failed calls.
Download Audit Log
This endpoint downloads the audit trail or completion certificate for a document. The audit trail records the full signing history (views, signatures, declines, IP addresses, timestamps) and is typically retained for compliance.
Enter the BoldSign document ID in the Document ID field. This field is required.
Get Embedded Signing Link
This endpoint generates an embedded signing link that allows a specific signer to sign a document directly inside your application, without leaving for the hosted BoldSign signing page. Use this endpoint to power an in-app signing experience.
Enter the BoldSign document ID in the Document ID field. This field is required and identifies the document for which the link is generated.
Enter the signer's email address in the Signer Email field. The link will be tied to the signer role that matches this email on the document.
Enter the country code for the signer's phone (for example, +1) in the Country Code field if the signing flow requires phone-based multi-factor authentication.
Enter the signer's phone number in the Phone Number field if phone-based multi-factor authentication is required.
Enter the URL to redirect the signer to after they complete signing in the Redirect URL field. This is typically a confirmation page in your own application.
Embedded signing links are short-lived and intended for one-time use. Generate a fresh link each time a signer enters the signing flow. For complete details, see the BoldSign embedded signing link documentation.
List Team Documents
This endpoint returns a paginated list of documents owned by team members. Use it to sync documents across an entire team into a downstream system without iterating individual users.
No endpoint-specific parameters are required. Nexla automatically paginates through all available team documents using the BoldSign page and pageSize query parameters, stopping when no more records are returned.
List Behalf Users
This endpoint returns a paginated list of users who can send and sign documents on behalf of the account owner. Use it to sync the set of authorized "send-on-behalf-of" users for governance and access reviews.
The Page Number field is optional and identifies which page of results to retrieve. Page numbers start at 1.
Template List
This endpoint retrieves a list of reusable templates configured in the BoldSign account. Templates predefine signer roles, fields, and document content for repeated signature requests. Use this endpoint to sync the template catalog into downstream systems or to obtain template IDs for use with the Send Template destination endpoint.
The Pagesize field is optional and controls how many records are returned per page. The default value is 10.
The Page field is optional and identifies which page of results to retrieve. The default value is 1.
Get Template Properties
This endpoint retrieves the full configuration of a single template by ID, including roles, fields, and metadata. Use it to enrich a template catalog with detailed definitions for governance or to drive downstream automation that depends on template structure.
Enter the BoldSign template ID in the Template ID field. This field is required. Template IDs can be obtained from the Template List endpoint.
Brand List
This endpoint retrieves all brands configured in the BoldSign account. Brands customize the logo, colors, and signer experience for different business units or product lines.
No configuration is required for this endpoint beyond selecting it.
List - SenderIdentity
This endpoint retrieves a paginated list of sender identities. Sender identities represent verified "from" addresses that can be used when sending documents for signature, allowing the account to send on behalf of multiple verified email addresses.
The Page field is optional and identifies which page of results to retrieve. The default value is 1.
The Pagesize field is optional and controls how many records are returned per page. The default value is 5.
List Contacts
This endpoint returns all contacts in the BoldSign account. Contacts are the saved set of signers and recipients that can be reused across documents.
No configuration is required for this endpoint beyond selecting it.
This endpoint returns all custom fields configured in the BoldSign account. Custom fields extend documents and templates with organization-specific data inputs.
No configuration is required for this endpoint beyond selecting it.
List Teams
This endpoint retrieves a paginated list of teams configured in the BoldSign account. Teams group users for shared visibility into documents and templates.
The Page Number field is optional and identifies which page of results to retrieve.
The Page Size field is optional and controls how many records are returned per page.
This endpoint is paginated, and Nexla automatically advances through pages to retrieve all available teams.
User List
This endpoint retrieves a paginated list of users in the BoldSign account, including their roles and status. Use it to sync the BoldSign user base into an identity, HR, or reporting system.
The Page field is optional and identifies which page of results to retrieve. The default value is 1.
The Pagesize field is optional and controls how many records are returned per page. The default value is 10.
Get API Credits Count
This endpoint retrieves the current API credits remaining on the BoldSign plan. Use it to monitor API consumption and to alert when remaining credits fall below a threshold.
No configuration is required for this endpoint beyond selecting it.
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.
BoldSign data sources can also be manually configured to ingest data from any valid BoldSign API endpoint, including endpoints not covered by the pre-built templates, chained API calls (for example, listing documents and then fetching properties for each), 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.
BoldSign API endpoints follow the format https://api.boldsign.com/v1/<resource> — for example, https://api.boldsign.com/v1/document/list?page=1&pageSize=10. BoldSign list endpoints wrap records in a top-level result array, so the path to data for the /document/list endpoint is entered as $.result[*]. The X-API-KEY header is handled automatically by Nexla based on your credential configuration and does not need to be added as a request header.
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 BoldSign 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.
Click the + icon on the Nexset that will be sent to the BoldSign destination, and select the Send to Destination option from the menu. Select the BoldSign connector from the list of available destination connectors, then select the credential that will be used to connect to the BoldSign account, and click Next; or, create a new BoldSign credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common BoldSign 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.
Send Document
This endpoint sends a document for signature to one or more signers and CC recipients. Use it to programmatically launch signature requests as records flow in from an upstream system — for example, turning a row in a CRM or contract management system into an out-for-signature document.
Each upstream record is sent as the JSON body of the POST call. Use the Nexla transform layer to shape upstream attributes into the field names expected by the BoldSign send-document API, such as title, signers, files, and message.
This endpoint sends a document built from a reusable template to signers for signature. Use this endpoint when the document structure (fields, signer roles, content) is predefined in a BoldSign template and only signer-specific values need to be supplied per call.
Enter the BoldSign template ID in the Template ID field. This field is required and identifies the template that will be used to generate the signature request. Template IDs can be obtained from the Template List data source endpoint.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to the role-specific signer fields expected by the template (for example, signer name, email, and any pre-fill values).
Remind Document
This endpoint sends a signing reminder to the pending signers on an in-flight document. Use it to automate nudge cadences for documents that have been out for signature beyond a threshold.
Enter the BoldSign document ID in the Document ID field. This field is required and identifies the document to send a reminder for. Map the upstream record's document ID into this field.
Change Access Code
This endpoint updates the access code (one-time passcode) required for a signer to open a document. Use it when the access code needs to be rotated or shared through a separate channel partway through the signing workflow.
Enter the BoldSign document ID in the Document ID field. This field is required and identifies the document whose signer access code is being updated.
Each upstream record is sent as the JSON body of the POST call and should include the signer's email and the new access code value.
Revoke Document
This endpoint revokes (cancels) an in-flight document that has not yet been signed by all parties. Use it to recall documents when upstream systems indicate the underlying agreement is no longer valid.
Enter the BoldSign document ID in the Document ID field. This field is required and identifies the document to revoke.
Each upstream record is sent as the JSON body of the POST call and should include the revocation reason (and any other supported revocation parameters).
Revocation is permanent for the document instance. Filter upstream records to only those documents that should genuinely be cancelled before activating this destination.
Delete Document
This endpoint permanently deletes a completed or declined document from the account. Use it to enforce retention policies or to remove test documents from a production account.
Enter the BoldSign document ID in the Document ID field. This field is required and identifies the document to delete.
Because deletion is irreversible and may have compliance implications, route upstream data through a Nexla transform that filters to only documents eligible for deletion before activating this destination.
Create Template
This endpoint creates a new reusable template with the specified roles, CC recipients, fields, and other configuration. Use it to programmatically provision templates from a system of record.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to the template fields expected by BoldSign, such as title, roles, and the document content/files.
Delete Template
This endpoint deletes a template that is no longer needed. Use it to retire templates as part of a template lifecycle process.
Enter the BoldSign template ID in the Template ID field. This field is required and identifies the template to delete.
Create Brand
This endpoint creates a new brand with custom branding settings and a redirect URL. Use it to provision per-business-unit or per-product branding from a central configuration source.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to the brand fields expected by BoldSign, such as brandName, logo, color, and redirect URL values.
Edit Brand
This endpoint updates an existing brand's settings and customization properties. Use it to keep BoldSign brand configurations aligned with an upstream branding source of truth.
Enter the BoldSign brand ID in the Brand ID field. This field identifies the brand to edit.
Each upstream record is sent as the JSON body of the POST call. Include only the fields that should be changed.
Create Sender Identity
This endpoint creates a new sender identity with a specified name and email address. Sender identities let an account send signature requests on behalf of multiple verified addresses.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to name and email at a minimum.
The email address used for a new sender identity must be verified through BoldSign before it can be used to send documents.
Update Sender Identity
This endpoint updates an existing sender identity with a new name for the specified email address. Use it to keep display names aligned with HR or identity changes.
Enter the email address of the sender identity to update in the Email Address field. The email address acts as the key used to locate the identity.
Each upstream record is sent as the JSON body of the PUT call and should include the new name value.
Create Team
This endpoint creates a new team in the BoldSign account. Use it to provision teams from an upstream HR or identity system.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to the team field names expected by BoldSign, such as name and team member assignments.
Update Team
This endpoint updates an existing team identified by team ID. Use it to keep BoldSign team membership in sync with an upstream system of record.
Enter the BoldSign team ID in the Team ID field. This field is required and identifies the team to update.
The body of each PUT call is the upstream record (as JSON). Include only the fields that should be changed; omitted fields are left untouched.
Create Contact
This endpoint creates a new contact in the BoldSign contacts list. Use it to provision frequently used signer and recipient contacts from a CRM or address book system.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to name, email, and any other supported contact attributes.
Invite User
This endpoint invites a new user to the BoldSign account or team. Use it to automate user onboarding from an upstream HR or identity system.
Each upstream record is sent as the JSON body of the POST call. Map upstream attributes to the invite field names expected by BoldSign, such as emailId, userRole, and any team assignment values.
BoldSign destinations can also be manually configured to send data to any valid BoldSign 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. Nexla can also send the response received from the BoldSign API after each call to a new Nexla webhook data source — useful for capturing IDs returned by BoldSign for newly created documents, templates, or brands.
The BoldSign API expects application/json, so JSON is the appropriate content format for most operations. BoldSign API endpoints follow the format https://api.boldsign.com/v1/<resource> — for example, https://api.boldsign.com/v1/document/send or https://api.boldsign.com/v1/template/send?templateId=<template-id>. For update operations, include the ID of the object to be updated in the URL. The X-API-KEY header is handled automatically by Nexla based on your credential configuration.
Most BoldSign write endpoints operate on a single document, template, or account resource per call. Record batching is best suited to custom endpoints that accept multiple records in a single request — confirm the target endpoint supports batched payloads before enabling this option.
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 begin sending data to BoldSign, open the destination resource menu, and select Activate.
The Nexset data will not be sent to BoldSign until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
