Developer CenterGuidesAccount Number Changes

    Account Number Changes

    The implemented public path for account-number changes is the standard ingest endpoint with an attached L1 segment.

    Public Endpoint

    Use POST /api/v1/submit-metro2-data and include an l1_segments array, or the external alias change_indicators.

    L1 Fields

    • change_indicator: 1 account number only, 2 identification number only, 3 both
    • new_consumer_account_number
    • new_identification_number (optional)

    Example

    {
      "records": [
        {
          "consumer_account_number": "NEW-ACCT-1001",
          "portfolio_type": "I",
          "account_type": "00",
          "date_opened": "2024-01-15",
          "highest_credit_or_original_loan_amount": 25000,
          "terms_duration": "060",
          "terms_frequency": "M",
          "account_status": "11",
          "current_balance": 18500,
          "date_of_account_info": "2025-03-01",
          "surname": "Smith",
          "first_name": "Jane",
          "ecoa_code": "1",
          "address_1": "123 Main St",
          "city": "Austin",
          "state": "TX",
          "postal_code": "78701",
          "address_indicator": "C",
          "country_code": "US",
          "l1_segments": [
            {
              "change_indicator": "1",
              "new_consumer_account_number": "NEW-ACCT-1001"
            }
          ]
        }
      ]
    }

    Not Implemented

    The repo does not implement a separate public /api/v1/records endpoint for this workflow.