Poynt
Poynt (GoDaddy Poynt) is an open commerce platform for merchants built around smart payment terminals and a cloud API. Its Poynt Cloud API (services.poynt.net) lets developers build and distribute business apps that read and write orders, transactions, customers, products, catalogs, inventory, taxes and businesses, register webhooks for real-time events, and tokenize card data in the browser with Poynt Collect. Authentication is OAuth 2.0 using a self-signed JWT bearer grant that is exchanged for a short-lived access token. The platform serves three integration audiences: payment processors, terminal OEMs, and independent app developers.
Poynt publishes 1 API on the APIs.io network. Tagged areas include Company, Consumer, Payments, Point of Sale, and Commerce.
The Poynt catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Poynt’s developer surface includes documentation, API reference, getting-started guide, support, authentication, and 17 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Poynt Cloud API
The Poynt Cloud API lets developers manage a merchant business's orders, transactions, customers, products, catalogs, inventory and taxes, register webhooks for real-time events...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Poynt Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll for all 8
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Company 1
The organization behind the API