Entity Sets

Every set is read-only and scoped to your museum and your key's test mode. Edm.DateTimeOffset values are ISO 8601 UTC timestamps, Edm.Guid values are UUIDs, Edm.Decimal amounts are in the museum's currency (major units). Properties marked data only cannot be used in $filter or $orderby.

Customers, Memberships and MembershipTypes carry updatedAt from the source record: when Loby last recorded a change to it. Not every change updates it, so treat it as a hint, not a guarantee. Visits, tickets, orders and transactions have no reliable change time in Loby, so those sets have no updatedAt; use their own dates (see Power BI & Excel).

Visits

One entry to the venue: a ticket scan, a member checkin, a manual entry or an event ticket scan.

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
visitDateEdm.DateTimeOffsetWhen the visit happened
originEdm.StringTicket, Membership, Manual or EventTicket (data only)
quantityPerson … quantityYoungPersonEdm.Int32Visitors per role: quantityPerson, quantityAdult, quantityChild, quantityInfant, quantitySenior, quantityPensioner, quantityDisabled, quantityVeteran, quantityStudent, quantityYoungPerson (data only)
quantityTotalEdm.Int32Total visitors in the entry
ticketIdEdm.GuidThe scanned ticket, for ticket visits
eventTicketIdEdm.GuidThe scanned event ticket, for event visits
customerIdEdm.GuidThe customer, when known
departmentIdEdm.GuidThe department the visit was registered at
membershipIdEdm.GuidThe membership used, for member checkins
customerMuseumIdEdm.GuidThe visitor's home museum, when a partner-museum member visited you
customerMuseumNameEdm.StringThat museum's name (data only)

Tickets

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
createdAtEdm.DateTimeOffsetWhen the ticket was issued
expiresAtEdm.DateTimeOffsetWhen the ticket expires
numberEdm.Int32Ticket number within the museum
globalNumberEdm.Int32Ticket number across Loby
usedEdm.BooleanWhether the ticket has been used
batchCodeEdm.StringThe batch, for tickets issued in batches
ticketTypeIdEdm.GuidThe ticket type
customerIdEdm.GuidThe buyer, when known
orderIdEdm.GuidThe order it was sold on
locationIdEdm.GuidThe location it admits to
timeSlotIdEdm.GuidThe time slot, for timed tickets

Customers

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
createdAtEdm.DateTimeOffsetWhen the customer was created
updatedAtEdm.DateTimeOffsetWhen Loby last recorded a change to the customer
firstName, lastName, nameEdm.StringName fields
emailEdm.StringEmail address
phoneEdm.StringPhone number
memberNumberEdm.Int32Member number, for members
archivedEdm.BooleanWhether the customer is archived
subscribedToNewsletterEdm.BooleanNewsletter consent
address, postalCode, city, countryEdm.StringAddress fields
gender, nationality, preferredLanguageEdm.StringProfile fields

Memberships

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
createdAtEdm.DateTimeOffsetWhen the membership was created
updatedAtEdm.DateTimeOffsetWhen Loby last recorded a change to the membership
startDateEdm.DateTimeOffsetValidity start
endDateEdm.DateTimeOffsetValidity end; null while open
autoRenewEdm.BooleanWhether it renews automatically
autoRenewedEdm.BooleanWhether it was created by an automatic renewal
renewalEdm.BooleanWhether this row is a renewal of an earlier membership
originEdm.StringWhere it was created, e.g. WEB, POS, ADMIN
membershipTypeNameEdm.StringThe membership type's name (data only)
customerIdEdm.GuidThe member
secondaryCustomerIdEdm.GuidThe second member, on couple memberships
membershipTypeIdEdm.GuidThe membership type
orderIdEdm.GuidThe order it was sold on

Orders

The ORDER rows of the transactions ledger: one row per completed sale.

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
orderDateEdm.DateTimeOffsetWhen the order was completed
orderNumberEdm.Int32Order number
amount, fee, net, vatAmountEdm.DecimalSale total, payment fee, net and VAT
channelEdm.StringSales channel, e.g. POS, WEB
paymentMethodEdm.Stringe.g. CREDIT_CARD, CASH, MOBILE_PAY
cardBrandEdm.StringCard brand, for card payments
pspEdm.StringPayment service provider
bankReferenceEdm.StringReference on the bank statement
customerIdEdm.GuidThe buyer, when known

Transactions

The whole money ledger: orders, refunds and payouts, told apart by type.

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
transactionDateEdm.DateTimeOffsetWhen the transaction happened
typeEdm.StringORDER, REFUND or PAYOUT
amount, fee, net, vatAmountEdm.DecimalAmounts; negative on refunds and payouts
channel, paymentMethod, cardBrand, wallet, psp, bankReferenceEdm.StringPayment details
includeInBalanceEdm.BooleanWhether the row counts toward the payout balance
stripeConnectEdm.BooleanWhether it ran through Stripe Connect
orderNumberEdm.Int32The order number, on order rows
orderIdEdm.GuidThe order, on order and refund rows
customerIdEdm.GuidThe buyer, when known

TicketTypes

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
nameEdm.StringName
skuEdm.StringSKU, for bookkeeping
priceEdm.DecimalPrice
locationIdEdm.GuidThe location it admits to
createdAtEdm.DateTimeOffsetWhen it was created

MembershipTypes

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
nameEdm.StringName
skuEdm.StringSKU, for bookkeeping
priceEdm.DecimalPrice
renewalPriceEdm.DecimalRenewal price, when it differs
coupleEdm.BooleanWhether it covers two members
createdAtEdm.DateTimeOffsetWhen it was created
updatedAtEdm.DateTimeOffsetWhen Loby last recorded a change to it

Departments

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
nameEdm.StringName

Locations

PropertyTypeDescription
idEdm.GuidUnique identifier (key)
nameEdm.StringName
‹ Previous
Power BI & Excel