Add-on
Extra capacity bought on top of a plan: an extra member or an extra number, each billed monthly or yearly with the plan. See Plans and limits.API key
Your bearer credential (Authorization: Bearer …). Prefix sk_test_ or sk_live_ selects the mode. Keys carry scopes and optional phone-number / IP restrictions — see Authentication.
Automation pack
A named bundle of starter templates and workflow defaults a platform can provision for a platform customer at setup time. See Automation packs.Broadcast
A one-to-many outbound campaign paced to Meta’s messaging-limit tier rather than fired all at once. See Broadcasts.BSUID
Business-scoped user id — Meta’s opaque recipient identifier when a phone number is not available. Address it withrecipient: { "type": "bsuid", "value": "…" } on send. See Messages.
Capability
A feature flag for a connection (calling, block lists, flows, and so on). AskGET /v1/capabilities instead of hard-coding what a number supports.
Connection
One WhatsApp Business Account and its phone numbers in a workspace. Credentials live here. Select it withphone_number_id or connection_uuid when you have more than one. See Workspaces and modes and Connecting WhatsApp.
Contact
The person being messaged — never “user” (a user is someone who logs into LazyApp). Identified by phone, BSUID, or your own external id.Conversation
The thread between a connection and a contact. Inbox and some webhooks key offconversation_id.
Customer service window
The 24-hour period after a contact’s last inbound message during which free-form (non-template) messages are allowed. Outside it, only an approved template will send. Reported asservice_window on the contact.
Embedded Signup
Meta’s hosted flow that connects a WhatsApp Business Account into LazyApp without you collecting tokens by hand. Platforms often wrap it in a setup link. See Connecting WhatsApp.Event (application event)
A business signal you POST to/v1/events (order shipped, appointment reminder) that LazyApp can map to a template send. Distinct from a webhook event LazyApp delivers to you.
Idempotency-Key
Optional header on every write under/v1. Retrying the same key with the same body replays the original response instead of double-sending. Messages also accept a body idempotency_key for permanent dedupe. See Idempotency.
Media
A file uploaded to Meta through LazyApp (POST /v1/media or /v1/media/url) and referenced by media_id when sending. Meta’s copy expires in about 30 days; retention controls whether LazyApp keeps a copy. See Media.
Message
One outbound or inbound WhatsApp message. Status movesqueued → sent → delivered → read / played, or failed. Schedule with send_at. See Message lifecycle.
Mode
live or test — never “environment”. Taken from the API key prefix. Data never crosses modes. See Workspaces and modes.
phone_number_id
Meta’s id for a specific WhatsApp Business phone number on a connection. Pass it on send when the workspace has more than one number.Plan
The flat monthly subscription (Starter, Growth or Pro) that pays LazyApp. It sets how many numbers and members a workspace has, its live broadcast sends a month, and which features it gets; live API keys and webhooks need Pro. LazyApp adds 0% to Meta’s message rates: Meta bills messages to the business directly. Test mode is free and never plan-limited. A live key below Pro gets402 plan_limit_reached. See Plans and limits.
Platform
A LazyApp workspace for a platform team: it owns platform customers, issues setup links, and can act on a customer’s behalf withX-LazyApp-Customer. See Build a platform.
Platform customer
Your customer when you resell LazyApp. Each gets an isolated workspace with its own connections, keys and data. Identified bypublic_id (cus_…), uuid, or your external_id.
Quality rating
Meta’sGREEN / YELLOW / RED signal for a number, exposed on capabilities. Sliding to RED can cut the messaging-limit tier.
Request id (X-Request-Id)
Correlation id on every /v1 response. Echo your own or accept LazyApp’s. For support tickets, not for idempotency — use Idempotency-Key.
Reseller (brand)
A partner who offers LazyApp under their own brand, on their own host. Each client signs up on that host and gets their own workspace; the reseller pays LazyApp’s plan price for each client from the reseller’s wallet and bills clients however they like, outside LazyApp. Distinct from a platform, which integrates through the API. See Resellers.Scope
A permission on an API key such asmessages:send or webhooks:write. A call outside the key’s scopes returns 403. See Scopes.
Setup link
A one-time URL (set_…) a platform sends so a platform customer can connect WhatsApp themselves. See Setup links.
Template
An approved WhatsApp message template (utility, marketing, or authentication). Required outside the customer service window. See Templates.User
Someone who signs into the LazyApp console. Not a contact.Verify
LazyApp’s OTP send/check API for phone verification flows. See Verify.WABA
WhatsApp Business Account — Meta’s container for your business numbers. LazyApp stores it as part of a connection. Meta bills messages to the WABA’s own payment method at Meta’s rates, and LazyApp adds 0%. See Meta message billing and WhatsApp message rates.Wallet
Prepaid INR balance, topped up by card with Add money. Only two kinds of account have one: a reseller, whose wallet pays LazyApp’s plan price for each client workspace, and a platform team, whose wallet pays the monthly charge per connected customer number (and Meta’s charges, when LazyApp pays Meta for a number). An ordinary workspace has no wallet: its plan is billed to a card, and Meta bills its messages directly. See Wallets.Webhook
An HTTPS endpoint you register that receives events (message.received, message.delivered, …). Delivery is at-least-once — dedupe on the event id — and signed with X-LazyApp-Signature. See Webhooks.