Configure the BP fuel connection | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/configure-the-bp-fuel-connection Publisher: Pixie Technologies LLC BP fuel connection, fuel cards and reconciliation Configure the BP fuel connection 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 create the secure connection used to fetch fuel transactions. Audience: Courier operations staff; Permission: Courier: Manage integrations; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Settings → BP Fuel What this guide helps you do Create the secure connection used to fetch fuel transactions. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects. Follow these steps - Select sandbox or production environment. - Select authentication method. - Enter public HTTPS base URL and transactions endpoint. - Enter required credentials/token endpoint. - Enter mapping JSON containing transaction_id and transaction_at. - Set interval from 15 to 1,440 minutes. - Save inactive. - Test. - Activate only after validation. Fields and options Environmentproduction or sandbox; other values fall back to sandbox. Authenticationoauth2, bearer, api_key or none. Required mappingtransaction_id and transaction_at. Interval15–1,440 minutes. Rules and limits - Active configuration requires base URL and transactions endpoint. - Authentication-specific credentials must be present. - Header values and secrets are sanitised; line breaks are rejected. 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 Test the BP fuel connection (https://pixiecrm.com/help-centre/test-the-bp-fuel-connection)Run a manual BP fuel sync (https://pixiecrm.com/help-centre/run-a-manual-bp-fuel-sync)Understand automatic BP fuel sync timing (https://pixiecrm.com/help-centre/understand-automatic-bp-fuel-sync-timing)Create a fuel card (https://pixiecrm.com/help-centre/create-a-fuel-card)