Skip to content
FOPilot

Integrations and credentials

What each connected service is used for, which credential it needs, where the user gets it, and what FOPilot can do with it.

Users connect their own accounts; FOPilot calls the providers' official APIs with those credentials. Credentials are validated with a live call before saving and stored encrypted.

Service Credential Where the user gets it Used for
Nova Poshta API 2.0 API key Business cabinet → Settings → Security → My API keys → Create key city/branch search, price & delivery date, waybill create/delete, document list, tracking, label PDFs
Prom.ua public API personal API token (Bearer) Seller cabinet → Settings → API token management orders list/get/status, attach waybill number, products price/stock
Horoshop API store domain + admin login/password (token from api/auth) Store admin → Settings → Admins (a dedicated admin for the integration) orders get/update (status, external tracking code)
Rozetka Seller API seller cabinet login + password (sent base64-encoded to /sites) Rozetka seller cabinet order search/get, allowed status changes, waybill number
KeyCRM OpenAPI API key (Bearer) KeyCRM → Settings → General → API key orders, statuses, tracking code, stock
Checkbox (PRRO) cash register license key + cashier login/password or PIN; production or test environment Checkbox web cabinet shift status/open/close (Z-report), sale and return receipts, receipt list
monobank personal API personal token (X-Token) https://api.monobank.ua/ balances and statements, read-only; 1 request per 60 s per token is enforced by FOPilot

Security notes: the Nova Poshta key never appears in links — label PDFs are streamed through short-lived signed URLs; Horoshop domains must be public hostnames (SSRF protection); no tool can move money.