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

Lone Wolf Technologies Documents API

The Documents API from Lone Wolf Technologies — 17 operation(s) for documents.

Lone Wolf Technologies Documents 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 Documents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a changelog, and authentication docs.

This API exposes 19 operations across 17 paths, and defines 4 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}.

19 operations 17 paths 4 schemas 1 DELETE15 GET1 PATCH2 POST

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 Documents 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 19

Across 17 paths, the API surfaces 19 operations — 1 DELETE, 15 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Documents 19
GET
/api/v1/signings/{signingId}/documents
Retrieve signing document IDs. This endpoint fetches the document IDs associated with the provided signing ID.
GetDocuments 1 param → 200default
PATCH
/api/v1/signings/{signingId}/documents/{documentId}
Apply a layout to a document within a specific signing.
ApplyLayout 3 params body → 200400404default
GET
/api/v1/signings/{signingId}/documents/s
Retrieve the fully executed combined signing package PDF.
GetFinalSigningDocument 1 param → default
GET
/api/v1/signings/{signingId}/documents/s/url
Retrieve the URL to a fully executed combined signing package PDF.
GetFinalSigningDocumentUrl 1 param → 200default
GET
/api/v1/signings/{signingId}/documents/sc
Retrieve the signing certificate for a specific signing.
GetSigningCertificate 1 param → default
GET
/api/v1/signings/{signingId}/documents/ls
Retrieve the latest signed document for a specific signing.
GetLatestSignedDocument 1 param → default
GET
/api/v1/signings/{signingId}/documents/ls/url
Retrieve the URL to latest signed document associated with the specified signing ID.
GetLatestSignedDocumentUrl 1 param → 200default
GET
/api/v1/documents/{encryptedDocumentId}/o
Retrieve the original document using its encrypted ID.
GetOriginalDocument 1 param → default
GET
/api/v1/documents/{documentId}/o/url
Retrieve the URL of the original document.
GetOriginalDocumentUrl 1 param → 200default
GET
/api/v1/documents/{encryptedDocumentId}/d
Retrieve the final version of a document using its encrypted ID.
GetFinalDocument 1 param → default
GET
/api/v1/documents/{documentId}/d/url
Retrieve the URL of the final version of a document.
GetFinalDocumentUrl 1 param → 200default
GET
/api/v1/documents/{encryptedDocumentId}/dc
Retrieve the certificate of a document using its encrypted ID.
GetDocumentCertificate 1 param → default
GET
/api/v1/documents/{documentId}/dc/url
Retrieve the URL of the document's certificate.
GetDocumentCertificateUrl 1 param → 200default
POST
/transact-workflow/v1/Documents
Upload a document
createDocument body → 201400401403404
GET
/transact-workflow/v1/users/{userId}/documents
List documents
getDocuments 2 params → 200400401403404
POST
/transact-workflow/v1/users/{userId}/documents
Upload a document (user-scoped)
createDocumentForUser 1 param body → 201400401403404
GET
/transact-workflow/v1/users/{userId}/documents/{documentId}
Get a document
getDocumentByKey 2 params → 200400401403404
DELETE
/transact-workflow/v1/users/{userId}/documents/{documentId}
Delete a document
deleteDocument 2 params → 204400401403404
GET
/transact-workflow/v1/users/{userId}/documents/file/{documentId}
Download a document file
getDocumentFile 2 params → 200400401403404

Schemas 4

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

Microsoft.AspNetCore.Mvc.ProblemDetails
object
5 properties
Authentisign.Services.Dtos.ErrorResponse
object
3 properties
Authentisign.Services.Dtos.DocumentLayoutDto
object
1 property 1 required
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Lone Wolf Technologies publishes across the network.

Lone Wolf Authentisign API
Lone Wolf Technologies Accounts API
Lone Wolf Technologies Authentication API
Lone Wolf Technologies Authorization API
Lone Wolf Technologies Business Contact API
Lone Wolf Technologies Business Contacts API
Lone Wolf Technologies C Cs API
Lone Wolf Technologies Classification API
Lone Wolf Technologies Classifications API
Lone Wolf Technologies Client Contact API
Lone Wolf Technologies Client Contacts API
Lone Wolf Technologies Commission API
Where this information came from

This is an independent, third-party profile of Lone Wolf Technologies Documents 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.