AI Support

Integrating Vemcount with External Systems: API, Data Push & POS

Written by Vemco Support | Aug 19, 2026, 1:06:52 AM

Overview

Vemcount supports integration with external systems including BI platforms, ERP systems (such as SAP), retail partner APIs, and POS solutions. This article covers how to set up and troubleshoot data integrations using the Vemcount API and automated export features.

Vemcount REST API (v4)

Requesting API Access

To access the Vemcount API, submit a support ticket with:

  • Your company name and Vemcount company ID or URL

  • The purpose of the integration (e.g. PowerBI dashboard, SAP data feed, custom BI tool)

  • Preferred data format (JSON) and pull frequency (hourly, daily, etc.)

Support will provide an API token and link to the REST API v4 documentation.

API Key Management

  • API keys are account-specific and should be stored securely.

  • To rotate or revoke an API key, contact support — do not share keys across multiple integration partners.

  • To whitelist specific IP addresses for API access, include the IP range in your request ticket.

Automated Data Push (Export) to External Systems

Vemcount can push footfall data automatically to external endpoints (retail partner APIs, aggregator platforms, or internal systems). This is configured per location by the Vemco technical team.

Setting Up a Push Export

Submit a ticket specifying:

  • Target endpoint URL or SFTP details

  • Authentication method (API key, OAuth token, basic auth)

  • Data format required (JSON, CSV, XML)

  • Push frequency (real-time, hourly, daily)

  • Locations to include

Troubleshooting a Failed Export

If data stops flowing to a connected system, check the following:

  • Authentication expired: OAuth tokens and API keys expire. Re-authenticate on the receiving system and update the credentials in the Vemcount export configuration.

  • Endpoint timeout: If the receiving API is slow or unavailable, Vemcount's export will log a timeout error (e.g. cURL error 28: Operation timed out). Verify the endpoint is reachable, then contact support to re-trigger the failed exports.

  • Export error log: In the Vemcount platform, navigate to the location's export settings to view the export log. Copy the error message and include it in your support ticket.

  • Data mismatch vs. BI: If Vemcount shows correct data but your BI tool reports different numbers, check whether the API is applying a different timezone or aggregation interval than expected.

POS / Sales Data Integration

Connecting a POS System

Vemcount supports integration with various POS systems for combined footfall and sales analytics. To connect a POS system:

  • Open a support ticket specifying the POS system name and version.

  • Provide the store location IDs and POS integration credentials or API endpoint details.

  • Allow 2–5 business days for the technical team to configure the integration.

Switching POS Providers

If you are migrating from one POS system to another:

  • Notify support in advance of the switchover date.

  • Provide the old and new POS system names and the affected location IDs.

  • The technical team will reconfigure the integration to point to the new system.

Uploading Sales Data Manually (SFTP/FileZilla)

For bulk sales data uploads via SFTP:

  • Contact support to receive SFTP credentials and the required file format specification.

  • Files uploaded via SFTP are processed automatically and viewable in the Vemcount sales analytics dashboard.

  • To check upload logs or verify whether an upload was processed, contact support with the filename and upload date.

Managing POS Terminal IDs and Store Codes

If you need to update POS Terminal IDs, Active/Closed Dates, or map Lease Codes to store locations in bulk, contact support with a structured list of the changes required. Bulk updates are handled by the technical team and are not currently self-service.

Getting Support

For integration issues, always include in your ticket:

  • The location name and Vemcount URL

  • The error message or export log entry

  • The date and time the issue started

  • The name of the connected system