Partner-only portal APIs: what investors can do instead

An investor in a fund whose portal runs on eFront put the question plainly: "So I must sign a contract with eFront? I just want the capital call notice." The registry had marked the eFront API as partner-only, and the label read like a door the investor had to unlock.

What the access statuses mean for an investor

Every registry entry records a status per access channel: web, API, MCP, SFTP, webhooks and email notifications. The schema defines the values. Here is what each one means if you are the LP trying to get your own documents. Counts are for the API channel across all 63 entries.

• Available Documented and self-serve. You can read the docs and request credentials. Check the audience field: some available APIs are still meant for GPs, not LPs. 6 entries.
• Partner only The API exists but needs a commercial agreement. The audience field says who may sign one. When the audience is GP, fund administrator or distribution partner, an investor cannot obtain credentials on their own. 24 entries.
• Beta Released to a limited group, subject to change. Useful to watch, risky to build a process on. 0 entries.
• Planned Announced, not yet released. 1 entry.
• Not offered Confirmed absent. Someone checked and found no API. 6 entries.
• Unknown Nobody has checked yet. This is not a negative finding. It means the research is open. 26 entries.

The audience field matters as much as the status. Of the 24 partner-only APIs in the registry, 4 list investors among the audience. For the rest, partner-only effectively means "not for LPs".

Why vendors gate their APIs

Gating is a normal consequence of how these products are sold, not a judgment about investors.

• The customer is the GP or administrator. Portal software is licensed to the firm that runs the fund or its administration. That firm decides which investors see which documents, and it pays for the platform. An API is part of that commercial relationship.
• Contracts define who may access data. The licence, the administration agreement and the fund documents set out who handles investor data and on whose instructions. A vendor that issued credentials directly to investors would step outside those agreements.
• Data protection. Under rules such as the GDPR, the firm that collects investor data generally decides how it is used, and a software provider processes it on that firm's instructions. Opening a separate channel to each investor would need that firm's consent and controls.
• Support and security. Each API client needs onboarding, monitoring and support. Many portals are deployed per GP or administrator, so a single investor-facing API would have to span many separate instances.

Worked example: eFront Investment Café

The registry entry for eFront Investment Café reads as follows. Vendor: BlackRock eFront. Category: LP portal. The entry is community research with verification status unverified.

API

Partner only

API audience

GP, Fund administrator

Email notifications

Available

SFTP

Unknown

MCP

Unknown

Exports

PDF, XLSX

Automation policy

Unknown

Difficulty

4 / 5: Web login only, exports possible

The API note in the entry says: "Press material cites API capabilities for sync with the eFront back office. No public docs. Also distributed by Apex Group." The general note adds: "No LP-side programmatic access identified." In other words, the API that exists is described as back-office integration for the GP or administrator, and the registry has found no route for an investor to obtain API credentials.

Investors rarely meet eFront directly. They meet a portal branded and run by a GP or an administrator. The registry lists these known deployments:

• Lakestar Investor Reporting Portal: operator Lakestar, administrator Aztec Group, CH (confirmed)
• Lakestar Investor Café: operator Lakestar, CH (confirmed)
• Investment Café: operator Funds administered by Apex Group, administrator Apex Group, BM (confirmed)
• Investment Café: operator Funds administered by Ocorian, administrator Ocorian, JE (confirmed)

Take the case from the opening. An investor in a Lakestar fund whose reporting portal is run by Aztec Group on eFront has a relationship with Lakestar, set out in the fund documents, and through Lakestar with Aztec Group as administrator. Aztec Group, not the investor, is eFront's customer for that portal. The request to get notices in another way therefore goes to the GP or administrator. A contract with the software vendor is not needed for it.

Practical routes to your notices today

1. Parse the notification emails

Most portals email investors when a new document is posted. 10 of the 24 partner-only entries list email notifications as available, eFront Investment Café among them. A mailbox rule or a small parser can detect the notice, record the fund, amount type and due date from the subject or body where present, and alert your team to fetch the PDF. The guide to automating capital call and distribution notices covers the setup in detail.

