Events
Collects the Method Financial resource change feed: account lifecycle, credit score, and credit health attribute events, each with a before/after diff.
Sync Type: Incremental
Prerequisites
Before configuring this input, you need:
- A Method account with access to the Method Dashboard.
- An API key (
sk_...) for the environment you want to connect — Production, Sandbox, or Development. Each environment issues its own key, so make sure you generate the key for the environment you configure in Monad.
Authentication
This input authenticates with a static Bearer API key issued from the Method Dashboard for the selected environment, plus a pinned Method-Version header that Monad sends on every request so API behavior doesn't drift as Method ships new default versions.
To obtain the API key:
- Log in to the Method Dashboard.
- Switch to the environment (Production, Sandbox, or Development) you want to connect.
- Copy the API key (
sk_...) for that environment.
Configuration
Settings
| Setting | Type | Required | Description |
|---|---|---|---|
| Environment | string | Yes | The Method environment to connect to. Each environment issues its own API key. Options: Production (default), Sandbox, Development. |
| Resource Type | string | No | Only collect events for this resource type. Options: All (default), Payment, Entity, Account, Credit Score. |
| Event Type | string | No | Only collect events of this exact type, e.g. account.opened, credit_score.increased, or entity_attribute.credit_health_payment_history.decreased. Leave empty to collect every event type. |
| Backfill Start Time | string | No | The date to start fetching events from on the first run. If not specified, the first run collects events from the start of the current day (UTC). |
| Use Synthetic Data | boolean | No | Generate synthetic data for testing instead of connecting to the real Method API. Defaults to false. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
| API Key | string | Yes | The Method API key (e.g. sk_...) for the selected environment. Found in the Method Dashboard. |
How It Works
Method's GET /events feed lists events newest first. Each run requests events from the timestamp of the newest event collected so far. On the first run, that's the Backfill Start Time, or the start of the current day (UTC) if none is set. Method filters that start date by day only, so Monad discards any events from that day that are earlier than the start time.
Monad follows Method's pagination cursor through the results. A run stops when Method returns no more pages, or when a page reaches events older than the start time. Monad tracks which events it has already collected, so re-reading the same day produces no duplicates.
Event types
Method documents these event types:
| Event Type | Description |
|---|---|
account.opened / account.closed | An account was opened or closed. |
credit_score.increased / credit_score.decreased | An entity's credit score changed. |
entity_attribute.credit_health_credit_card_usage.increased / .decreased | Credit card usage changed. |
entity_attribute.credit_health_derogatory_marks.increased / .decreased | Derogatory marks changed. |
entity_attribute.credit_health_hard_inquiries.increased / .decreased | Hard inquiries changed. |
entity_attribute.credit_health_soft_inquiries.increased | Soft inquiries increased. |
entity_attribute.credit_health_total_accounts.increased / .decreased | Total accounts changed. |
entity_attribute.credit_health_credit_age.increased / .decreased | Credit age changed. |
entity_attribute.credit_health_payment_history.increased / .decreased | Payment history changed. |
Method may emit other event types (for example, payment events). Leave Event Type empty to collect all of them.
Setup Walk-through
- In the Method Dashboard, select the environment you want to connect and copy its API key.
- In Monad, navigate to Inputs and click Add Input.
- Search for Method Financial and select Events.
- Set Environment to match the API key you copied (Production, Sandbox, or Development).
- Optionally set Resource Type and/or Event Type to narrow which events are collected.
- Optionally set Backfill Start Time to collect historical events on the first run.
- Enter the API Key in the Secrets section.
- Click Save and verify that the input status transitions to Running.
Testing in Development
Method's Development environment uses mocked data and lets you generate events with its Simulate an Event endpoint (POST https://dev.methodfi.com/simulate/events). Simulation endpoints only work in Development; Sandbox and Production return 403 Forbidden.
- Create an entity, then create the resource the event depends on — a credit score (
POST /entities/{ent_id}/credit_scores), attributes (POST /entities/{ent_id}/attributes), or a Connect (POST /entities/{ent_id}/connect). - Simulate the event with your Development API key, for example
{"type": "credit_score.increased", "entity_id": "ent_..."}. - Configure this input with Environment set to Development and confirm the simulated events arrive.
Troubleshooting
Common Issues
Authentication failures (401)
- Confirm the API key matches the configured Environment — a Sandbox key will not authenticate against Production (and vice versa).
- Confirm the key hasn't been revoked or regenerated in the Method Dashboard.
No records returned
- Without a Backfill Start Time, the first run only collects events from the current day (UTC). Set a backfill date to pull earlier events.
- Backfill Start Time only applies to an input's first run. Once the input has saved state, changing the backfill date has no effect.
- Check the Resource Type and Event Type filters. Event Type must match the event's
typeexactly (e.g.credit_score.increased).
Rate limiting
- Method allows up to 6,000 reads per minute per API key, shared across all
GETrequests on that key. Exceeding it blocks the key for 60 seconds. Monad applies a conservative default outbound request rate so this input can share a key with the Method Financial Accounts input.
Related Articles
Sample Record
Code