• Blog

How to Send E-Signature Documents from OutSystems via API

How to Send E-Signature Documents from OutSystems via API

Table of Contents

Sign Docs 3x Faster

Send, sign, and manage documents securely and efficiently.

In this step-by-step guide, I’ll guide you through the process of using BoldSign APIs in OutSystems. This integration grants you access to a premium eSignature solution, achieved with minimal coding. With these instructions, you’ll quickly set up document signing with BoldSign in OutSystems.

Whether you’re a business owner aiming to streamline your document signing process or just someone in need of remote document signing capabilities, this tutorial will guide you in using the powerful combination of BoldSign and OutSystems for efficient and effective results with very little code.

Getting started

In this section, we’ll go through the initial steps to start using BoldSign APIs with OutSystems. You’ll create a BoldSign account, obtain an API key, and set the stage for integrating eSignature functionality into your OutSystems application:

  1. To use BoldSign APIs, you’ll need a BoldSign account, which can be either a paid account or free sandbox account. If you haven’t created one yet, you can sign up for a free account to follow along.
  2. Next, you’ll need an API key to authenticate your access. You can find the API key on the API Key – BoldSign page. Keep this API key handy; we’ll use it in our Python code later.
  3. Log into your OutSystems account. You can either create a new app or use an existing one where you want to integrate eSignature functionality.

Setting up OutSystems for API integration

In OutSystems, you’ll set up the necessary structures to make API calls to BoldSign.

Create a new module

  1. In your OutSystems environment, create a new module or open an existing one where you want to add the BoldSign integration.
Create module option
Create module option
  1. Go to Logic and expand the Integrations section.
Integrations section
Integrations section
  1. Right-click on REST and select Consume REST API.
Consume REST API option
Consume REST API option
  1. Select Add Single Method or Add Multiple Methods, based on your need.
REST API methods
REST API methods
  1. Here, use the BoldSign Swagger JSON path to import all the endpoints.
Insert URL or upload file
Insert URL or upload file
  1. If you want specific endpoints, you can choose them. For this demo, we are selecting only the SendDocument endpoint.
Select endpoints
Select endpoints
  1. Click Finish. You can see the BoldSign SendDocument method added.
Send Document method added
Send Document method added
  1. Right-click the SendDocument method and choose Open.
Open Option
Open Option
Send Document page
Send Document page
Finish button
Finish button

Configure the API request

Add the following headers for the SendDocument API.

KeyValue
acceptApplication/json
X-API-KEYYour-API-KEY

Replace Your-API-KEY with the API key you obtained earlier.

Next, you’ll need to set up the request body:

  1. Provide a title and message for the signer.
  2. Input the signer’s name and email address.
  3. Specify the form field where the signer will provide their signature.
  4. Include the document you want signed, encoded in Base64 format.
Configure API request
Configure API request

Following is an example of the JSON request body.


{
      "files": [
        "data:application/pdf;base64,JVBERi0xLjcNCiW1tbW1DQoxIDAgb2JqDQo8P..."
      ],
      "title": "Send document from OutSystems",
      "message": "test",
      "signers": [
        {
          "name": "JP",
          "emailAddress": "[email protected]",
          "signerOrder": 1,
          "signerType": "Signer",
          "formFields": [
            {
              "id": "sign",
              "fieldType": "Signature",
              "pageNumber": 1,
              "bounds": {
                "x": 100,
                "y": 200,
                "width": 200,
                "height": 50
              },
              "isRequired": true,
              "isReadOnly": false,
                  }
          ]
        }
      ]
     }
    

Note: Replace Recipient Name and [email protected] with the actual name and email address of the signer. Also, replace the files content with your actual, Base64-encoded PDF data.

Checking the API response

This step ensures you’re on the right track. Click the Test button to make sure your app can call the BoldSign API properly.

Check API response
Check API response

You’ll receive a documentId in the response, which means the document has been sent to the signer. The signer will receive an email with a link to sign the document. That’s all there is to it!

API response test result
API response test result

The following links will help you learn more about BoldSign and how to integrate it with OutSystems:

Conclusion

Start integrating BoldSign with OutSystems today and deliver modern document signing to your users. The best way to experience BoldSign is to sign up for a free sandbox account and try sending a few signature requests yourself.

To get started with BoldSign, check out the BoldSign API documentation. Explore all the BoldSign features in the BoldSign features page.

If you have questions, you can contact us through our support portal. We are always happy to assist you!

Like what you see? Share with a friend.

Latest blog posts

How ID Verification Protects Your Rental Applications from Fraud

How ID Verification Protects Your Rental Applications from Fraud

Add ID verification for rental applications to your eSignature flow—BoldSign verifies ID + selfie before signing and keeps a clear audit trail to minimize fraud risks.

Webinar Show Notes: What’s New in BoldSign

Webinar Show Notes: What’s New in BoldSign

Missed the BoldSign webinar? Explore new QES, AI‑assisted fields, WhatsApp notifications, and more—new features designed for faster, compliant eSigning.

ASP.NET Core JWT Authentication: Setup, Validation, and Best Practices

ASP.NET Core JWT Authentication: Setup, Validation, and Best Practices

TL;DR: JWT performs best when you avoid server sessions, minimize claims, and rely on cached key and metadata lookup. Prioritize strict validation and short-lived access tokens; implement refresh only for long-lived sessions. High-traffic APIs validate on every request, so these choices directly control latency and risk. JWT authentication in ASP.NET Core is a stateless, token-based […]

Sign up for your free trial today!

  • tick-icon
    30-day free trial
  • tick-icon
    No credit card required
  • tick-icon
    30-day free trial
  • tick-icon
    No credit card required
Sign up for BoldSign free trial