> ## Documentation Index
> Fetch the complete documentation index at: https://developers.clara.team/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> History of API changes and field updates.

### 24 Mar 2026 Cards Configuration V2 service - time adjustment

The Cards Configuration V2 service has been updated to handle default time values when inserting or updating a Period configuration.

Previously, if `startTime` or `endTime` were not provided in the request, the service defaulted to the current time at the moment of the operation. This behavior was incorrect for period-based configurations.

**New behavior:**\
Whenever a Period configuration is created or updated, if `startTime` or `endTime` are `null` or empty, the service will now apply the following defaults:

* `startTime` → `00:00`
* `endTime` → `23:59`

**Action required:**\
No changes are required on the consumer side. However, if `startTime` and `endTime` are treated as mandatory fields in your integration, ensure they are explicitly sent as `00:00` and `23:59` respectively for full-day period cases, rather than relying on empty or null values.

🔍 Affected Endpoints:

* POST /api/v2/cards/{uuid}/configurations
* PATCH /api/v2/cards/{uuid}/configurations

<br />

```json RequestBody theme={null}
{
  "period":{
      "startDate": "2026-03-19",
      "endDate": "2026-05-21",
      "startTime": null,
      "endTime": null,
      "enableAutoDeletion": false 
  },
  "atmCashLimit": 0.0,
  "weekdays": null,
  "merchants": null
}
 
```

***

<br />

### 9 Feb 2026 Enable Configuration and Threshold Updates for Locked, Frozen, and Restricted Cards

🔍 Affected Endpoints:

* POST /api/v2/cards/{uuid}/configurations
* PATCH /api/v2/cards/{uuid}/configurations
* DELETE /api/v2/cards/{uuid}/configurations
* POST /api/v3/cards/{uuid}/configurations
* PATCH /api/v3/cards/{uuid}/configurations
* DELETE /api/v3/cards/{uuid}/configurations
* PATCH /api/v2/cards/{uuid}
* PATCH api/v3/cards/threshold

***

<br />

### 12 Jan 2026 Adding Accounting Fields in Transaction V3 services

We've exposed the custom fields property through the API Transactions Service v3, enabling deeper integration and more flexible accounting workflows.

🔍 Affected Endpoints:

* GET /api/v3/transactions
* GET /api/v3/transactions/{uuid}
* GET /api/v3/billing-statements/current
* GET /api/v3/billing-statements/{uuid}

<br />

```json new Accounting fields theme={null}
{
  "content":[{
      "uuid": "1614c41b-8eb4-4573-9262-8aff011224c5",
      "type": null,
      "transactionLabel": "DHL EXPRESS CE",
      "labels": [],
      "status": null,
      "comment": null,
      "billingStatement": {
         "uuid": null,
         "periodStartDate": null,
         "periodEndDate": null,
         "links": []
      },
      "accountingFields": [
        {
          "customFieldUuid": "439671cd-6117-420b-a9e4-f39e994c1cee",
          "customFieldName": "Expense Category",
          "value": "MAND",
          "label": "MANTTO. DE EDIFICIO"
        },
        {
          "customFieldUuid": "439671cd-6117-420b-a9e4-f39e994c1cff",
          "customFieldName": "Center Cost",
          "value": "COMP",
          "label": "COMPRAS"
        }
      ],
      "audit":{...},
      //...
  }]
}
 
```

This update provides visibility of accounting-related custom fields in transaction and billing statement detail.

***

<br />

### 08 Jul 2025 Improved Tax ID Validation for User Management

We’ve introduced enhanced validation rules for user Tax Identifiers based on the user’s country, ensuring data integrity and compliance.

**🔍 Affected Endpoints:**

* [`Create User`](/v3/users)
* [`Update User`](/v3/users)

**📌 Validation Rules by Country:**

* **MX (Mexico)**: Tax ID must be **11 or 13** digits
* **CO (Colombia)**: Tax ID must be **7, 8, 9, or 10** digits
* **BR (Brazil)**: Tax ID must be **11** digits

Requests that do not comply with these rules will now return a validation error.

This update improves consistency in user data and prepares the system for future compliance checks and integrations.

***

<br />

### New 03 Jul 2025`GET Reimbursements` Endpoint

We’ve implemented a new service to retrieve reimbursement records, improving visibility and integration with your internal tools.

**🆕 New Endpoints docs:**

* [`How to use it`](/v3/reimbursements)
* [`Find reimbursements`](/v3/reimbursements)

**🔍 Highlights:**

* Programmatically retrieve reimbursement data by user, status, or time range.
* Supports filtering, sorting, and pagination for scalable integration.
* Enables real-time access to reimbursement information for finance automation and reporting.

This release enhances control and transparency around reimbursement workflows.

***

<br />

## 30 Jun 2025 — `Field Update to transactions-v3`

