POST
/
v2
/
journey
/
{queryId}
curl --request POST \
  --url https://api.request.network/v2/journey/{queryId} \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --data '{
  "status": "COMPLETED",
  "amount": "1000.00",
  "currency": "USDT",
  "txReference": "0xabc123def456...",
  "processedAt": "2024-06-10T14:23:00Z",
  "rawPayload": {
    "exchange": "Binance",
    "network": "Ethereum",
    "fee": "2.50",
    "note": "Withdrawal to bridge"
  }
}'
{
  "id": "01EVENTULID1234567890ABCDEF",
  "journeyId": "01JOURNEYULID1234567890ABCDEF",
  "processorId": "01PROCESSORULID1234567890ABCDEF",
  "status": "COMPLETED",
  "amount": "1000.00",
  "currency": "USDT",
  "txReference": "0xabc123def456...",
  "processedAt": "2024-06-10T14:23:00Z",
  "rawPayload": {
    "exchange": "Binance",
    "network": "Ethereum",
    "fee": "2.50",
    "note": "Withdrawal to bridge"
  }
}

Headers

​
x-api-key
string
required

API key for authentication

Path Parameters

​
queryId
string
required

Either a journeyId (e.g., '01JOURNEYULID1234567890ABCDEF') or a txReference from an existing event in the journey (e.g., '0xabc123def456...'). The system will automatically determine which type is provided and locate the appropriate journey.

Example:

"01JOURNEYULID1234567890ABCDEF"

Body

application/json
​
status
string
required

The status of the journey event

​
amount
string
required

The amount of the journey event

​
processedAt
string
required

The date and time the journey event was processed, has to be in UTC format and end with 'Z' example 2025-07-23T14:23:00Z

​
currency
string

The currency of the journey event

​
txReference
string

The transaction reference of the journey event

​
rawPayload
any

The raw payload of the journey event

​
nextProcessorId
string

The ID of the next processor in the journey

Response

Journey event created successfully. Returns the event details.

The response is of type any.