Create a signing

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://apidocs.lwolf.com/doc/transact-api/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "Transact API MCP server": {
    "url": "https://apidocs.lwolf.com/doc/transact-api/mcp"
  }
}

Close
POST /authentisign/v3/users/{userId}/signings

Creates a new signing with one or more documents. The request is sent as multipart/form-data.

Path parameters

  • userId string(uuid) Required

    Unique identifier (GUID) of the acting user. All Transact Workflow resources are scoped to a user.

Query parameters

  • api-version string Required

    Authentisign API version. Use 3.

    Default value is 3.

multipart/form-data

Body Required

  • Name string Required

    Display name of the signing.

  • isOrdered boolean

    Whether participants must sign in order.

  • ExpirationDate string(date-time)

    Expiration date of the signing.

  • Files string(binary) Required

    Document file(s) to include in the signing.

  • CallbackUrl string(uri)

    Optional callback URL invoked on signing events.

  • TransactionId string(uuid)

    Optional GUID of the transaction to associate the signing with.

Responses

  • 201

    Signing created.

  • 400 application/json

    The request is malformed or contains invalid parameters.

    Hide response attributes Show response attributes object
    • error string

      Error code or short error name.

    • message string

      Human-readable error description.

  • 401 application/json

    The access token is missing, invalid, or expired.

    Hide response attributes Show response attributes object
    • error string

      Error code or short error name.

    • message string

      Human-readable error description.

  • 403 application/json

    The caller is not permitted to perform this operation.

    Hide response attributes Show response attributes object
    • error string

      Error code or short error name.

    • message string

      Human-readable error description.

  • 404 application/json

    The requested resource does not exist.

    Hide response attributes Show response attributes object
    • error string

      Error code or short error name.

    • message string

      Human-readable error description.

POST /authentisign/v3/users/{userId}/signings
curl \
 --request POST 'https://gateway.lwolf.com/authentisign/v3/users/{userId}/signings?api-version=3' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "lw-subscription-key: $API_KEY" \
 --header "Content-Type: multipart/form-data" \
 --form "Name=string" \
 --form "isOrdered=true" \
 --form "ExpirationDate=2026-05-04T09:42:00Z" \
 --form "Files=@file" \
 --form "CallbackUrl=https://example.com" \
 --form "TransactionId=string"
Response examples (400)
{
  "error": "string",
  "message": "string"
}
Response examples (401)
{
  "error": "string",
  "message": "string"
}
Response examples (403)
{
  "error": "string",
  "message": "string"
}
Response examples (404)
{
  "error": "string",
  "message": "string"
}