Skip to main content
The Events API allows you to track both literal and computed changes to various Method resources, such as Attributes, Accounts, Credit Scores, and more. Events provide detailed insights into how data changes over time, helping teams monitor resource updates and interpret complex changes. Literal events track specific updates to a resource. For example, if an account’s status transitions from active to closed, an account.closed event will be triggered, showing the exact change. Computed events are triggered when a meaningful interpretation is derived by comparing changes across multiple resources or combining several field changes. For example, the credit_score.increased event is triggered when a new credit score record shows an increase compared to the previous record.

​
Event Objects

​
id
string
Unique identifier for the Event.
​
type
enum
Type of event.
​
resource_id
string
ID of the resource associated with the event.
​
resource_type
enum
Type of resource One of account, attribute, connect or credit_score
​
data
object
A snapshot of the associated resource.
​
diff
object
An object representing the differences/changes that occurred.
​
created_at
string
Timestamp when the event was created.
​
updated_at
string
Timestamp when the event was last updated.
{
  "id": "evt_7pPmytbXgWk7C",
  "type": "credit_score.increased",
  "resource_id": "crs_wXVk4MM7QWNnh",
  "resource_type": "credit_score",
  "data": "CreditScore",
  "diff": {
    "before": {
      "id": "crs_pn4ca33GXFaCE",
      "entity_id": "ent_au22b1fbFJbp8",
      "status": "completed",
      "scores": [
        {
          "score": 724,
          "source": "equifax",
          "model": "vantage_3",
          "factors": []
        }
      ]
    },
    "after": {
      "id": "crs_wXVk4MM7QWNnh",
      "entity_id": "ent_au22b1fbFJbp8",
      "status": "completed", 
      "scores": [
        {
          "score": 741,
          "source": "equifax",
          "model": "vantage_3",
          "factors": []
        }
      ]
    }
  },
  "updated_at": "2024-08-01T16:08:25.462Z",
  "created_at": "2024-08-01T16:08:25.462Z"
}