Read-only catalogue of fund allocations available to workplace workers

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://docs.getpenfold.dev/mcp

Standard setup for AI tools providing an mcp.json file

{
  "Penfold Partner API MCP server": {
    "url": "https://docs.getpenfold.dev/mcp"
  }
}

GET /fund_allocations

O auth2 client credentials

Read-only catalogue of fund allocations available to workplace workers. Each item is mapped from the FundAllocation row (nullable fields are returned as null). annual_return_percent is intentionally omitted (not shown in the member app; compliance TBD).

Responses

200 application/json

Fund allocation catalogue retrieved successfully.
Hide response attributes Show response attributes object
- id string Required
- name string Required
- description string | null
- provider string | null
- risk_level integer | null
- indicative_annual_fee_percent number Required
  
  Indicative combined annual fee percentage (Penfold administration fee at the lowest pot threshold plus fund manager charge), using the same calculation as the member app fund wizard but not personalised per worker or employer bespoke rates. Catalogue entries assume a workplace worker with no pot value.
401 application/json

Unauthorized.
Hide response attribute Show response attribute object
- error string
  
  A descriptive error message.
405 application/json

Method not allowed
Hide response attribute Show response attribute object
- error string
  
  A descriptive error message.

GET /fund_allocations

curl \
 --request GET 'https://payroll-api.getpenfold.dev/v4/fund_allocations' \
 --header "Authorization: Bearer $ACCESS_TOKEN"

Response examples (200)

[
  {
    "id": "string",
    "name": "string",
    "description": "string",
    "provider": "string",
    "risk_level": 42,
    "indicative_annual_fee_percent": 42.0
  }
]

Response examples (401)

{
  "error": "Bad request: invalid data provided."
}

Response examples (405)

{
  "error": "Bad request: invalid data provided."
}