How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Lone Wolf Technologies

Lone Wolf Technologies Signings API

The Signings API from Lone Wolf Technologies — 23 operation(s) for signings.

Documentation Provider Profile APIs.io OpenAPI GitHub

Lone Wolf Technologies Signings API is one of 65 APIs that Lone Wolf Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Signings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a changelog, and authentication docs.

This API exposes 27 operations across 23 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://api.lwolf.com/authentisign, https://gateway.lwolf.com, {tw_host}.

27 operations 23 paths 9 schemas 1 DELETE13 GET1 PATCH11 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://gateway.lwolf.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Lone Wolf Technologies Signings API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as lw-subscription-key (subscriptionKey).

  • bearerAuth — JWT access token obtained from the /oauth/token endpoint, sent as Authorization: Bearer .
  • subscriptionKey — API subscription key issued by Lone Wolf, sent on every request.

Paths & Operations 27

Across 23 paths, the API surfaces 27 operations — 1 DELETE, 13 GET, 1 PATCH, 11 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Signings 27
GET
/api/v1/signings
Retrieve all signings owned by a user. This endpoint fetches a list of all the signings that the user owns.
GetSignings 7 params → 200default
POST
/api/v1/signings
Create a signing. This endpoint allows for the creation of a new signing, including the ability to add a webhook callback URL.
CreateSigning 1 param body → 200default
GET
/api/v1/signings/{id}
Retrieve details of an individual signing. This endpoint fetches details for the signing associated with the provided signing ID.
GetSigning 1 param → 200default
PATCH
/api/v1/signings/{id}
Update the callback URL for a signing. This endpoint allows you to update the callback URL on the signing for webhook events.
UpdateSigningCallback 2 params body → 200400404
DELETE
/api/v1/signings/{id}
Deletes a signing session. This endpoint removes a signing session based on the provided signing ID.
DeleteSigning 1 param → 200default
POST
/api/v1/signings/{id}/copy
Duplicate an existing signing. This endpoint creates a copy of a signing session based on the provided signing ID.
CopySigning 1 param → 200default
POST
/api/v1/signings/{id}/reset
Reset a signing session. This endpoint resets the status of a signing session based on its ID.
ResetSigning 1 param → 200default
POST
/api/v1/signings/{id}/resend-invitation
Resend the signing invitation. This endpoint resends the invitation for a signing session based on the provided signing ID.
ResendInvitation 1 param → 200default
POST
/api/v1/signings/{signingId}/send-final-documents
Send final documents of a signing session. This endpoint sends the final documents for a completed signing session.
SendFinalDocuments 2 params body → 200default
POST
/api/v1/signings/{signingId}/link-transaction
Link a transaction to a signing session. This endpoint associates a transaction with a signing session based on the provided ID.
LinkTransaction 3 params body → 200default
POST
/api/v1/signings/{signingId}/force-complete
Force completes a signing session. This endpoint forcefully completes a signing session based on the provided signing ID.
ForceCompleteSigning 1 param → 200default
GET
/api/v1/signings/deleted
Retrieve deleted signing sessions. This endpoint fetches all the deleted signing sessions for a given external ID.
GetDeletedSignings 1 param → 200404default
PUT
/api/v1/signings/{signingId}/recover-deleted
Recover a deleted signing session. This endpoint recovers a deleted signing session based on the provided signing ID.
RecoverDeletedSigning 1 param → 200401404default
POST
/api/v1/signings/{signingId}/send-signing
Send a signing session to participants. This endpoint starts the signing process for a signing session based on the provided signing ID.
SendSigning 1 param → 200400401default
POST
/api/v1/signings/{signingId}/reject
This is only called by Trestle client
RejectSigning 1 param → 200400401default
GET
/api/v1/signings/participants/{signingId}/invitations
GetLinksOfInvitationsWhenSigningIsSent 1 param → 200404default
GET
/api/v1/signings/documents/{signingId}/completed
GetLinksOfDocumentsWhenSigningIsCompleted 1 param → 200404default
GET
/api/v1/signings/documents/{signingId}/originals
GetLinksOfOriginalDocuments 1 param → 200404default
GET
/api/v1/signings/documents/{signingId}/certificates
GetLinksOfCertificateDocuments 1 param → 200404default
GET
/authentisign/v3/users/{userId}/signings
List signings
getSignings 2 params → 200400401403404
POST
/authentisign/v3/users/{userId}/signings
Create a signing
createSigning 2 params body → 201400401403404
GET
/authentisign/v3/api/v3/users/{userId}/sso/signing/{signingId}
Get a signing SSO link
getSigningSsoLink 3 params → 200400401403404
POST
/authentisign/v3/api/v3/users/{userId}/participants/batch
Add signing participants (batch)
addSigningParticipants 1 param body → 201400401403404
GET
/authentisign/v3/api/v3/users/{userId}/signings/{signingId}/documents
List original signing documents
getSigningDocuments 2 params → 200400401403404
GET
/authentisign/v3/api/v3/users/{userId}/signings/{signingId}/documents/s
List signed documents
getSignedDocuments 2 params → 200400401403404
GET
/authentisign/v3/api/v3/users/{userId}/signings/{signingId}/documents/sc
List signing certificates
getSigningCertificates 2 params → 200400401403404
GET
/authentisign/v3/api/v3/{encryptedDocumentId}/d
Download an individual signed document
getSignedDocument 1 param → 200400401403404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Authentisign.Services.Dtos.ParticipantDto (23 properties), SigningParticipant (9 properties), Microsoft.AspNetCore.Mvc.ProblemDetails (5 properties), Authentisign.Services.Dtos.ErrorResponse (3 properties). Each schema is shown below with its type and property counts.

Microsoft.AspNetCore.Mvc.ProblemDetails
object
5 properties
Authentisign.Services.Dtos.TransactionDesk.TDLinkTransactionDto
object
2 properties
Authentisign.Services.Dtos.TransactionDesk.TDDocumentMapChecklistItemDto
object
2 properties
Authentisign.Services.Dtos.EmailsDto
object
1 property 1 required
Authentisign.Services.Dtos.SigningUpdateDto
object
1 property
Authentisign.Services.Dtos.ErrorResponse
object
3 properties
Authentisign.Services.Dtos.ParticipantDto
object
23 properties 3 required
SigningParticipant
object
9 properties 5 required
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lone-wolf-signings-api-openapi.yml Raw ↑

Other APIs Lone Wolf Technologies publishes across the network.

Lone Wolf Authentisign API
AE Profile APIs.io
Lone Wolf Technologies Accounts API
AE Profile APIs.io
Lone Wolf Technologies Authentication API
AE Profile APIs.io
Lone Wolf Technologies Authorization API
AE Profile APIs.io
Lone Wolf Technologies Business Contact API
AE Profile APIs.io
Lone Wolf Technologies Business Contacts API
AE Profile APIs.io
Lone Wolf Technologies C Cs API
AE Profile APIs.io
Lone Wolf Technologies Classification API
AE Profile APIs.io
Lone Wolf Technologies Classifications API
AE Profile APIs.io
Lone Wolf Technologies Client Contact API
AE Profile APIs.io
Lone Wolf Technologies Client Contacts API
AE Profile APIs.io
Lone Wolf Technologies Commission API
AE Profile APIs.io
#Signings
← Back to L APIs
API Details
ID
lone-wolf:lone-wolf-signings-api
Base URL
https://gateway.lwolf.com
Docs
https://apidocs.lwolf.com/doc/transact-api
Provider
Lone Wolf Technologies
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lone-wolf-signings-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lone-wolf-signings-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Lone Wolf Technologies Signings API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.