BursaPay Logo
Knowledge Base
Ticket Sign In
Help Center > Developer Platform & Gateway API > API Request Logging and Audit Trail

API Request Logging and Audit Trail

Published 2026-08-24 5 min read
Who is this article for?
This guide is for Developers, Engineering Teams, Platform Operators seeking operational guidance on BursaPay workflows.

UI Navigation Path (Step-by-Step)

  1. Inspect the API history area or logs endpoint.
  2. Filter by endpoint, reference or time window where available.
  3. Correlate the request with your application logs.
  4. Use the reference to trace the financial operation.
Verified BursaPay workflow: Understand what the gateway records about API requests for support, audit and debugging.

1. Overview & Purpose

ApiLog stores the developer, API key, endpoint, method, IP, user agent, request/response information, duration and reference.

2. Requirements & Setup

Developers should avoid sending secrets in request bodies because logged request data may be retained for audit/debugging.

3. Step-by-Step Workflow

  1. Inspect the API history area or logs endpoint.
  2. Filter by endpoint, reference or time window where available.
  3. Correlate the request with your application logs.
  4. Use the reference to trace the financial operation.

4. Rules & Troubleshooting

Never send passwords, secret keys or unnecessary sensitive data in metadata or request bodies.

5. Verification & Next Steps

Use API logs together with payment/ledger records for production incident analysis.

Was this article useful?

Related Articles

Sandbox Playground for API Testing Rate Limits and API Throttling
Ask Bursa AI