> **Source:** https://knowledge.leegality.com/sign-station/api/leegality-signstation-api
> **Site:** Leegality Knowledge Base — https://knowledge.leegality.com
> **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration.
> **Navigation:** Every article on this site has a plain-text version at `<article-url>.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt
> **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt

---
# Leegality SignStation API

> Welcome to the Leegality Sign Service (SignStation) API documentation. SignStation is Leegality's on-premise digital signing platform. This API lets you integrate every part of it — from signing documents with your own PKCS12 certificates to managing users, roles, audit logs, and notifications — directly into your applications and back-office systems.

Welcome to the Leegality Sign Service (SignStation) API documentation. SignStation is Leegality's on-premise digital signing platform. This API lets you integrate every part of it — from signing documents with your own PKCS12 certificates to managing users, roles, audit logs, and notifications — directly into your applications and back-office systems.

## What can you do with this API?

- **Sign documents** — Apply legally valid digital signatures, retrieve signed copies, and download audit trails for compliance.
- **Manage certificates** — Upload, assign, and track expiry of PKCS12 (`.pfx` / `.p12`) certificates used for signing.
- **Control access** — Create users and departments, define roles with granular entitlements (RBAC), and enforce password policies.
- **Authenticate** — Use JWT Bearer tokens via user login, or OAuth2 client credentials for machine-to-machine integrations.
- **Configure notifications** — Set up email rules for events such as certificate expiry, document completion, and more.
- **Audit & comply** — Search detailed audit logs of every system action; configure retention and audit trail generation.
- **Manage your license** — Install license files, view current status, and track usage statistics.

## Base URL

SignStation is deployed on your own infrastructure, so the base URL is unique to your organisation. The reference instance used throughout this documentation is:

`https://sign-station.theleegality.com`

Replace it with your own SignStation host when making API calls. If you are unsure of your base URL, contact your SignStation administrator.

## Getting started

1. **Generate a token** — Call `/api/v1/auth/login` with your username and password to receive a JWT Bearer token. For machine-to-machine flows, use `/api/v1/auth/token` with OAuth2 client credentials.
2. **Authorise your requests** — Click **Authorize** on this page (or include the header `Authorization: Bearer <your-jwt-token>` in your client) to try out endpoints directly from the documentation.
3. **Explore by feature** — Each section in the left sidebar maps to one functional area of SignStation (Documents, Certificates, Users, Roles, and so on). Every endpoint includes request and response examples.

For the dashboard equivalent of these flows, see [Logging In](https://knowledge.leegality.com/sign-station/getting-started/logging-in) and [API Credentials](https://knowledge.leegality.com/sign-station/api-credentials).

## Need help?

Reach out to [support@leegality.com](mailto:support@leegality.com) for any questions about your integration or deployment.

      JWT Bearer token authentication. Use the login endpoint (/api/v1/auth/login) to get a token, then click 'Authorize' and enter: Bearer &lt;your-jwt-token&gt;

        <table>
          <tbody>
            <tr>
              <th>
                Security Scheme Type:
              </th><td>
                http
              </td>
            </tr><tr>
              <th>
                HTTP Authorization Scheme:
              </th><td>
                bearer
              </td>
            </tr><tr>
              <th>
                Bearer format:
              </th><td>
                JWT
              </td>
            </tr>
          </tbody>
        </table>