# FINRA API Platform API: access, auth, sandbox and MCP (checked Oct 2026)

> FINRA's API Platform exposes Query, Notification and Submission APIs plus fileX file transfer, with public docs and a dataset catalog. Credentials are created in the API Console in FINRA Gateway; a Mock credential and a $0 Public credential exist, and a Firm credential is $1,650 per month.

- Vendor: Financial Industry Regulatory Authority (FINRA) (Financial Industry Regulatory Authority (FINRA))
- Website: https://developer.finra.org/
- Category: Regulatory adviser data (core)
- API access: Open: self-serve docs and keys
- Last checked: 2026-10-17
- Id: `finra-api` · JSON: https://wealthtech.dev/products/finra-api.json

## Developer surface

| Field | Value | Source and quote | Checked |
|---|---|---|---|
| API access | Open: self-serve docs and keys | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/docs) "if you are logged-in to the API Console as an Individual User, the allowable selections will include mock and public." | 2026-10-17 |
| Developer docs | https://developer.finra.org/docs | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/) "The FINRA Developer Center is a strategic FINRA initiative to support the automation goals of member firms and the broader financial services industry." | 2026-10-17 |
| API style | REST | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/docs) "All API requests must use HTTPS protocol." | 2026-10-17 |
| Authentication | OAuth 2.0 (client credentials) | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/docs) "The FINRA API Platform authentication and authorization scheme is based on OAuth 2.0." | 2026-10-17 |
| How to get access | Firm users: the firm's Super Account Administrator requests the API Console entitlement, then credentials are created in the API Console in FINRA Gateway. Individuals can create an account for a Test Credential with mock data. | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/fees) "Create an Individual Account and start building right away with a Test Credential and mock data." | 2026-10-17 |
| Sandbox | Yes, self-serve | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/fees) "Create an Individual Account and start building right away with a Test Credential and mock data." | 2026-10-17 |
| Rate limits | Each FIRM credential has a data limit of 10GB per month. FINRA reserves the right to limit requests; the docs list a Request Throttling section but the numbers were not in the captured text. | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/docs) "each FIRM Credential has a data limit of 10GB per month" | 2026-10-17 |
| Webhooks | No | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/products/notification-api) "The Notification API  allows third-party systems to detect changes related to FINRA datasets/resources via polling." | 2026-10-17 |
| SDKs | Not found | Not found. No SDKs or client libraries mentioned. Pages read: developer.finra.org home, /docs, /fees, /support, /catalog, /products and the Query and Notification API product pages. The terms-of-service page returned HTTP 429 to the capture tool. No SDKs or client libraries mentioned. Pages read: developer.finra.org home, /docs, /fees, /support, /catalog, /products and the Query and Notification API product pages. The terms-of-service page returned HTTP 429 to the capture tool. | 2026-10-17 |
| OpenAPI spec | Not found | Not found. No OpenAPI spec or Swagger file linked. Pages read: developer.finra.org home, /docs, /fees, /support, /catalog, /products and the Query and Notification API product pages. The terms-of-service page returned HTTP 429 to the capture tool. No OpenAPI spec or Swagger file linked. Pages read: developer.finra.org home, /docs, /fees, /support, /catalog, /products and the Query and Notification API product pages. The terms-of-service page returned HTTP 429 to the capture tool. | 2026-10-17 |
| Partner program | On Behalf Of (OBO) feature for authorized third-party vendors | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/docs) "The On Behalf Of (OBO) feature is available at the FINRA Enterprise level and enables authorized third-party vendors (or another firm) to access data and perform submissions on behalf of FINRA member firms" | 2026-10-17 |
| Public integration list | https://developer.finra.org/catalog | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/) "Explore our featured products and catalog of datasets." | 2026-10-17 |
| Ways to connect | Native API, File exchange | Checked on the source's own page. [developer.finra.org](https://developer.finra.org/) "The Submission API allows third-party systems to submit filings and other data to FINRA via a standard submission interface." | 2026-10-17 |

## MCP servers and AI connectors

None recorded on public pages we checked.

## What the docs don't say

- The FAQ answers on the support page are collapsed and were not in the captured text, so statements about which registration data is limited were not verified.
- The docs list Request Throttling and Responsible Use Guidelines sections, but no request-per-second figure was in the captured text.
- The fees page shows $1,650 per month for a Firm credential and $0 for a Public credential, with a per-dataset availability grid; the grid's cell meanings were not verified.
- No BrokerCheck API is named on the catalog and product pages read.

## Changes

No changes recorded since this record was first published.
---
Source: https://wealthtech.dev/products/finra-api · Facts licensed CC BY 4.0 (attribution "wealthtech.dev"). Every fact states where it was checked and when; check the source before relying on it.