Securitize Connect API (Securitize iD)

OAuth-based identity API that lets partners add "Log in with Securitize iD" to their own application and, with investor consent, retrieve verified KYC/KYB/AML identity data — investor information, verification details, investor documents, legal signers, and registered wallets. Scopes are limited to info, details, and verification. Documented endpoint surface only; Securitize publishes no machine-readable specification for this API and the Swagger reference its docs link to now returns 404.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/securitize-connect-api-securitize-id"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
name: Securitize Connect API (Securitize iD)
description: OAuth-based identity API that lets partners add "Log in with Securitize iD" to their own
  application and, with investor consent, retrieve verified KYC/KYB/AML identity data — investor information,
  verification details, investor documents, legal signers, and registered wallets. Scopes are limited
  to info, details, and verification. Documented endpoint surface only; Securitize publishes no machine-readable
  specification for this API and the Swagger reference its docs link to now returns 404.
humanURL: https://sec-connect-api-docs.securitize.io/
baseURL: https://sec-id-api.securitize.io/
tags:
- Identity Verification
- KYC
- AML
- Authentication
- Single Sign-On
tags_raw:
- identity-verification
- kyc
- aml
- oauth
- single-sign-on
properties:
- type: Documentation
  url: https://sec-connect-api-docs.securitize.io/
- type: GettingStarted
  url: https://sec-connect-api-docs.securitize.io/accessing-the-apis
- type: Authentication
  url: https://sec-connect-api-docs.securitize.io/authentication-1/authentication
- type: OAuthScopes
  url: scopes/securitize-scopes.yml
- type: LLMsTxt
  url: llms/securitize-connect-api-llms.txt
x-evidence:
  fetched: '2026-08-05'
  spec_probe: https://sec-id-api.sandbox.securitize.io/swagger
  spec_probe_status: 404
  note: The Connect API docs link to a Securitize iD Swagger at https://sec-id-api.sandbox.securitize.io/swagger#/
    as "the reference documentation"; that path and every /swagger-json, /openapi.json and /api-json variant
    on both the sandbox and production hosts returned 404 on 2026-08-05. No OpenAPI was authored on the
    provider's behalf.