Removed

Deprecated Fields To Be Removed from Auth Rule Performance Report

Release Date

April 8, 2026

Products Affected

Auth Rules

Impact

Deprecated fields and objects will be removed from GET /v2/auth_rules/{auth_rule_token}/report response

Audience

Customers using Auth Rule performance reports

Action Required

Migrate to versions array and action_counts fields before April 8th if still referencing deprecated fields

Overview

Beginning Wednesday, April 8th, several deprecated fields and objects will be removed from the Auth Rule performance report endpoint (GET /v2/auth_rules/{auth_rule_token}/report). The current_version_statistics and draft_version_statistics objects are being migrated to the versions array, and the explicit approved/declined/challenged count fields have been replaced by the more flexible action_counts field. All customers who have called this endpoint in the last 60 days have been contacted and confirmed no impact.

Details

The current_version_statistics and draft_version_statistics objects will be removed from each entry in the daily_statistics array in favor of the versions array, which provides the same per-version statistics with additional context: version number, state (ACTIVE, SHADOW, or INACTIVE), action_counts, and examples.

Deprecated Count Fields Removed

The following fields, previously present within the statistics objects, will also be removed:

  • approved (integer) - Returns the total number of transactions approved by the rule during the reported period
  • declined (integer) - Returns the total number of transactions declined by the rule during the reported period
  • challenged (integer) - Returns the total number of transactions challenged by the rule during the reported period

These counts are available through the action_counts object on each entry in the versions array, which provides a mapping of all action types (including APPROVE, DECLINE, CHALLENGE, NO_ACTION, REQUIRE_TFA, and others) to their respective counts.

Example Response

Currently, each entry in daily_statistics includes current_version_statistics, draft_version_statistics, and the versions array:

{
  "date": "2026-03-15",
  "current_version_statistics": {
    "approved": 150,
    "declined": 30,
    "challenged": 5,
    "action_counts": {
      "APPROVE": 150,
      "DECLINE": 30,
      "CHALLENGE": 5,
      "NO_ACTION": 200
    },
    "examples": [...]
  },
  "draft_version_statistics": {
    "approved": 80,
    "declined": 45,
    "challenged": 10,
    "action_counts": {
      "APPROVE": 80,
      "DECLINE": 45,
      "CHALLENGE": 10,
      "NO_ACTION": 100
    },
    "examples": [...]
  },
  "versions": [
    {
      "version": 3,
      "state": "ACTIVE",
      "action_counts": { "APPROVE": 150, "DECLINE": 30, "CHALLENGE": 5, "NO_ACTION": 200 },
      "examples": [...]
    },
    {
      "version": 4,
      "state": "SHADOW",
      "action_counts": { "APPROVE": 80, "DECLINE": 45, "CHALLENGE": 10, "NO_ACTION": 100 },
      "examples": [...]
    }
  ]
}

After April 8th, current_version_statistics and draft_version_statistics will be migrated to the versions array, and the deprecated count fields will be removed. The state field on each version entry (ACTIVE, SHADOW, INACTIVE) indicates which version is current and which is a draft:

{
  "date": "2026-03-15",
  "versions": [
    {
      "version": 3,
      "state": "ACTIVE",
      "action_counts": { "APPROVE": 150, "DECLINE": 30, "CHALLENGE": 5, "NO_ACTION": 200 },
      "examples": [...]
    },
    {
      "version": 4,
      "state": "SHADOW",
      "action_counts": { "APPROVE": 80, "DECLINE": 45, "CHALLENGE": 10, "NO_ACTION": 100 },
      "examples": [...]
    }
  ]
}

Release Timeline

Production availability: April 8, 2026

User Impact

Integrations that read current_version_statistics or draft_version_statistics should migrate to the versions array, which provides the same data keyed by version number and state. Integrations that reference the approved, declined, or challenged count fields will need to migrate to action_counts. The action_counts field provides broader coverage, including action types such as NO_ACTION, REQUIRE_TFA, and TAG that were not represented by the legacy fields.

Updated Documentation

For the complete Auth Rule performance report specification, visit our API Reference.

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.


The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.