Get transaction's details report

Get Transaction's Details Report

The GET /api/transaction/reportDetails endpoint provides detailed reporting information about specific transactions. It returns a file-like content object containing the transaction report, including transaction IDs, dates, amounts, descriptions, and associated account details. This endpoint is useful for auditing, verification, and in-depth review of individual or filtered transaction history.

Endpoint

GET /api/transaction/reportDetails

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a partner or customer needs a comprehensive report for a specific transaction or all transactions associated with a payment card. It is well-suited for audit workflows, customer-facing transaction review screens, and back-office reconciliation processes that require granular transaction-level data.

Query Parameters

ParameterTypeRequiredDescription
paymentCardIdstringNoThe unique identifier of the payment card whose transactions should be included in the report.
transactionIdstringNoThe unique identifier of a specific transaction to retrieve detailed report data for.

Response

200 OK

FieldTypeDescription
namestring (nullable)The name or filename of the generated report content.
contentstring (nullable)The report payload, typically encoded as a string (e.g., base64 or plain text).
contentTypestring (nullable)The MIME type of the content (e.g., application/json, text/plain).
{
  "name": "transaction_report_20240601.json",
  "content": "eyJ0cmFuc2FjdGlvbklkIjoiYWJjMTIzIiwiYW1vdW50IjoxMDAuMDB9",
  "contentType": "application/json"
}

Error Codes

CodeWhen it happens
400Invalid or malformed query parameter values provided
401Token missing, expired, or invalid
403Insufficient permissions to access transaction report data
404No transaction or card record found for the provided identifiers
500Internal server error

Common Mistakes

  • Omitting both paymentCardId and transactionId — while both are optional, providing at least one is necessary to retrieve a meaningful report; an empty query may return no results or a generic response.
  • Assuming content is always human-readable — the content field may be base64-encoded depending on the report format; check contentType to determine how to parse or render it.
  • Using a stale Bearer token — tokens expire after 10 minutes; refresh via POST /api/auth/refresh before making this call if your token may have expired.

Related Endpoints

  • GET /api/transaction/report — Retrieve a summary-level transaction report
  • GET /api/transaction/{transactionId} — Fetch details for a single transaction by ID
  • POST /api/auth/v2 — Obtain a Bearer token for authentication
  • POST /api/auth/refresh — Refresh an expiring Bearer token

Example

curl -X GET "https://api.banking.netevia.dev/api/transaction/reportDetails?paymentCardId=card_abc123&transactionId=txn_xyz789" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"
Query Params
string
string
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json