Skip to content
PHP SDK

eSignature SDK for PHP applications

Send documents for signature from your PHP code with the BoldSign PHP SDK. Signers sign in their browser from an email link, or inside your app.

Create free API sandboxBook a walkthrough
  • Install from Composer
  • API key or OAuth 2.0
  • Webhooks for every status change
Your CompanyPreviewSend
Assignee
David
SERVICE AGREEMENT
Company signatureSign here*
Client signatureSign here*
agreements.phpPHP SDK
$documentApi = new DocumentApi($config);$signer = new DocumentSigner();$signer->setName("David");$signer->setEmailAddress("david@cubeflakes.com");$request = new EmbeddedDocumentRequest();$request->setTitle("Service Agreement");$request->setSigners([$signer]);$request->setSendViewOption("PreparePage");$request->setShowToolbar(true);$embeddedSendCreated =  $documentApi->
    createEmbeddedRequestUrlDocument($request);$sendUrl = $embeddedSendCreated->send_url;
Sample PHP web app at yourapp.example with BoldSign embedded: the prepare page of a service agreement assigned to David, with Preview and Send buttons, beside the PHP code from BoldSign’s docs that creates this embedded request

Trusted by 100,000+ organizations worldwide

Samsonite
Ryanair
Hyatt
Sony
Crumbl Cookies
Payroc
Cost Plus
The problem

Why is adding eSignatures to a PHP app harder than it looks?

Signing is quick. Legal validity, identity checks, reminders, an audit trail, and a sealed PDF are not. With the BoldSign PHP SDK, you get all five from your PHP code.

  • Collecting the signature is quick

    A signature pad takes an afternoon. The record behind it takes much longer.

  • The document has to stand up later

    A sealed PDF needs a trusted certificate you buy and renew, and a timestamp on each action.

  • Your team carries it

    Reminders, status tracking, and file storage stay in your code once the feature ships.

The solution

How can you add eSignatures to a PHP app without building them?

The BoldSign PHP SDK gives your code two routes to a signature. BoldSign runs the signing behind both. Your app creates the document, names the signers, and tracks what comes back.

  • Send for signature from your code

    Your PHP code posts the document and signers to BoldSign, which emails each signer a private link.

  • Embed signing in your product

    BoldSign returns a signing URL for your own page. The signer signs the document inside your app, without leaving it.

Capabilities

What can your PHP app do with the PHP eSignature SDK?

With the BoldSign PHP SDK, your PHP app handles the whole signing flow. Every completed PDF is digitally signed.

  • Send documents for signature

    Send a contract or form from PHP to one signer or several, in the order you set.

    See the eSignature API

  • Sign inside your app

    Display the signing page in your own PHP pages, so the signer never leaves your product.

    See embedded signing

  • Prepare and send in your app

    Your users place fields and send the document from inside your PHP app.

    See embedded sending

  • Send from templates

    Save a template with its fields once, then reuse it for new signers from PHP.

    See templates

  • Check who is signing

    Pick a check per signer: access code, email code, SMS code, KBA, or ID verification.

    See signer authentication

  • Know when it is signed

    Catch each status change on your webhook route, then download the signed PDF and audit trail.

    See webhooks

Works in: server-side PHP apps installed with Composer. Keep the SDK on your server, since it carries your API key.

Get started

How do you implement electronic signatures in PHP?

You implement BoldSign eSignatures in PHP in 3 steps: install the SDK, authenticate, and send.

  1. Install from Composer

    composer require boldsign/boldsign-php

    Runs on PHP 7.4 or later.

  2. API authentication

    $config = new BoldSign\Configuration();$config->setHost("https://api.boldsign.com");$config->setApiKey("Your-API-Key-Here");

    Connect your API key, or use an OAuth 2.0 token.

  3. Send the document

    $documentCreated = $documentApi->sendDocument(...);

    The response holds the document ID.

Using an AI coding tool? Connect BoldSign’s coding assistant (MCP), then try this prompt. Set up the coding assistant.Write a PHP function that sends a document for signature with the BoldSign PHP SDK.

See the full PHP walkthrough
Why BoldSign

Why choose BoldSign for PHP developers

