Tagify

API overview

Today Tagify exposes many PHP handlers under /api/ for authenticated business and check-in flows. A public /api/v1 JSON REST contract is planned.

What exists today

Representative families include check-ins, wallet/cards, Stripe billing helpers, business CRM endpoints, inquiries, and scan-device pairing. Most expect a logged-in business session.

What is planned

A versioned /api/v1 surface with API key headers is documented as a future contract—not something to assume is generally available yet.

Integration guidance

Prefer documented scan-device pairing for kiosks. Avoid fragile long-lived browser sessions for machine-to-machine use.

Authentication Talk to us

Related

Authentication

Know which auth model you are calling—session for most live handlers, planned key headers for /api/v1.

Webhooks

Event-driven hooks keep billing and ops automation in sync with Tagify without manual polling.

QR scan devices

Optional paired devices for desks and kiosks when phones alone are not enough for your traffic pattern.

Docs

Practical guides for launching Tagify at your gym or membership business.