Retrieves the most recent transaction event for a given payment card within an optional time range.
Get Last Transaction Event
Deprecated: This endpoint is deprecated and should not be used in new integrations. Use the current transaction events endpoints for up-to-date transaction data.
This endpoint returns the last (most recent) transaction event associated with a specific payment card. An optional date-time range can be provided to narrow the lookup window. It is intended for querying the tail end of transaction activity on a card.
Endpoint
GET /api/transactionEvents/last
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint when you need to quickly retrieve the single most recent transaction event for a payment card, optionally scoped to a specific time window. This is useful for lightweight status checks or polling scenarios where only the latest activity is needed. Because this endpoint is deprecated, new integrations should prefer the current transaction events listing endpoints.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| paymentCardId | string | No | The unique identifier of the payment card to retrieve the last transaction event for. |
| from | string (date-time) | No | Start of the time range (ISO 8601 date-time) to filter transaction events. |
| to | string (date-time) | No | End of the time range (ISO 8601 date-time) to filter transaction events. |
Response
200 OK
Returns the most recent transaction event matching the provided filters. The response body structure depends on the available transaction data for the given card and time range.
{
"id": "txnevt_abc123xyz",
"paymentCardId": "card_abc123xyz",
"type": "PURCHASE",
"amount": 49.99,
"currency": "USD",
"status": "APPROVED",
"merchantName": "Example Merchant",
"merchantCategory": "RETAIL",
"createdAt": "2026-06-08T14:32:00Z"
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Invalid date-time format supplied for from or to parameters |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to access transaction events for the given card |
| 404 | No transaction event found for the specified card or within the given time range |
| 500 | Internal server error |
Common Mistakes
- Providing
fromortovalues that are not valid ISO 8601 date-time strings will result in a 400 error. - Omitting
paymentCardIdmay return unexpected results or no data if the partner has multiple cards on record; always supply the card ID for precise lookups. - This endpoint is deprecated — avoid building new features on top of it and migrate existing integrations to the current transaction events endpoints.
- Tokens expire after 10 minutes; ensure you refresh the token before making requests in long-running processes.
Related Endpoints
GET /api/transactionEvents— Retrieve a list of transaction events with filtering and pagination supportGET /api/transactionEvents/{transactionEventId}— Retrieve details for a specific transaction event by ID
Example
curl -X GET "https://api.banking.netevia.dev/api/transactionEvents/last?paymentCardId=card_abc123xyz&from=2026-06-01T00%3A00%3A00Z&to=2026-06-08T23%3A59%3A59Z" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"Success