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

# Load Confirmation

> Send a request to a REST API after a successful load

## Overview

Load Confirmation sends an additional request to a REST API alongside the main load, so you can forward the load result to another destination or trigger a downstream action.

A confirmation request can be **dependent** on or **independent** from the main load. A dependent confirmation runs only after the main load succeeds and can access its response; an independent confirmation runs without waiting for the load and has no access to its response.

The flow becomes **Extract → Transform → Load → Confirmation**.

## When to use

Use Load Confirmation when you need to forward the data returned by the load request to another destination, or when you need to trigger another action once the load has succeeded, for example acknowledging an order back to the source system or notifying a separate service that the records were delivered.

## Configuration

Mark the **Send Confirmation?** checkbox to enable the feature, then configure:

| Field      | Description                                               |
| ---------- | --------------------------------------------------------- |
| Connection | Connection to the REST API to send the request to.        |
| Method     | HTTP method to use for the request (`GET`, `POST`, etc.). |
| Path       | Endpoint path to send the request to.                     |

### Query parameters and body

The query parameters and body can use data from the extract and enrichment phases. Data from the load phase is only available when the confirmation is dependent on the load (see below).

## Dependent vs. independent confirmation

The **Make the confirmation dependent on the load?** checkbox controls how the confirmation request relates to the main load:

| Mode        | Behavior                                                                                            |
| ----------- | --------------------------------------------------------------------------------------------------- |
| Dependent   | Runs only after the main load request has succeeded, and can access the main load's response data.  |
| Independent | Runs without waiting for the main load request, and has no access to the main load's response data. |

Leave the checkbox unmarked for an independent confirmation. Mark it when the confirmation needs to wait for the load to succeed or needs to use data returned by the load.

## Accessing load data

When the confirmation is **dependent** on the load, the load response is exposed to the confirmation request, so its fields can be referenced in query parameters and the body:

| Field         | Description                               |
| ------------- | ----------------------------------------- |
| load.response | The body of the load request response.    |
| load.status   | The status of the load request response.  |
| load.headers  | The headers of the load request response. |

## Related

<CardGroup cols={2}>
  <Card title="Dynamic Parameters" icon="brackets-curly" href="/en/features/extract/dynamic-parameters">
    Insert dynamic values into paths, headers, and request bodies
  </Card>

  <Card title="Enrichment" icon="layer-group" href="/en/features/extract/enrichment">
    Fetch additional data for each extracted datapoint
  </Card>
</CardGroup>