Skip to content

Blog · 16/11/2026

How Apointoo labels its 22 integrations

A clear breakdown of Apointoo’s 22 catalog entries: what is Production, Beta, Via API and still Planned, plus the TypeScript SDK stack.

Apointoo’s integration catalog lists 22 entries. That number describes the size of the catalog, not 22 integrations ready for every customer. Each entry carries a delivery status so teams can distinguish what is available from what is still a specification.

What the 22 entries mean

  • 5 Production: marked as available in the current catalog.
  • 2 Beta: shipped paths whose current scope and limits are documented on their pages.
  • 1 Via API: available through the API rather than a native point-and-click connector.
  • 14 Planned: spec-grade descriptions of future connectors; the integrations are not built yet.

In the repository, Production, Beta and Via API are explicitly treated as shipped reality. Planned entries are described as planned and should not be represented as live. The distinction matters when an agency is choosing a customer workflow: a connector page can describe intended behavior without proving that the connector exists in production.

Where Apointoo fits in the conversion path

The product is designed to keep a Google Ads click connected to a lead as it moves through intake and booking, then send confirmed sale outcomes back as offline conversions. The value of the integration layer is the handoff between the first visit and the later business outcome. A booked appointment, a paid sale, and a changed or refunded sale are different states; a useful system needs to preserve enough context to report the state that actually happened.

Consent rules remain part of that path. Apointoo’s copy and integration pages describe attribution and conversion delivery subject to the site’s consent setup. The presence of an integration entry does not remove the need to configure consent, verify a customer’s event flow, or confirm that a provider accepted a delivery.

The stack behind the product

The public Apointoo SDK is written in TypeScript and uses Hono for server handlers and Zod for validation. Its first public source release is version 0.12.2; the package README marks it pre-1.0, notes that APIs may change between minor releases, and documents installation from a tagged GitHub release rather than npm.

The product website is a separate application, built with Next.js 16.2.6, React 19.2.4 and Tailwind CSS 4. Separating the SDK from the marketing site keeps the integration runtime and the product’s public explanation as distinct parts of the system.

How to use the catalog

Start with the exact workflow you need, then read the status and documented limits on that connector’s page. Treat Planned as a roadmap description, not a delivery promise. Before using a shipped path for a customer, run a real account-level validation for consent, event mapping, provider acceptance and correction behavior.

The catalog currently has 22 entries (5 Production, 2 Beta, 1 Via API and 14 Planned, checked on 16 November 2026). Statuses can change as implementation and validation progress. See Apointoo.

← Blog