Connect RetailHawk to the systems your programme already relies on.
Use RetailHawk as the operating layer for fieldwork while keeping external questionnaires and adjacent systems where they still make sense.
Integration options
External survey providers
Connect configured external questionnaire providers so confirmed completion can feed the RetailHawk visit record. Integrations are configured for the provider and programme; support for every third-party service is not implied.
API integrations
RetailHawk uses authenticated, tenant-scoped APIs. Customer-facing API integration is scoped to the authorised resources and workflow required; internal application endpoints are not presented as an unrestricted public API.
Callbacks and event integration
The configured external-provider pattern accepts authenticated completion callbacks. Outbound webhooks or other event-delivery requirements are defined and tested for the system and programme involved rather than assumed as a universal webhook catalogue.
Integration boundaries that stay explicit
No secrets in tenant data
Provider credentials and endpoints stay outside customer-visible programme data.
No silent fallback
A provider failure is surfaced explicitly rather than silently treated as a successful completion.
Historical integrity
Published work retains the provider context it was issued with, so later integration changes do not redefine historical visits.
Configured, not assumed
RetailHawk integration capability is configured around the systems and data flows a programme actually needs; named third-party compatibility is confirmed during discovery.