---
title: CARE API Overview
slug: public-apis/care-api-overview
createdAt: 2026-03-12T12:40:11.707Z
---

::::ExpandableHeading{isOpen="true"}
###

**Topic type: Concept**

:::hint{type="warning"}
**Purpose**: CARE API overview, request vs settlement flows, and integration scope.&#x20;

**Audience**: API integrators and client developers implementing CARE transactions.&#x20;

**Applies to**: Clients using the CARE API for claims, adjustments, refunds, returns, and exchanges via API.&#x20;

**Does not apply to**: Retail/Fraud industry APIs or clients using non-API CARE integrations.
:::
::::

The Accertify CARE API lets you send CARE requests and settlements to the Interceptas Platform to address risk associated with claims, adjustments, refunds, returns, and exchanges. The API gets you up and running quickly, validates the data you send, and lets you leverage all the data associated with your original transactions.

- If CARE accepts the data you send, it creates a new transaction or updates an existing transaction.&#x20;
- If CARE rejects the data you send, it returns detailed warning and error messages in the response.&#x20;

:::ExpandableHeading
## How CARE Works

1. You send us API inputs when you finalize the settlement of a claim, adjustment, return, refund, or exchange.
2. We create a record for the settlement in the Interceptas Platform and track customer data overtime using keys (email address, shipping address, and so forth).
3. You use the aggregated stats in rules to approve or deny the next transaction using those keys.

In between steps one and two above, your event data is processed through our system. We measure consistency and change in the data collected compared to previous CARE requests and that customer's original transactions, and push it through the Interceptas Platform.
:::

:::::ExpandableHeading
## Two Processing Flows: Requests and Settlements

CARE supports two data flows for CARE transactions: Requests and Settlements. When coding, Requests differ from Settlements in that they include device fields.

::::Tabs
:::Tab{title="Requests"}
**Request Transactions**: Occur when a user attempts to process a CARE-related action on your website, and you must decide whether to grant the request.&#x20;

![CARE Request flow](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/g5QfbjaCJJeZB_jOj1OW2-20260318-154721.png "CARE Request")
:::

:::Tab{title="Settlements"}
**Settlement Transactions**: Occur when your agent processes a CARE transaction (for example, a reship), and you must decide whether to allow that customer’s next transaction.

![CARE Settlement flow](https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/jQkJjo4apHrbwjNJQnzpj-20260318-154721.png "CARE Settlement")
:::
::::
:::::

:::ExpandableHeading{isOpen="true"}
## Calling the API

&#x20;The CARE API request must come from a backend server. JavaScript submission is not supported due to backend data requirements, event-specific error handling, IP allowlisting, and hashing requirements for certain fields.
:::

## Field Reference

View field requirements, paths, and try it out!

::Image[]{src="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/L3EJLm3G3prOYz_UhWGnD-20260326-200545.png" size="34" width="1200" height="600" darkWidth="1200" darkHeight="600" position="center" caption="CARE field references" alt="CARE field references" showCaption="true"}

::::VerticalSplit{layout="middle"}
:::VerticalSplitItem
[CARE Request Fields](docId\:H91CKH3ZobMmFB0MvJ3vG)

[CARE Settlement Fields](docId\:Giq3omTS7qBbt48kgpxXX)
:::

:::VerticalSplitItem
[CARE Request Fields EU](docId\:GwWfO4CmZ-wkn--gmuLWM)

[CARE Settlement Fields EU](docId\:JSQMNYxwrbGjnqqqAKMOG)
:::
::::

