Counterpoint Connector

Build and embed customer-facing integrations that sync Counterpoint items, customers, inventory and sales with your SaaS app. Orchestrate multi-step flows to create sales tickets, update stock levels and surface Counterpoint customer records natively inside your product.

Build with this Connector Talk to an integration expert

In-app integrations

Surface Counterpoint records natively inside your product.

Reusable orchestration

Build reusable workflows for order and inventory syncing.

Operational control

Centralize error handling, retries and tenant mappings.

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Teams can integrate Counterpoint to read and write items, customers, inventory and sales documents and automate order, stock and customer synchronization. Counterpoint runs on the customer server; integrations call a local CPHive or CP CoreWebServices endpoint and can receive change notifications via CPWebhooks. Use Cyclr to design reusable workflows, map tenants and publish white-label in-app integrations.

PRODUCT USE CASES

Top Use Cases for Counterpoint Integrations

Quickly create integrations between your SaaS application and Counterpoint with Cyclr’s low code builder. Publish Counterpoint integrations into your application using Cyclr’s embedded integration marketplace and automate flows like inventory sync, customer provisioning, and order creation across multiple customer sites.

Push item and inventory updates to ecommerce

Sync Counterpoint Items and inventory quantities to your ecommerce catalog when stock or price changes occur.

Create sales tickets and orders from your app

Create Counterpoint Documents (sales tickets/orders) from orders placed in your SaaS platform to centralize sales processing.

Sync customer records and loyalty data

Provision or update Counterpoint Customer records and loyalty fields when users are created or updated in your app.

ORCHESTRATION

How Counterpoint works with Cyclr

Cyclr sits between your SaaS product and Counterpoint to handle authentication, govern access and orchestrate every API call per customer, at scale.

1
Your SaaS product
Your app requests an action for a specific customer.
2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
3
Counterpoint
Counterpoint processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Counterpoint methods you can orchestrate through Cyclr.

Categories4

List Item Categories

Action

Gets a list of all Categories and subcategories in the system.

List eCommerce Categories

Action

Lists eCommerce category information.

Get Category

Action

Get a category by category code.

Get Item Category

Action

Gets information about a category and it's child subcategories

Pay Codes1

List Pay Codes

Action

Gets information about all pay codes for a company.

Tax Codes1

List Tax Codes

Action

List all tax codes configured in the system.

Gift Cards2

List Gift Cards

Action

List all gift cards.

List Gift Card Codes

Action

Gets a list of gift card codes.

Items4

Get Item

Action

Get an item by item number.

List New Items

Action

List all new items created since the last successful run.

List Items

Action

List all items.

Get Item Inventory

Action

Get the inventory of an item by item number and location ID.

Documents3

Create Document Payments

Action

Adds a collection of lines to an existing document.

Create Document

Action

Create a completed document/ticket in the database.

Get Document

Action

Get a document by document ID.

Customers4

List Customers

Action

List all customers.

List Customers EC

Action

List all customers EC information.

Get Customer

Action

Get a customer by customer number.

List New Customers

Action

List all new customers created since the last successful run.

Users2

List Users

Action

Lists all users.

Get User

Action

Get a user by user ID.

Inventory2

List Inventory Locations

Action

List all inventory locations.

List Inventory Quantity

Action

List all inventory quantity by location ID.

TECHNICAL DETAILS

Counterpoint integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Counterpoint integrations in Cyclr.

API and authentication

API host: Customer's Counterpoint server (CPHive or CP CoreWebServices URL)
Authentication: Token (CPHive) / Basic / APIToken
Credentials: CP Api Url; CP Api Username; CP Api Key (saved); system username/password for admin endpoints.
Method categories: Read/write Customers, Items, Inventory, Documents (sales/orders), Timecards, Messages, Admin endpoints.

View vendor API documentation →

Pagination and rate limits

Pagination

CPHive responses are unpaged; CoreWebServices returns full result sets. Handle full payloads or implement batching in workflows.

Rate limits

Refer to the vendor API documentation for current limits.

IMPLEMENTATION

Authentication at a glance

Counterpoint exposes on-prem APIs (CPHive or CP CoreWebServices). Integrations request a token from CPHive’s /token using a CP Api Username; some admin endpoints require Basic auth or APIToken parameters.

Authentication method: Token (CPHive) / Basic / APIToken
Credential required: CP Api Url; CP Api Username; CP Api Key (saved); system username/password for admin endpoints.

Before you begin:

Requires installing CPHive and CPWebhooks on each Counterpoint server; must be internet-reachable with valid certificate.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It can read and write Counterpoint Items, Customers, Inventory and Documents (sales/orders), automate inventory and order sync, and surface customer or ticket data inside your app. Implementation uses the on-prem CPHive or CP CoreWebServices endpoints and optional webhooks.

Counterpoint integrations use a token model from the local CPHive /token endpoint (CP Api Username). Some admin or system endpoints require Basic auth or an APIToken parameter; developer API keys are required for certain vendor-restricted endpoints.

Yes. Each customer supplies their own CPHive/CP CoreWebServices URL and credentials; Cyclr maps tenants and deploys the same orchestrations per customer for multi-tenant embedding.

Yes. Cyclr can expose CPHive method calls as governed MCP tools with centralized governance, tenant configuration, and reusable workflow building blocks.

KEEP EXPLORING

Related resources and connectors

Documentation

Counterpoint Connector

In-app integrations

Reusable orchestration

Operational control

Embedded experience

Overview

Top Use Cases for Counterpoint Integrations

Push item and inventory updates to ecommerce

Create sales tickets and orders from your app

Sync customer records and loyalty data

How Counterpoint works with Cyclr

Your SaaS product

Cyclr orchestration

Counterpoint

Available connector capabilities

List Item Categories

List eCommerce Categories

Get Category

Get Item Category

List Pay Codes

List Tax Codes

List Gift Cards

List Gift Card Codes

Get Item

List New Items

List Items

Get Item Inventory

Create Document Payments

Create Document

Get Document

List Customers

List Customers EC

Get Customer

List New Customers

List Users

Get User

List Inventory Locations

List Inventory Quantity

Counterpoint integration and API details

API and authentication

Pagination and rate limits

Pagination

Rate limits

Authentication at a glance

Frequently asked questions

Related resources and connectors

CRM Integrations you should be using

What is iPaaS?

MCP PaaS

SalesPad

ActiveCampaign

Aircall

Let Cyclr handle the integrations.