Use POST for session creation | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/proplix-secure-api-gateway-session-authentication-method Publisher: Pixie Technologies LLC Master-token and short-lived client sessions Use POST for session creation Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Other methods return 405. Audience: CRM administrators, integration developers, external portal backend teams and security reviewers; Permission: Valid active master portal token; Module v1.0.0; Where to goExternal backend → POST /proplix_api_gateway/portal_api/session 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 Other methods return 405. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to External backend → POST /proplix_api_gateway/portal_api/session. - Find the record, endpoint, field or action used to use post for session creation. - 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 endpointExternal backend → POST /proplix_api_gateway/portal_api/session PurposeOther methods return 405. 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 use post for session creation 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 Call the session endpoint (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-session-authentication-endpoint)Send the master bearer token (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-session-authentication-bearer)Master-token and short-lived client sessions (https://pixiecrm.com/help-centre/topic/proplix-secure-api-gateway-session-authentication)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)