We've updated the `transactions-v3` data model to add the field `hasExtractedDocuments`, this field has two parts one is value that will have true or false and the other one is links that is redirect to the endpoint `extracted-documents`. This change enhances consistency across services and aligns with the broader data model strategy.

### Affected Endpoints:

* [Find all transactions with filters](/v3/transactions)
* [Get a Transaction by UUID](/v3/transactions)

***

## 25 Jun 2025 — `Audit API`

We’ve introduced a new **Audit API** to provide enhanced visibility into API activity and improve observability across the platform.

### New Endpoints

* [Get current month logs](/v1/logs)
* [Get logs by year/month](/v1/logs)
* [Get logs by year/month/day](/v1/logs)

### Highlights:

* Filtered logs only (by date: current month, a specific month and year, or a precise day) - no unfiltered access
* Logs include metadata, such as request URI, method, token, status, chargeability
* Improves monitoring, auditing, and billing visibility

This update is part of our commitment to building transparent and secure systems that empower teams to trace and audit platform activity with precision.

***

## 13 Jun 2025 — `New Receipt Scanner Service`

We’ve introduced a new **Receipt Scanner** service to enhance document processing and data extraction capabilities across the platform.

### New Endpoint:

* [Find documents by transaction UUID](/v3/extracted-documents)

### Highlights:

* Enables retrieval of documents automatically extracted from invoices, receipts, mexican\_fiscal\_invoices and other documents based on the associated transaction UUID.
* Supports tighter integration between scanned receipt, invoices data and transaction records.
* Lays the groundwork for future automation and smart reconciliation features.

This update is part of our ongoing efforts to streamline expense management and improve document intelligence throughout Clara’s ecosystem

***

## 26 May 2025 — `Field Update to cards-v3`

We've updated the `cards-v3` data model to replace the deprecated `claraStatus` field with a new standardized `status` field. This change enhances consistency across services and aligns with the broader data model strategy.

### Affected Endpoints:

* [Find all cards](/v3/cards)
* [Find card by UUID](/v3/cards)

✅ \*\*Update: Replace \*\*`claraStatus` with `status` in the API responses for the above endpoints.

⚠️ \*\*Action Required: \*\*Update your integrations accordingly

***

## 15 Jun 2024 — New Fields

### Affected Endpoints:

* Transactions:
  * `billingStatement`: Billing statement dates - start, end, and dueDate
  * `authorizationNumber`: Number of authorization from a transaction

***

## 06 May 2024 — `New Fields and Endpoints`

### Affected Endpoints:

* \*\*Cards: \*\*Limit adjustment, lock/unlock card (PATCH)
* **Transactions:** Added `authorizationNumber` → It refers to the approval number from MasterCard that is also on the Transactions report in the Clara Platform

***

## 15 Apr 2024 — `Write Mode Launch`

We're introducing **WRITE MODE** functionality for Cards, Labels, and Groups!

With the addition of Write Mode, you now have the ability to not only retrieve data but also create and manage cards, labels, and groups directly through our API. This expansion provides you with greater flexibility and control over your data, enabling you to tailor your applications to better suit your needs.

### Affected Endpoints:

* \*\*Cards: \*\*Create cards with custom rules
* **Groups:** Create/manage groups
* \*\*Labels: \*\*Create labels to classify transactions

***

## 26 Mar 2024 —` User Field Update`

### Affected Endpoints:

* \*\*Users: \*\*Changed userFullName format → We inverted the *First Last Name* and *Second Last Name* `(Only MX and CO)`

***

## 26 Feb 2024 — `Filter Updates`

### Affected Endpoints:

* Transactions: Added `sort` → Sort the results by specific fields and directions. (accountingDate | operationDate),(ASC | DESC)

***

## 21 Feb 2024 — `More Field Updates`

### Affected Endpoints:

* Transactions:
  * `maskedPan`: First 6 digits and last 4 digits of the card)
  * `cardLastDigits`: Masked Pan Last Digits of the card associated with the transactions)

***

## 19 Feb 2024 — `Attachments and Filters`

### Affected Endpoints:

* Transactions:
  * Attachments: Information about the files attached to the transaction
    * fileName
    * type: TRANSACTIONS\_RECEIPT/TRANSACTIONS\_INVOICE
    * hasReceipt: Boolean
    * hasInvoice: Boolean
* userErpId: ERP id of the transaction user from the Team panel in Clara's Platform
* username: Username of the transaction user

***

## 08 Feb 2024 — Field Modifications

### Affected Endpoints:

* Transactions:
  * `statusCode` → `status`
  * `comments` → `comment`
  * Removed: `tax` (because it didn't refer to the purchase taxes but rather to transaction values), `expirationDate` (Was a static value. We are creating a new field to bring this expiration value for each transaction)