Configure API-key authentication | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/configure-api-key-authentication Publisher: Pixie Technologies LLC Provider connections, APIs and webhooks Configure API-key authentication Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to send a configured API key/header. Audience: Courier operations staff; Permission: Courier: Manage integrations; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Settings → Providers → Open provider What this guide helps you do Send a configured API key/header. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Select the matching Authentication method. - Enter only the fields required for that method. - Save. - Test the provider. - Check the response without exposing secrets. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - Credentials are encrypted before storage. - Secrets with line breaks are rejected. - Use HTTPS endpoints only. Check it worked - The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action. Security, audit and operational checks - Use the exact record and least-privilege role before changing any state. - Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed. - Use protected document and image routes rather than exposing server filesystem paths. - Keep customer, driver, provider, financial and credential data within the authorised workflow. - For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process. Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful. Related guides Create a provider connection (https://pixiecrm.com/help-centre/create-a-provider-connection)Edit a provider connection without overwriting secrets (https://pixiecrm.com/help-centre/edit-a-provider-connection-without-overwriting-secrets)Understand supported provider types (https://pixiecrm.com/help-centre/understand-supported-provider-types)Configure Bearer authentication (https://pixiecrm.com/help-centre/configure-bearer-authentication)