2. Ask the GP or administrator to deliver to you

Administrators already distribute notices to investors, so the request is about where and in what form, not about new access. Ask for delivery to a nominated email address or SFTP folder, ideally with a structured file next to the PDF. The ILPA Capital Call & Distribution Template gives both sides a shared field list, so the request is easy to specify. A short template:

Subject: Delivery of capital call and distribution notices for [investor entity]

Dear [Investor Relations / Investor Services team],

We are invested in [fund name] through [investor entity name, investor ID if known].
We currently receive notices through the investor portal. To support our internal
processing, could you please also deliver the following documents for this account:

- capital call notices
- distribution notices
- capital account statements and quarterly reports

to [nominated email address, e.g. notices@investor.example]
or to an SFTP folder we provide (we can share host details and a public key).

Where possible, please include the data in the ILPA Capital Call & Distribution
Template format (or the ILPA Reporting Template for statements) as XLSX or CSV,
alongside the PDF notice.

Please let us know if you need a signed request, a side letter reference or
additional verification before setting this up.

Kind regards,
[Name, role, entity]

Send it to the investor relations contact named in your fund documents or the administrator's investor services team. Keep it narrow: a specific fund, a specific entity and a specific destination are easier to approve.

3. A GP data feed

Some GPs and administrators provide periodic data files to investors or to the investor's own reporting platform. If you already use a portfolio monitoring or reporting provider, ask whether it receives feeds from your GP or administrator, and whether your fund can be added. This route depends on the GP, not on the portal vendor.

4. Browser automation, only if the terms allow it

Logging in with a script on your own account is a fallback. It breaks with every portal change and multi-factor prompt, and it may be against the portal terms. Check the automation policy in the registry entry and read the terms yourself. For eFront Investment Café the registry records the policy as unknown, which means it has not been checked. Where an entry says prohibited, connectors must not automate the login.

How the open protocol changes the picture

The routes above all work around the same gap: there is no investor-facing interface. The Open Investor Portal Protocol (OIPP) fills it. The portal operator, the GP or administrator running the instance, enables one standard endpoint and a "Connect with OpenInvestorPortal" option in the portal they already run. Each investor then links their own cryptographic key to the account they already have, and signs every request with it.

• No separate contract per investor. The operator enables the endpoint once, for all its investors.
• No passwords or tokens leave the portal, and OpenInvestorPortal never holds portal data in the default mode.
• The operator decides which capabilities a link can read, and can revoke it at any time.
• Capital call and distribution payloads align with the ILPA templates, so the data is the same across portals.

Partner APIs stay as they are, serving GPs and administrators. The protocol adds the investor side. You can see which portals support it, and which APIs investors can use today, in the overview of investor portals with an API or MCP server.

Frequently asked questions

Sources

Registry data: the eFront Investment Café entry, registry/deployments.json and research/assessments.json, plus the schema definitions of each status. External sources:

• eFront Investment Café product page: https://www.efront.com/alternative-investment-software/efront-investment-cafe/
• Apex Group, investor portal technology: https://www.apexgroup.com/technology-platforms/investor-portal/
• Apex Group, client portals: https://www.apexgroup.com/client-portals/
• Ocorian, investor services: https://www.ocorian.com/service/investor-services
• Ocorian partners with BlackRock's eFront (press release via Mondaq): https://www.mondaq.com/PressRelease/86414/Ocorian-Partners-With-Blackrocks-Efront-Suite-For-Its-Global-Funds-Administration-Platform
• ILPA Capital Call & Distribution Template: https://ilpa.org/industry-guidance/templates-standards-model-documents/ilpa-templates-hub/ilpa-capital-call-distribution-template/
• ILPA templates hub: https://ilpa.org/industry-guidance/templates-standards-model-documents/updated-ilpa-templates-hub/

Not affiliated with eFront, BlackRock or any listed vendor. Product names identify the listed products only.