Update a Transaction Contact

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/transactiondesk-api/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "TransactionDesk API MCP server": {
    "url": "https://apidocs.lwolf.com/doc/transactiondesk-api/mcp"
  }
}
Close
PATCH /v2/transactions/{transactionId}/contacts/{contactId}
Bearer auth

Updates one or more attributes of a specific transaction contact.

Path parameters

  • transactionId string(uuid) Required

    TransactionGUID

  • contactId string(uuid) Required

    ContactGUID

application/json

Body Required

  • id string(uuid)

    ContactGUID

  • transactionId string(uuid)

    TransactionGUID this contact is associated with

  • preferredName string

    Preferred name; overrides firstName/lastName on real estate forms

  • firstName string
  • middleName string
  • lastName string
  • fullAddress string

    Street number and name

  • city string
  • state string
  • zipCode string
  • phone string
  • fax string
  • cell string
  • email string(email)
  • company string
  • typeId string(uuid)

    Contact type GUID. See Glossary for values.

Responses

  • 200

    Contact updated successfully

  • 400 application/json

    Bad request

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • details array[string]
  • 401 application/json

    Unauthorized

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • details array
    • data
  • 404 application/json

    Contact not found

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • details array
PATCH /v2/transactions/{transactionId}/contacts/{contactId} 
curl \
 --request PATCH 'https://api.pre.transactiondesk.com/v2/transactions/{transactionId}/contacts/{contactId}' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --data '{
  "id": "805355ec-7f7d-413e-986a-c767ea0632da",
  "transactionId": "34bfff2a-d186-48c6-b09d-6c15232cfe26",
  "preferredName": "Bobby Jones",
  "firstName": "Robert",
  "middleName": "P",
  "lastName": "Jones",
  "fullAddress": "100 Wellington St.",
  "city": "London",
  "state": "ON",
  "zipCode": "N6E B3B",
  "phone": "519-000-0000",
  "fax": "519-000-0001",
  "cell": "519-000-0002",
  "email": "bobbyjones@fakeemail.com",
  "company": "Bobby Jones Real Estate",
  "typeId": "918753cd-df9d-4a8c-b9c5-2d0115835ea0"
}'
Request examples 
{
  "id": "805355ec-7f7d-413e-986a-c767ea0632da",
  "transactionId": "34bfff2a-d186-48c6-b09d-6c15232cfe26",
  "preferredName": "Bobby Jones",
  "firstName": "Robert",
  "middleName": "P",
  "lastName": "Jones",
  "fullAddress": "100 Wellington St.",
  "city": "London",
  "state": "ON",
  "zipCode": "N6E B3B",
  "phone": "519-000-0000",
  "fax": "519-000-0001",
  "cell": "519-000-0002",
  "email": "bobbyjones@fakeemail.com",
  "company": "Bobby Jones Real Estate",
  "typeId": "918753cd-df9d-4a8c-b9c5-2d0115835ea0"
}
Response examples (400) 
{
  "code": 400,
  "message": "Request was not valid.",
  "details": [
    "string"
  ]
}
Response examples (401) 
{
  "code": 401,
  "message": "Unauthorized. The user is not authenticated.",
  "details": []
}
Response examples (404) 
{
  "code": 404,
  "message": "Item not found.",
  "details": []
}