Intangles Api Request Log
The Intangles API Request Log is part of the Erpnext Intangles Integration module. It is designed to record every API interaction made between the ERP system and the Intangles platform. This log helps in monitoring API performance, debugging communication issues, and maintaining transparency in all API transactions.
Purpose
The main purpose of the Intangles API Request Log is to:
- Track all outgoing API requests and their responses from the ERP to Intangles.
- Record API endpoints, payloads, headers, and response details.
- Monitor the status of API responses through HTTP status codes.
- Support debugging by keeping complete request and response data.
- Automatically remove older logs to optimize database performance.
Key Features
- API Tracking: Every API request and response is stored with detailed information.
- Automatic Log Creation: Logs are created automatically whenever an API call is made.
- JSON Formatting: Request and response data are stored in a readable, formatted structure.
- Error Handling: Handles both JSON and non-JSON responses to prevent logging errors.
- Auto Cleanup: Automatically deletes logs older than one day to maintain efficiency.
Field Details
| Field Name | Description |
|---|---|
| API Method | Name or label of the API method or action performed, such as “Get Vehicle Details” or “Fetch DTC Log”. |
| URL | The API endpoint that was called, showing the complete URL of the request. |
| Header | Contains the request headers used in the API call, including authentication tokens or content types. |
| Payload | The data or parameters sent to the API during the request. |
| Status Code | The HTTP response code received from the API (e.g., 200 for success, 400 for error). |
| Response | The full response message received from the API call, including results or error details. |
Permissions
The following role has full access to create, read, write, delete, export, print, report, share, and email:
- System Manager
Automation
- Automatic Cleanup: Logs older than one day are automatically deleted to prevent database clutter.
- Error Handling: Invalid or non-JSON responses are safely stored as plain text.
- Commit on Insert: Each log is committed to the database immediately for accurate tracking.
Example Workflow
- A request is sent from ERPNext to an Intangles API endpoint.
- The system automatically creates a new log entry capturing the API name, URL, headers, and request payload.
- Once a response is received, it records the status code and complete response data.
- Old logs are deleted automatically after one day to maintain efficiency.
Benefits
- Improves visibility into all API communications.
- Helps diagnose failed API calls easily.
- Keeps the integration reliable and transparent.