Skip to main content
This service is available in v3 only.

How to Find Reimbursements via Clara API

This guide explains how to use the GET /api/v3/reimbursements endpoint to retrieve reimbursements in the Clara API system.

Authentication Requirements

To access this endpoint, ensure the following:
  • Use mutual TLS (MTLS) for secure two-way certificate validation.
  • Obtain an OAuth2 access token via the /oauth/token endpoint.
  • Include the Bearer token in the Authorization header of your request.

Endpoint

  • Base URL examples:
    • https://public-api.mx.clara.com
    • https://public-api.br.clara.com
    • https://public-api.co.clara.com

Query Parameters (Optional)


Successful Response


Error Responses


Example cURL Request

Replace {your_access_token}, {client_cert_path}, and {client_key_path} with actual values.

Example Response Object



Lifecycle Statuses (ValidationStatus — Reimbursements)

The lifecycle of a reimbursement request typically flows through these statuses:
  • PENDING: Request has been created and is pending review or approval.
  • APPROVED: Request has passed validation and been approved.
  • SENT_TO_PAY: Approved and submitted for financial processing.
  • PAYMENT_IN_PROGRESS: Payment execution has started.
  • PAID: Funds have been disbursed.
  • REJECTED: Request did not meet policy or was denied.
  • FINANCE_REJECTED: Rejected specifically by the finance department.
  • CANCELLED: Request was manually cancelled before payment.
  • NOT_FOUND: No matching reimbursement record exists.
  • UNAUTHORIZED: Request not allowed under current user permissions.

Lifecycle Flow (Reimbursements)

Create → Pending → Approve/Reject → Sent to Pay → Payment In Progress → Paid
  1. Creation: A reimbursement request is submitted. Initial status: PENDING.
  2. Approval: The request may be APPROVED or REJECTED based on validations.
  3. Cancellation: A PENDING request can be cancelled, moving to CANCELLED.
  4. Financial Routing: Once approved, it moves to SENT_TO_PAY.
  5. Payment: Transitions to PAYMENT_IN_PROGRESS as disbursement begins.
  6. Completion: Final state is PAID once the process completes.
Exceptional states like NOT_FOUND and UNAUTHORIZED are returned for invalid operations or permissions.

Summary

  • Use the GET /api/v3/reimbursements endpoint to retrieve reimbursement records with rich filtering options.
  • Apply filters such as creation date, approval date, requester UUIDs, or statuses for granular access.
  • Use the lifecycle and validation statuses to interpret reimbursement processing stages.
  • Ensure mutual TLS and OAuth2-based access to securely consume the API.

Endpoint Reference

GET /api/v3/reimbursements

List reimbursements (v3) Parameters:

GET /api/v3/reimbursements/{uuid}

Get reimbursement by UUID (v3) Parameters: Response Schema (ReimbursementV3):