Understand log context | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/proplix-secure-api-gateway-logs-errors-responses-fields Publisher: Pixie Technologies LLC Request logs, response codes and troubleshooting Understand log context Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Logs can include key/profile, endpoint/source/module/resource, method, IP and response code. Audience: CRM administrators, integration developers, external portal backend teams and security reviewers; Permission: Administrator or integration developer; Module v1.0.0; Where to goAdmin Area → Utilities/Tools → API Gateway → Recent API logs Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do Logs can include key/profile, endpoint/source/module/resource, method, IP and response code. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Utilities/Tools → API Gateway → Recent API logs. - Find the record, endpoint, field or action used to understand log context. - Complete the displayed values exactly as described in this guide. - Select the available save, submit, send, upload, create, update or confirm action. - Return to the related register, portal, activity log or API response and verify the expected result. Fields and options Workspace or endpointAdmin Area → Utilities/Tools → API Gateway → Recent API logs PurposeLogs can include key/profile, endpoint/source/module/resource, method, IP and response code. Rules and limits - The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions. - Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages. Check it worked - The understand log context workflow completes without a validation, permission, ownership or availability error. - The related record, portal view, activity entry, notification log or API response shows the expected state. - Client-visible, public and API data remains limited to the code-backed ownership and visibility rules. Security, privacy and operational checks - Use controlled test records and non-production credentials before wider rollout. - Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs. Related guides Review recent API logs (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-logs-errors-responses-recent)Understand successful responses (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-logs-errors-responses-200)Request logs, response codes and troubleshooting (https://pixiecrm.com/help-centre/topic/proplix-secure-api-gateway-logs-errors-responses)Browse all Proplix Secure API Gateway guides (https://pixiecrm.com/help-centre/category/proplix-secure-api-gateway)Enterprise integrations (https://pixiecrm.com/help-centre/category/enterprise-integrations)Client portal overview (https://pixiecrm.com/help-centre/client-portal-overview)Apply API request throttling (https://pixiecrm.com/help-centre/apply-api-request-throttling)Understand one-way API-token storage (https://pixiecrm.com/help-centre/understand-one-way-saas-api-token-storage)Manage API-token lifecycle metadata (https://pixiecrm.com/help-centre/manage-api-token-expiry-revocation-rotation-and-usage-metadata)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)