BoldSign suits PHP teams that want signing in their product without building or maintaining it.

  • One package, two PHP generations

    The same Composer package supports PHP 7.4 and PHP 8. It drops into an older codebase and a current one without separate installs.

  • Write PHP code with your AI coding tool

    BoldSign’s coding assistant (MCP) plugs into VS Code, Cursor, or Claude. It answers SDK questions from BoldSign’s docs, with no API key.

  • Build it all before you pay

    Try every endpoint in a free sandbox and finish the work before go-live.

  • Signers need no account

    No BoldSign account and no download for anyone who signs.

  • Legally binding signatures

    Signatures you collect with BoldSign are legally binding under the ESIGN Act, UETA, and eIDAS.

Security

How are documents sent from your code kept secure?

BoldSign encrypts every document twice with AES-256. Its controls are audited independently for SOC 2 Type 2. Open the Compliance page in your account to see each standard, shown below.

Compliance

BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.

US flag

Data Residency

Active (US - Global)

Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.

View Data Residency Policy
HIPAA logo

HIPAA Compliance

Enabled

Enable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.

View Details
PCI DSS logo

PCI DSS

Compliant

Payments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.

View PCI DSS Policy
CCPA logo

CCPA & CPRA

Compliant

Ensures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.

View Privacy Policy
AICPA SOC logo

SOC 2 Type II

Compliant

BoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.

Request SOC 2
US flag

UETA & ESIGN

Compliant

BoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).

View UETA & ESIGN Policy
EU flag

eIDAS (SES)

Compliant

BoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.

View SES Policy
EU flag

eIDAS (QES)

Enabled

Enable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.

View QES Policy
The compliance panel in your BoldSign account.
For IT and procurement

Security and procurement documents for eSignature

IT and procurement teams can read BoldSign’s security policy, data processing agreement, and subprocessor list online. They can also request the SOC 2 Type 2 report.

What it costs

Limits and costs to know before you send from PHP with BoldSign

The BoldSign PHP SDK is free to install from Composer. Live documents run on a BoldSign API plan. Prices are in USD.

  • $30 Enterprise API plan, per month 40 envelopes included, then $0.75 each.
See all limits and add-on prices
Good to know
  • 2,000 API requests an hour per account The sandbox allows 50 an hour.
Related

More guides for building eSignatures in PHP

  • Page

    All eSignature SDKs

    Compare the five official BoldSign SDKs.

    See all SDKs
  • Page

    Embedded signing

    Open the signing page inside your own app.

    See embedded signing
  • Guide

    Laravel example

    Add BoldSign signing to a Laravel app, with the signing page inside your product.

    Read the guide
  • Guide

    Build an AI agent

    Let an AI agent send documents through the BoldSign MCP server.

    Read the guide
Common questions

Questions about the PHP eSignature SDK

Is there a PHP digital signature SDK?

Yes. The BoldSign PHP SDK, published on Packagist as boldsign/boldsign-php, is BoldSign’s official SDK for PHP. People sign electronically, and BoldSign seals each completed PDF with an AATL certificate.

Can I add eSignatures to a Laravel app?

Yes. The BoldSign PHP SDK installs in Laravel like any Composer package. The Laravel guide walks through a full example.

How do webhooks work with the PHP SDK?

Webhooks are set up once in your BoldSign account, under API then Webhooks, not in the SDK. BoldSign posts each status change to your HTTPS endpoint, so your PHP app never polls for status. Set up a webhook.

Does the PHP SDK support OAuth 2.0?

Yes. Pass a bearer token instead of an API key when you configure the client. See OAuth 2.0 setup.

How do I use the Europe, Canada, or Australia region?

Pass your region’s base URL to setHost, such as api-eu.boldsign.com for Europe. US accounts need no change. See all base URLs.

Can I test the PHP SDK for free?

Yes. Create a free BoldSign API sandbox, then use its API key with the PHP SDK. Sandbox documents are for testing only.

Get started

Send your first document from PHP

Open a free BoldSign API sandbox, install the PHP SDK from Composer, and send your first document.

Create free API sandboxBook a walkthrough
  • 30-day free trial
  • No credit card required

Last updated: October 18, 2026