Ids

A record's id is a prefix, an underscore and a 10-character body. cus_K1BROJhqzZ is Riverside Property, a Customer of Leaseline.

Prefix, then bodyCopy Anchor Link

Prefixes are short where Stripe set the pattern: cus for a Customer, sub for a Subscription, inv for an Invoice and evt for an Event. Every other Noun uses its own name, such as offer and startup.

A Noun a Startup adds takes its own name as its prefix. Leaseline's Lease records are ids such as lease_4loEed1JG4.

Never parse the bodyCopy Anchor Link

The body holds no date, no counter and no type, and its length never changes. Store an id whole, compare it whole, and pass it back unchanged.

• To learn the Noun, read the prefix or the record's $type.
• To order records, sort by createdAt or by an Event's seq, never by id.
• To learn whether a record exists, get it: a well-formed id can name nothing.

Where an id goesCopy Anchor Link

An id is the last segment of the record's $id. Every input that names a record takes either form:

import { $ } from 'startup-builder'

await $.Invoice.collect({ invoice: 'inv_FXANyzQojc' })
await $.Invoice.collect({ invoice: 'https://api.sb/leaseline.app/invoices/inv_FXANyzQojc' })

The namespace in $id names the Startup that holds the record, and an id is unique within its namespace.

Keys are not idsCopy Anchor Link

A key is a credential, never a record id. leaseline_sk_live_ begins every live secret key Leaseline's Customers hold: the Brand, the kind and the environment.

The API Key record behind a key has an id of its own, key_KpTRSdhqzZ, and no $id ever holds the secret. Keys lists every kind.

Every prefixCopy Anchor Link