List offices

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
GET /platform/v1/clients/{clientId}/offices
Bearer auth & Subscription key

Returns the offices belonging to the specified client account.

Path parameters

  • clientId string(uuid) Required

    GUID of the Lone Wolf client (tenant) account.

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 /platform/v1/clients/{clientId}/offices 
curl \
 --request GET 'https://gateway.lwolf.com/platform/v1/clients/{clientId}/offices' \
 --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"
}