# Overview

Source: https://developers.weerom.com/docs/use-cases

> Ten things people build on the WeerOm API, each with the key it needs, the steps, a code sketch and what the API cannot do for it.

Each use case names who it is for, the endpoints and the kind of key, the steps, a short sketch in JavaScript, and its limits. The sketches call only real WeerOm endpoints and fields. Where another product comes in, a named function such as `createBillitInvoice(payment)` stands for your own code, which you write from that product's documentation.

- [Send payments to Billit](https://developers.weerom.com/docs/use-cases/billit.md): Make one invoice in Billit for every payment staff note in WeerOm. Keys: Read key.
- [Bookkeeping with Accountable](https://developers.weerom.com/docs/use-cases/accountable.md): Build the admin's Accountable lines from the payments: one per day and payment method. Keys: Read key.
- [Your own booking page](https://developers.weerom.com/docs/use-cases/booking-page.md): Your own design on any site, with WeerOm's agenda, rules and mail behind it. Keys: Public key, Write key.
- [Bookings in your calendar](https://developers.weerom.com/docs/use-cases/calendar.md): Copy every booking into Google Calendar or Outlook and keep the copy current. Keys: Read key.
- [Customers in a mailing tool](https://developers.weerom.com/docs/use-cases/newsletter.md): Keep a Mailchimp or Brevo list in step with the shop's customers. Keys: Read key.
- [A revenue sheet](https://developers.weerom.com/docs/use-cases/revenue-sheet.md): Revenue per day, per staff member and per payment method in Google Sheets. Keys: Read key.
- [Automations](https://developers.weerom.com/docs/use-cases/automations.md): A flow in n8n, Make or Zapier, started by a WeerOm webhook or on a schedule. Keys: Read key, Write key.
- [Messages by SMS or WhatsApp](https://developers.weerom.com/docs/use-cases/messages.md): Send tomorrow's customers a text or a WhatsApp message through your own provider. Keys: Read key.
- [An assistant that books](https://developers.weerom.com/docs/use-cases/assistant.md): A chat or phone assistant that finds free times and books them from your server. Keys: Write key.
- [Several shops on one screen](https://developers.weerom.com/docs/use-cases/several-shops.md): One key for each shop and one loop, for an owner with two shops or a group. Keys: Read key.

## The kinds of key

| Key | Starts with | Use it for |
| --- | --- | --- |
| **Read key** | `wo_live_` | A server that reads: invoices, bookkeeping, calendars, sheets, dashboards. |
| **Write key** | `wo_live_` | A server that also books, cancels, moves or blocks. |
| **Public key** | `wo_pub_` | A booking page in the browser. |

[Authentication](https://developers.weerom.com/docs/authentication) says what each may do and how a shop makes one.

## Following changes

A use case that follows changes can hear about them in two ways.

- **Webhooks.** WeerOm posts a signed message to your server a few seconds after a booking is made, changed or cancelled, or a payment is noted. The invoices, the calendar, the reminders and the automations use them. See [Webhooks](https://developers.weerom.com/docs/webhooks).
- **Polling.** A job asks on a schedule, with `updated_after` on bookings and customers or `paid_after` on payments. One run that finds nothing costs one request. At 120 requests a minute for each key, a job every 5 or 15 minutes uses a small part of it. Customers send no webhook, so the newsletter polls. The revenue sheet polls because once an hour is enough.

Where both fit, each page says which to pick.
