How to view developer request logs for GuardsPro APIs? – GuardsPro Support Center

The Developer Request Logs section provides a comprehensive audit trail of all API interactions performed using your GuardsPro access token, enabling developers to monitor request execution, validate integrations, and troubleshoot issues with precision.

By capturing key metadata such as endpoints, methods, timestamps, and response status codes, it allows you to verify whether external system calls are successfully reaching GuardsPro services, quickly identify and diagnose failed requests, and correlate timestamps with test executions for indirect payload validation. Additionally, it offers basic insights into API usage patterns by tracking the frequency and sequence of requests, helping developers better understand system behavior during testing and deployment.

✅Here's a step-by-step guide to view developer request logs for GuardsPro APIs :

Log in to your GuardsPro Back Office Dashboard. From the top right corner, click on your company name and select Settings from the dropdown. Then, from the left-hand menu, scroll down to the Developer Access section and click on Request Logs to view the developer request logs.

Each log entry represents a single API request and includes the following metadata:

Created Date : Timestamp indicating when the request was initiated (server-side).
Request URL : The API endpoint that was invoked (e.g., /v1/common/select_branch, /v1/report/dar).
Method Type
HTTP method used for the request:
- GET → Data retrieval
- POST → Resource creation or action execution
- (Other methods may be supported depending on the endpoint)
Response Status Code
Standard HTTP response codes returned by the server:
- 200 OK → Request successful and processed correctly
- 400 Bad Request → Invalid payload or parameters
- 401 Unauthorized → Invalid or missing access token
- 403 Forbidden → Insufficient permissions
- 404 Not Found → Invalid endpoint
- 500 Internal Server Error → Server-side failure

Important notes :

Use unique identifiers or timestamps in your API requests to easily trace them in logs.
Regularly monitor logs during integration deployment or updates.
Logs are read-only and cannot be edited or deleted.
On encountering repeated failures (e.g., 401 or 500), verify:
- Access token validity
- Endpoint correctness
- Request structure

If you have any more questions, please feel free to contact our support team anytime.

Important notes :

Related articles