Query Cash In by E2E ID
Queries a PIX transaction by End-to-End ID (BACEN unique identifier).
Endpoint
GET /api/v2/external/transactions/e2e/:e2e_idHeaders
| Header | Type | Required | Description |
|---|---|---|---|
Authorization | String | Yes | Bearer {access_token} |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
e2e_id | String | Yes | Transaction End-to-End ID (format E{ISPB}{date}{seq}) |
E2E ID Format
The E2E ID follows the BACEN standard: E + ISPB (8 digits) + UTC date/time (12 digits) + sequential (6 digits). Example: E37839059202603071530000001.
Example
bash
curl -X GET https://api.owem.com.br/api/v2/external/transactions/e2e/E37839059202603071530000001 \
-H "Authorization: Bearer $TOKEN"Success Response (200)
json
{
"worked": true,
"data": {
"id": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
"transaction_id": "PIXIN20260307a1b2c3d4e5f6",
"end_to_end_id": "E37839059202603071530000001",
"type": "pix",
"status": "completed",
"amount": 10000,
"fee_amount": 0,
"net_amount": 10000,
"description": "Order #1234",
"direction": "inbound",
"counterparty_name": "Maria Santos",
"created_at": "2026-03-07T15:30:00Z",
"completed_at": "2026-03-07T15:30:02Z"
}
}This endpoint returns the same transaction object described in Query by ID. The direction field indicates whether it is a receipt (inbound) or a send (outbound).
Error Response (404)
json
{
"worked": false,
"detail": "Transaction not found for the provided E2E"
}Error Response (401)
json
{
"worked": false,
"detail": "Invalid or expired token"
}Cash In and Cash Out
This endpoint returns both inbound and outbound transactions. Use the direction field to differentiate: inbound (receipt) or outbound (send).