Skip to main content

​
New Features

​
API Guides

A new API Guides section is now available in Method’s documentation. This comprehensive, concept-first companion to the API Docs helps product and business teams understand how Method’s platform works and how best to configure Method’s APIs for their use case. The API Guides include:
  • How Method Works: How Method leverages multiple data sources to power identity verification, account discovery, and data retrieval.
  • Core Products: In-depth guides for each product area, covering payload details, subscription behaviors, error handling, and edge cases.
  • Use Case Guides: Implementation frameworks for the most common use cases: debt consolidation and balance transfers for lenders, card linking and checkout for commerce platforms, and liability dashboards and bill pay for personal finance apps, with step-by-step flows mapping Method products to each stage of the customer journey.
These guides are designed to complement the existing API Reference documentation by providing the conceptual foundation and product context that teams need to plan and build their integrations effectively.

​
Improvements

​
Webhook Idempotency Headers

You can now easily deduplicate retried or replayed webhook deliveries. All outbound webhooks now include a method-webhook-delivery-id header, containing a unique identifier for each webhook delivery. If your endpoint receives the same delivery twice (due to network timeouts, retries, or replays), the method-webhook-delivery-id value will be identical, letting you skip duplicate processing with a simple lookup.
Sample Headers
{
  "method-webhook-delivery-id": "obwh_yBaCP3DQxJ4",
  "content-type": "application/json"
}
For more information, visit the Webhooks API documentation.

​
Simulations API

Connect Webhook in Account Opened Simulation The POST /simulate/events endpoint for account.opened events now also sends the connect.create webhook as part of the simulation, aligned with the endpoint’s production behavior. Previously, simulating an account.opened event only fired the account.opened webhook. This gap meant customers couldn’t fully test their Connect-to-Account-Opened integration pipeline in dev. Now, when you simulate account.opened, both webhooks fire in sequence:
  1. connect.create — the Connect session that discovered the account
  2. account.opened — the account itself becoming available
This enables true end-to-end testing of workflows that listen for Connect completion and then act on the resulting accounts.
POST /simulate/events
{
  "type": "account.opened",
  "entity_id": "ent_au22b1FBFJbp8",
  "account_id": "acc_Dz3E8r4mJ7xKn"
}
For more information, visit the Simulations API documentation.