Create a Field for a Life Stage Section for a Firm 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
POST /api/v1/expenditure-structure/field
Personal access token & O auth2

Path parameters

  • firm_uuid string Required

    The uuid of the Firm.

  • lifeStageSection_uuid string Required

    The uuid of the Life Stage Section.

application/json

Body

  • name string Required

    The name of the Life Stage Field.

  • life_stage_section_uuid string(uuid) Required

    The uuid of the parent Life Stage Section.

Responses

  • 200 application/json
    Hide response attributes Show response attributes object
    • uuid string
    • name string
    • section string
    • created_at string
    • updated_at string
  • 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
POST /api/v1/expenditure-structure/field 
curl \
 --request POST 'https://api.plannrcrm.com/api/v1/expenditure-structure/field' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --data '{
  "name": "Electricity",
  "life_stage_section_uuid": "b640a915-eb59-4d5c-bee6-6dd4a9b081e1"
}'
Request examples 
{
  "name": "Electricity",
  "life_stage_section_uuid": "b640a915-eb59-4d5c-bee6-6dd4a9b081e1"
}
Response examples (200) 
[
  {
    "uuid": "385f9897-590f-4b4b-8476-206e9a37994f",
    "name": "Electricity",
    "section": "Housekeeping Expenses",
    "created_at": "2026-10-29T17:25:04+00:00",
    "updated_at": "2026-10-29T17:25:04+00:00"
  }
]
Response examples (422) 
{
  "message": "The given data was invalid.",
  "errors": {
    "field": [
      "The field is invalid."
    ]
  }
}