Create expectations 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/statement-transaction/create-expectations
Personal access token & O auth2

Bulk action create expectations for incoming statement transactions. Useful when a provider statement has historic transactions which Plannr has not generated the expectations for. The client and policy for this transactions must exist within Plannr.

Headers

  • X-PLANNR-ACCOUNT-UUID string
application/json

Body

  • statement_transactions array[string(uuid)] Required

    Array of unreconciled statement transactions to bulk create matching expectations.

Responses

  • 204 application/json
  • 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/statement-transaction/create-expectations 
curl \
 --request POST 'https://api.plannrcrm.com/api/v1/statement-transaction/create-expectations' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --header "X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}" \
 --data '{
  "statement_transactions": [
    "33a2bec7-152c-4d97-9ad9-4b21f7cd4b3d",
    "af31f646-68b7-4775-8c49-a90ac4010f07",
    "b30fa22f-e403-41e6-8007-f983c76efc54"
  ]
}'
Request examples 
# Headers
X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}

# Payload
{
  "statement_transactions": [
    "33a2bec7-152c-4d97-9ad9-4b21f7cd4b3d",
    "af31f646-68b7-4775-8c49-a90ac4010f07",
    "b30fa22f-e403-41e6-8007-f983c76efc54"
  ]
}
Response examples (204) 
{}
Response examples (422) 
{
  "message": "The given data was invalid.",
  "errors": {
    "field": [
      "The field is invalid."
    ]
  }
}