Add signing participants (batch)

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/api/v3/users/{userId}/participants/batch
Bearer auth & Subscription key

Adds multiple participants to a signing in a single request. The type field on each participant controls their role (e.g. signer vs. carbon-copy recipient).

Path parameters

  • userId string(uuid) Required

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

application/json

Body Required

  • signingId string(uuid) Required

    GUID of the signing the participant is added to.

  • firstName string Required

    Participant first name.

  • middleName string

    Participant middle name.

  • lastName string Required

    Participant last name.

  • email string(email) Required

    Participant email address.

  • type integer Required

    Participant role code. Observed values: 1 and 0 — these appear to distinguish signer from carbon-copy recipient roles. TODO: confirm the code-to-role mapping and document all values.

  • staticSignatureEnabled boolean

    Whether static (typed) signatures are allowed.

  • scriptedSignatureEnabled boolean

    Whether scripted (drawn) signatures are allowed.

  • imageSignatureEnabled boolean

    Whether image signatures are allowed.

Responses

  • 201

    Participants added.

  • 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/api/v3/users/{userId}/participants/batch 
curl \
 --request POST 'https://api.pre.lwolf.com/authentisign/v3/api/v3/users/{userId}/participants/batch' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "lw-subscription-key: $API_KEY" \
 --header "Content-Type: application/json" \
 --data '[{"signingId":"string","firstName":"string","middleName":"string","lastName":"string","email":"hello@example.com","type":42,"staticSignatureEnabled":true,"scriptedSignatureEnabled":true,"imageSignatureEnabled":true}]'
Request examples 
[
  {
    "signingId": "string",
    "firstName": "string",
    "middleName": "string",
    "lastName": "string",
    "email": "hello@example.com",
    "type": 42,
    "staticSignatureEnabled": true,
    "scriptedSignatureEnabled": true,
    "imageSignatureEnabled": true
  }
]
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"
}