List form libraries

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

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

GET /forms-design/api/users/{userId}/libraries

Bearer auth & Subscription key

Returns the form libraries available to the specified user, including field schema information.

Path parameters

userId string(uuid) Required

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

Responses

200

Successful response
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.

GET /forms-design/api/users/{userId}/libraries

curl \
 --request GET 'https://api.pre.lwolf.com/forms-design/api/users/{userId}/libraries' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "lw-subscription-key: $API_KEY"

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"
}