Securitize: API, MCP and document access

Securitize is an investment platform or marketplace from Securitize, Inc., used globally for private equity, private credit and real estate. The registry rates investor document access 3 of 5 (exports, SFTP or email feeds, no investor-side API): the API is available for partners and GPs, and a vendor MCP server is available.

Vendor: Securitize, Inc.Unverified community researchUpdated
Vendor
Securitize, Inc. United States
Category
Marketplace
Regions
North America, Global, APAC
Asset classes
Private equity, Private credit, Real estate, Other
Investor access difficulty
3 / 5 Exports, SFTP or email feeds, no investor-side API
Automation policy
Unknown (terms not checked)
Verification
Unverified community research
Last updated

Access channels

Each way to get data out of Securitize, as recorded in the registry. "Unknown" means nobody has checked yet, not that the channel is missing.

ChannelStatusAuthDocsNotes
Web portalAvailableNot recordedNot recordedSecuritize iD investor login; MFA methods not confirmed from public docs.
APIAvailableOAuth 2.0 authorization code; API keyDocs Style: REST. Audience: partners and GPs. Sandbox available. Public docs: Connect API (OAuth provider 'Log in with Securitize iD'; with investor access token + app secret an integrating app can list the investor's documents and get temporary download links: GET https://sec-id-api.securitize.io/v1/{clientId}/investor/documents), Domain API (issuers/brokers: investors, KYC, documents, investments, transactions, issuances; sandbox public-api.sandbox.securitize.io), Webhooks API, APAC API (api-key). Credentials are issued to applications/issuers, not to investors directly.
MCP serverAvailableNoneNot recordedTransport: Streamable HTTP. Maintained by the vendor. Endpoint: https://mcp.securitize.io. Per API Evangelist profile (2026-08-05): public, unauthenticated 'Securitize Connector' MCP server with 5 tools; not verified against vendor docs; not in official MCP registry.
SFTPUnknownNot recordedNot recordedNot recorded
WebhooksAvailableNot recordedDocs Webhook API: KYC/KYB, accreditation and subscription-agreement updates (issuer-facing).
Email notificationsAvailableNot recordedNot recordedNot recorded

How an investor gets documents today

Well-documented public APIs with OAuth and sandbox; an app can retrieve an investor's documents with the investor's OAuth token, but credentials go to applications/issuers and fund reporting data sits in the issuer Domain API; third-party reports a public MCP server. Whether an investor can get API access is not documented.

  • The API is for partners and GPs, not for investors. Ask the GP or administrator to deliver documents to a nominated email address or SFTP folder, or to send a data feed from their side of the API. See Partner-only portal access explained.
  • MCP server. An MCP server is available. The registry has not confirmed that an investor account can connect to it, so check with Securitize, Inc. before relying on it.
  • Email notifications. Turn on notifications and route them to a monitored mailbox, so new notices trigger your own processing. See How to automate capital call notices.
  • Manual download. Download documents from the web portal (exports recorded: PDF and JSON).
  • Check the terms. The registry has not reviewed the terms for automated access. Read them before automating anything.

Background: How to automate capital call notices and Partner-only portal access explained.

Capabilities and terms

What Securitize exposes to investors, according to the research: documents, distribution notices, subscriptions, KYC and onboarding, cap table and tax documents (K-1 and similar).

  • Export formats: PDF, JSON
  • Standards: OAuth 2.0, OpenAPI
  • Terms of service: No terms link recorded
  • Automation policy: Unknown (terms not checked)

OIPP status

Not yet on the open protocol. Securitize does not implement the Open Investor Portal Protocol (OIPP), the open API any portal can implement so investors reach every portal through one interface with their own key.

For Securitize, Inc.. If anything on this page is wrong or out of date, correct the entry by pull request to the registry or by email. A pull request from a vendor-owned domain marks the entry vendor verified. Implementing OIPP lets investors and their agents fetch documents without scraping, under your own access rules. See the registry badge for how to show your status.

For Securitize, Inc.: show your listing

If you operate Securitize, you can link to this registry entry from your developer, security or integrations page with the badge below. It links back here, so investors and their operations teams can see how access works.

Securitize: Listed on OpenInvestorPortal

<a href="https://openinvestorportal.com/portals/securitize/" title="Securitize on OpenInvestorPortal"><img src="https://openinvestorportal.com/badge/securitize.svg" alt="Securitize: Listed on OpenInvestorPortal" width="220" height="28"></a>

This entry is not vendor verified yet. Confirm it with a pull request from an email on your company domain, or with a DNS TXT record. See how the badge and vendor verification work.

Sources and notes

Confidence: high on public API docs (vendor GitBook/Postman). The Connect API's investor-documents endpoints return identity/KYC documents (docType passport etc.), not fund statements; fund-level reports/distributions are managed through the issuer Domain API/Control Panel. Investor-side API: indirect only (an app acting with the investor's OAuth token). MCP server existence from third-party profile only. Terms not reviewed.

Sources checked for the assessment:

Questions

Does Securitize have an API?

Yes. Securitize has a REST API for partners and GPs. Public documentation is linked on this page. Investors are not listed among its users, so an LP usually cannot get credentials directly.

Does Securitize have an MCP server?

Yes. An MCP server is available for Securitize. Securitize, Inc. maintains it. The registry has not confirmed that an investor account can use it.

Can investors download documents from Securitize programmatically?

The registry rates investor access 3 of 5: exports, SFTP or email feeds, no investor-side API. Well-documented public APIs with OAuth and sandbox; an app can retrieve an investor's documents with the investor's OAuth token, but credentials go to applications/issuers and fund reporting data sits in the issuer Domain API; third-party reports a public MCP server. Whether an investor can get API access is not documented. The usual route is delivery by the GP or administrator to a nominated email address, SFTP folder or data feed.

Independent community research. Not affiliated with Securitize, Inc.. Facts are unverified community research as of 2026-11-07.

Other investment platforms and marketplaces

Guides

More in the registry