Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.methodfi.com/llms.txt

Use this file to discover all available pages before exploring further.

Attributes provide structured financial metrics derived from an Entity’s linked accounts. Rather than giving you raw account data, Attributes distill the information into actionable categories that your product can use to generate insights, recommendations, and personalized guidance.

​
Entity vs Account Attributes

Attributes are available at two levels:
  • Entity Attributes: Aggregated across all of an Entity’s connected accounts. Use POST /entities/{ent_id}/attributes to compute them. Available as a Product (on-demand) or Subscription (continuous updates via webhooks).
  • Account Attributes: Per-account metrics for a single Account. Use POST /accounts/{acc_id}/attributes. Available as a Product only.
This means you can show a user their overall credit utilization AND the utilization on each individual credit card.

​
How It Works

Attribute requests are asynchronous. When you create an Attributes request, you’ll receive an immediate response with status: "in_progress" and attributes: null. Once processing completes, the status updates to completed and the attributes object is populated. Use webhooks or poll the retrieve endpoint to get the final result. Each attribute in the response is an object with a value field and an error field. If an attribute couldn’t be computed (for example, insufficient historical data for a 60-day trend), value will be null and error will contain details about why. 
{
  "credit_card_utilization": {
    "value": 11.96,
    "error": null
  },
  "revolving_credit_card_balance_change_60d": {
    "value": null,
    "error": {
      "type": "ENTITY_ATTRIBUTE_INSUFFICIENT_DATA",
      "code": 27001,
      "message": "Insufficient data to compute this entity attribute."
    }
  }
}

​
Available Categories

Entity Attributes span six categories:
  • Revolving Credit Card: Balances, credit limits, utilization, weighted average APR, usage patterns, minimum payments, delinquency flags, and 30/60/90-day balance and utilization trends.
  • Personal Loan: Balances, original loan amounts, estimated monthly installments, utilization, weighted average APR, and 30/60/90-day trends.
  • Mortgage: Balances, original loan amounts, weighted average APR, and 30/60/90-day trends.
  • Overall: Cross-category totals for original loan amounts, overall utilization, and 30/60/90-day utilization trends.
  • Installment: Total installment balance and 30/60/90-day balance changes.
  • Other: Balances and trends for account types not covered above.
Account Attributes vary by the account’s liability type (credit card, personal loan, or mortgage). Requesting attributes for an unsupported account type returns a 400 error.

​
Quick Start

curl https://production.methodfi.com/entities/ent_au22b1fbFJbp8/attributes \
  -X POST \
  -H "Method-Version: 2026-03-30" \
  -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc"

​
Error Handling

Request-level errors (the Attributes request itself fails):
  • PRODUCT_UNAVAILABLE: The Entity doesn’t support Attributes.
  • TEAM_CAPABILITY_RESTRICTED: Your team doesn’t have access to Attributes.
  • PRODUCT_VERIFICATION_MISSING: Entity must be verified first.
  • PRODUCT_RESTRICTED_CONNECT_REQUIRED: Entity must have a completed Connect record.
Attribute-level errors (individual attributes within a successful response):
  • ENTITY_ATTRIBUTE_INSUFFICIENT_DATA: Not enough historical data to compute this attribute.
  • ACCOUNT_ATTRIBUTE_INSUFFICIENT_DATA: Same, for Account-level attributes.
For your product, Attributes enable features like credit health dashboards, personalized recommendations (“Your credit card utilization is high, consider paying down Card X first”), progress tracking over time, and educational content tied to the user’s actual situation.

Attributes API Reference

Full API documentation for Entity and Account Attributes.