Create an FCA Number 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/firm/{firm}/fca
Personal access token & O auth2

Headers

  • X-PLANNR-ACCOUNT-UUID string

Path parameters

  • firm string Required

    The firm.

application/json

Body

  • fca_number integer Required

    An FCA Number in a 6 or 7-digit format

Responses

  • 201 application/json
    Hide response attributes Show response attributes object
    • uuid string

      The UUID of the resource.

    • fca_number integer

      FCA Number

    • status string

      FCA Number Status, possible values are pending, verified and rejected

    • rejected_reason string

      Reason for rejection

    • actioned_at string

      DateTime FCA Number was verified or rejected
POST /api/v1/firm/{firm}/fca 
curl \
 --request POST 'https://api.plannrcrm.com/api/v1/firm/architecto/fca' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --header "X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}" \
 --data '{"fca_number":123456}'
Request examples 
# Headers
X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}

# Payload
{
  "fca_number": 123456
}
Response examples (201) 
{
  "uuid": "db1adc04-6000-4194-9e8a-93852b7e2a00",
  "fca_number": 123456,
  "status": "verified",
  "rejected_reason": "Reason for rejection",
  "actioned_at": "2026-06-08T16:08:01+01:00"
}