Network API

Update Conversion Status by Transaction ID

curl --request PATCH \
  --url https://api.eflow.team/v1/networks/reporting/conversions/{transactionId} \
  --header 'Content-Type: application/json' \
  --header 'X-Eflow-Api-Key: <api-key>' \
  --data '
{
  "conversion_status": "approved"
}
'

{
  "result": true
}

Update Conversions by Transaction ID

Modify the status of all conversions and events linked to a single transaction ID. Only approved and rejected are accepted values. Conversions that are invalid will be ignored; only approved, rejected, and pending conversions will be updated.

Note that the endpoint is asynchronous. Even when the endpoint returns true immediately, it may take up to a few seconds for the conversion updates to be processed (and to fire partner pixels if appropriate).

PATCH

networks

reporting

conversions

{transactionId}

Update Conversion Status by Transaction ID

curl --request PATCH \
  --url https://api.eflow.team/v1/networks/reporting/conversions/{transactionId} \
  --header 'Content-Type: application/json' \
  --header 'X-Eflow-Api-Key: <api-key>' \
  --data '
{
  "conversion_status": "approved"
}
'

{
  "result": true
}

Authorizations

X-Eflow-Api-Key

string

header

required

The Everflow API key generated from the Control Center > Security.

Path Parameters

transactionId

string

required

The transaction ID whose conversions should be updated.

Body

application/json

conversion_status

enum<string>

required

Target status for the conversions.

Available options:

approved,

rejected

Response

200 - application/json

result

boolean

Whether the update was successful.

⌘I

Documentation Index

Authorizations

Path Parameters

Body

Response