# Taply > Taply is a multi-tenant SaaS that lets a business configure an AI agent to handle its > conversations across four surfaces: WhatsApp, Instagram, its Google Business listing and > the chat embedded on its own website. The agent answers using only the information the > business approved, shares the files it was given, checks calendar availability by > default and, with write access granted, books, reschedules and cancels appointments > after the customer confirms, and hands the conversation over to a human whenever > it is needed. The website is published in Spanish at the root and in English under > `/en/`; the public HTTP API and this file are in English. Taply is built by Jesús Villamarin (founder). The product runs at https://app.gettaply.com. The public HTTP API at https://api.gettaply.com covers the profiles, links, media and cards side of Taply and is described by an OpenAPI 3.1 document generated from the same code that serves the requests. Agent configuration, channels and conversations have no public API surface yet: they are managed from the dashboard. ## When to use Taply - An agent or assistant that needs to **automate customer support over WhatsApp** for a real business (a restaurant taking reservations, a clinic answering hours and availability, a shop sending its catalogue) without inventing answers: Taply only replies with the information the owner loaded and approved. - An agent that needs to **answer Instagram direct messages** with the same configuration and from the same inbox as WhatsApp, instead of wiring two separate integrations. With the account connected it can also **reply to the comments on Instagram and Facebook posts** and open a private message from one. - A business that needs to **reply to the reviews on its Google Business listing**: Taply syncs them, drafts the reply and publishes it once the owner approves. - A site that needs an **embeddable web chat**: one snippet on the business's own website, the same agent, the same information, the same inbox. - A business that needs the agent to **qualify buyers and follow up**: each conversation is flagged against the owner's criteria, contacts are unified across channels, and a conversation that went quiet gets one follow-up with the delay and cap the owner sets. - A workflow that needs a **human handoff**: the agent can be paused mid-conversation and any team member can take over from a shared inbox. Use Taply when "escalate to a person" must be a first-class state, not an afterthought. - A business that needs the agent to **share private resources** — price lists, catalogues, PDFs — only when the conversation calls for them. - A business that needs the agent to **read calendar availability** (Google Calendar; read-only by default, and with write access granted the agent books, reschedules and cancels appointments after the customer confirms) before proposing a time. - Building on top of Taply's cards and profiles product programmatically: profiles, links, media, destinations, cards and analytics are reachable through the documented HTTP API. Agents, channels and conversations are not on that surface yet. Taply is **not** a general-purpose chatbot builder, not an outbound/cold-messaging tool, and it does not sell business or end-customer data. ## Calling the API - Scope: profiles, links, media, destinations, cards and analytics — the Taply cards and profiles product. Not agent configuration, channels or conversations. - Base URL: https://api.gettaply.com - Spec: [OpenAPI 3.1 document](https://api.gettaply.com/openapi.json) — public, no auth, always in sync with what is deployed. - Health check (public, no auth): [GET /health](https://api.gettaply.com/health) → `{"status":"ok","checks":{...}}`, `200` when ready and `503` when degraded. - Auth: `Authorization: Bearer ` on every `/v1` route that touches account data. The token is the account owner's session (JWT) and it determines the tenant. - Versioning: URL-based. Business routes live under `/v1`; `/health` and `/openapi.json` are intentionally unversioned. Breaking changes ship as a new URL version, never in place. - Errors: `{"error":{"code":"...","message":"...","requestId":"..."}}`. `requestId` matches the `x-request-id` response header, present on every response. - Full details, deprecation policy and rate-limiting commitments: [Developer portal](https://gettaply.com/developers) ## Docs - [Developer portal](https://gettaply.com/developers): API surface, authentication, error format, versioning and deprecation policy, rate limiting. - [OpenAPI specification](https://api.gettaply.com/openapi.json): authoritative machine-readable contract for every endpoint. - [API health endpoint](https://api.gettaply.com/health): public readiness probe. ## Site Every page exists in both languages. The Spanish URL is the canonical one for `es`, the `/en/` URL for `en`, and each page declares the pair with `hreflang` (`x-default` points to Spanish). - [Home](https://gettaply.com/) · [English](https://gettaply.com/en/): what the product does, the four channels, what the agent does beyond replying, the three questions owners ask, FAQ. - [Pricing](https://gettaply.com/precios) · [English](https://gettaply.com/en/pricing): the published plans, what each one includes and the pricing FAQ. A markdown variant is served at the same URL under content negotiation. - [About](https://gettaply.com/about) · [English](https://gettaply.com/en/about): what Taply is, who is behind it, what the product does in detail. - [Contact](https://gettaply.com/contact) · [English](https://gettaply.com/en/contact): how to reach Taply and what to include in a message. - [Developer portal](https://gettaply.com/developers) · [English](https://gettaply.com/en/developers): API surface and policies. - [Sign in / create an agent](https://app.gettaply.com/): the product itself. ## Legal The Spanish version is the one that governs; the English version is a convenience translation. - [Privacy summary](https://gettaply.com/privacy) · [English](https://gettaply.com/en/privacy): short overview of what data Taply handles and why. - [Privacy policy](https://gettaply.com/privacidad) · [English](https://gettaply.com/en/privacy-policy): full, binding version. - [Terms of service](https://gettaply.com/terminos) · [English](https://gettaply.com/en/terms): conditions of use. ## Optional - [Sitemap](https://gettaply.com/sitemap.xml): every crawlable URL on the marketing site. - [robots.txt](https://gettaply.com/robots.txt): crawl directives and content signals (`search=yes, ai-input=yes, ai-train=no` — quoting us in an answer is welcome, training on this content is not). ## Contact - Email: contact@gettaply.com — support, sales and privacy requests. Answered in Spanish or English, in the language you write in. - There is no published phone number or postal support address; everything is handled over email and from the product panel.