Update a fact-find policy Run in API Explorer

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.plannrcrm.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json 
{
  "PlannrCRM MCP server": {
    "url": "https://apidocs.plannrcrm.com/mcp"
  }
}
Close
PUT /api/v1/circles/{circle_uuid}/fact-find-access
Personal access token & O auth2

This updates the fact-find access for a given member.

Path parameters

  • circle_uuid string Required
application/json

Body

  • account_uuid string(uuid) Required

    The UUID of the circle member account to attach the access to.

  • target_account_uuid string(uuid) Required

    The UUID of the circle member account that account_uuid will have access to.

  • has_fact_find_access boolean Required

    Boolean to allow/deny the access.

Responses

  • 422 application/json

    Validation error

    Hide response attributes Show response attributes object
    • message string Required

      A human-readable description of the error.

    • errors object

      Validation messages keyed by the field that failed.

      Hide errors attribute Show errors attribute object
      • * array[string] Additional properties
PUT /api/v1/circles/{circle_uuid}/fact-find-access 
curl \
 --request PUT 'https://api.plannrcrm.com/api/v1/circles/6ff8f7f6-1eb3-3525-be4a-3932c805afed/fact-find-access' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --data '{"account_uuid":"86b65051-d738-4a63-8d32-95782182b573","target_account_uuid":"c085e3aa-e6d1-44b2-adf5-dd8775fe3c7c","has_fact_find_access":true}'
Request examples 
{
  "account_uuid": "86b65051-d738-4a63-8d32-95782182b573",
  "target_account_uuid": "c085e3aa-e6d1-44b2-adf5-dd8775fe3c7c",
  "has_fact_find_access": true
}
Response examples (422) 
{
  "message": "The given data was invalid.",
  "errors": {
    "field": [
      "The field is invalid."
    ]
  }
}