Get all transaction schedules 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
GET /api/v1/plans/{plan_uuid}/transaction-schedule
Personal access token & O auth2

Headers

  • X-PLANNR-ACCOUNT-UUID string

Path parameters

  • plan_uuid string Required

Query parameters

  • filter[uuid] string

    Filter by a comma separated list of UUIDs.

  • filter[subaccount] string

    Comma separated list of sub account UUIDs to filter by

  • filter[holding] string

    Comma separated list of holding UUIDs to filter by

  • filter[type] string

    Comma separated list of types to filter by

  • filter[sub_type] string

    Comma separated list of sub-types to filter by

  • filter[date_from] string

    Get transactions from a date.

  • filter[date_to] string

    Get transactions to a date.

  • filter[amount_from] string

    Get transactions greater than or equal to an amount in pennies.

  • filter[amount_to] string

    Get transactions less than or equal to an amount in pennies.

  • sort string

    Field to sort by. Valid fields are [created_at, updated_at, type, amount, start_date, next_transaction_date]. Negative sign to denote DESC. Defaults to '-start_date'.

  • per_page integer

    Number of results to return with pagination (Default 15. Max 500).

Responses

  • 200 application/json
    Hide response attribute Show response attribute object
    • data array[object]
      Hide data attribute Show data attribute object
      • message string
GET /api/v1/plans/{plan_uuid}/transaction-schedule 
curl \
 --request GET 'https://api.plannrcrm.com/api/v1/plans/6ff8f7f6-1eb3-3525-be4a-3932c805afed/transaction-schedule' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "X-PLANNR-ACCOUNT-UUID: {YOUR_PLANNR_ACCOUNT_UUID}"
Response examples (200) 
{
  "data": [
    {
      "message": "Plan is being deleted."
    }
  ]
}