Customer

Interest alone makes a Lead, not a Customer.

PropertiesCopy Anchor Link

ObjectCopy Anchor Link

{
  "$id": "https://api.sb/kilnbakery.com/customers/customer_1",
  "$type": "Customer",
  "since": "2026-10-22T12:00:00Z",
  "outside": true,
  "status": "trialing",
  "billingEmail": "tomas@kilnbakery.com",
  "billingAddress": "Example billing address",
  "taxIds": [
    "Example tax ids"
  ],
  "creditRecharge": {}
}

RelationshipsCopy Anchor Link

• A Customer accepts many Offers: a party becomes a Customer by accepting any Offer, at any price including zero. accepts, inverse acceptedBy.
• A Customer is acquired by one Acquisition: a Customer inherits the Acquisition of the Lead it was; Metrics and payouts read this one row. acquiredBy, inverse customers.
• A Customer has one Contact: a Contact becomes a Customer on accepting an Offer. contact, inverse becomes.
• A Customer has many Credit Grants: the Customer whose metered calls spend the balance; credits never move to another Customer. creditGrants, inverse credits.
• A Customer holds many Entitlements: a Customer’s Entitlements are what it may do right now, granted by the Offers it accepted. holds, inverse heldBy.
• A Customer has many Invoices: each Invoice is owed by one Customer. invoices, inverse charges.
• A Customer maintains many Subscriptions: a Customer holds Subscriptions, each billed once per Period. maintains, inverse subscriber.
• A Customer opens many Conversations: the Customer a Conversation serves, so every answer reads that Customer’s records. opens, inverse customer.
• A Customer owns one Tenant: each Customer has one Tenant: the partition of the Startup’s data that no other Customer reads. owns, inverse ownedBy.
• A Customer places many Orders: a Customer commits to one-time purchases as Orders. places, inverse placedBy.
• A Customer saves many Payment Sources: a Customer saves the Payment Sources its Orders, Subscriptions and Invoices charge; each belongs to one Startup and never moves to a sibling. saves, inverse savedBy.
• A Customer is served by one Startup: a Startup serves every party that has accepted one of its Offers. servedBy, inverse serves.
• A Customer signs into one Portal: Customers sign in to a Portal to order, track delivery, accept work, and pay. signsInto, inverse serves.

LifecycleCopy Anchor Link

VerbsCopy Anchor Link

1. createCreates a Customer.
   POST /{namespace}/customersdoCustomer.created
2. getReturns one Customer by id.
   GET /{namespace}/customers/{id}readNo Event
3. listReturns Customers, newest first, one page at a time.
   GET /{namespace}/customersreadNo Event
4. updateChanges the given properties of a Customer.
   PATCH /{namespace}/customers/{id}doCustomer.updated
5. deleteDeletes a Customer; its history is kept.
   DELETE /{namespace}/customers/{id}doCustomer.deleted
6. activateActivate marks a Customer activated on an Offer once its declared activation Event reaches the count within the window.
   POST /{namespace}/customers/{customer}/activatedoCustomer.activated
7. exemptExempt records a Customer’s exemption or resale certificate, verifies it, and stops tax on its Orders where the certificate applies.
   POST /{namespace}/customers/{customer}/exemptdoCustomer.exempted

PermissionsCopy Anchor Link

Which Access level may call each Verb. One-way Verbs wait their delay window.

StripeCopy Anchor Link

Customer (customer). The source of truth is db.sb, and Stripe holds a copy written from it.

Call itCopy Anchor Link

Activate the latest customer with an offer.

ExampleCopy Anchor Link

A developer who takes a $0 API key accepts an Offer and becomes a Customer, with since set to that day. A developer who joins the Waitlist accepts nothing and stays a Lead.