Plaid logo
Docs
ALL DOCS

API

  • Overview
  • Libraries
  • API versioning
  • Postman Collection
  • Webhooks
Payments and Funding
  • Auth
  • Signal and Balance
  • Identity
  • Transfer
  • Investments Move
  • Payment Initiation (Europe)
  • Virtual Accounts
Financial Insights
  • Transactions
  • Investments
  • Liabilities
  • Enrich
KYC/AML and anti-fraud
  • Look up Dashboard users
  • Identity Verification
  • Monitor
  • Protect
  • Beacon (beta)
Instant Onboarding
  • Layer
Credit and Underwriting
  • Consumer Report (by Plaid Check)
  • Assets
  • Statements
  • Income
Fundamentals
  • Items
  • Accounts
  • Institutions
  • Sandbox
  • Link
  • Users
  • Consent
  • Network
  • OAuth
Partnerships
  • Processor tokens
  • Processor partners
  • Reseller partners
Plaid logo
Docs
Close search modal
Ask Bill!
Ask Bill!
Hi! I'm Bill! You can ask me all about the Plaid API. Try asking questions like:
    Note: Bill isn't perfect. He's just a robot platypus that reads our docs for fun. You should treat his answers with the same healthy skepticism you might treat any other answer on the internet. This chat may be logged for quality and training purposes. Please don't send Bill any PII -- he's scared of intimacy. All chats with Bill are subject to Plaid's Privacy Policy.
    Plaid.com
    Log in
    Get API Keys
    Open nav

    User API migration

    Information on new user APIs

    =*=*=*=

    Introduction to Plaid's new User APIs

    Plaid is updating our user APIs to support the next generation of user-based products - such as Plaid Protect - and to create a more unified and consistent experience across our platform. These updates improve multi-product compatibility, simplify debugging, and ensure user identifiers behave consistently across all Plaid products. If you're beginning a new CRA integration in December 2025 or later, you’ll use these updated APIs to build your integration.

    If you are an existing customer (integrated prior to December 2025), here’s what you need to know:

    • No action is required.
    • Your existing integration remains fully supported. Plaid is not removing support and your integration will continue to function as expected.
    • We’ll share optional migration steps in Q1 2026. Only after that point will existing clients be able to migrate.
    =*=*=*=

    What's new

    Important: Customers with existing Plaid integrations cannot yet migrate to this new flow. The API changes below are currently described for informational purposes only.

    • When calling /user/create, the response includes a single user_id instead of a user_token and a user_id. This single user_id is used instead of the user_token to identify the user throughout the Plaid API, including when calling CRA or Link endpoints or when receiving webhooks.
    • The CRA user uses identity object (instead of the consumer_report_user_identity object) in the /user/create and /user/update request body. This identity object has a different schema than the consumer_report_user_identity object.
    • The webhooks CHECK_REPORT_READY and CHECK_REPORT_FAILED have been renamed to USER_CHECK_REPORT_READY and USER_CHECK_REPORT_FAILED.
    • Coming soon, the user APIs will include net-new endpoints and additional functionality to simplify user management.
    =*=*=*=

    Summary

    New clients integrating beginning December 10, 2025 or later should use the new user_id based implementation currently described in the docs. Existing clients should take no action at this time. Migration will be optional and available after Q1 2026.

    More information will be provided about the new user APIs in Q1 2026. In the meantime, if you have questions about timing, readiness, or how Plaid's new user APIs might benefit your integration, contact your Plaid Account Manager.

    Developer community
    GitHub
    GitHub
    Stack Overflow
    Stack Overflow
    YouTube
    YouTube
    Discord
    Discord