> ## Documentation Index
> Fetch the complete documentation index at: https://www.spacebring.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Discover the latest changes to the Spacebring API and webhooks.

Subscribe to our [newsletter](https://www.spacebring.com/partnership#subscribe) to be notified about developer platform updates.

**November 19, 2026**

A credit transaction returns `endingBalance`, the customer's total credits balance right after the transaction. [Retrieve a credit
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-credit-transaction.md), [retrieve credit
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-credit-transactions.md) and [create a credit
transaction](https://www.spacebring.com/docs/developer/api/transactions/create-a-credit-transaction.md) return it. Transactions created before this change, and the
expiration of credits that lapsed on their expiration date, have no `endingBalance`.

**November 18, 2026**

[Retrieve redemptions](https://www.spacebring.com/docs/developer/api/discounts/retrieve-redemptions.md) returns a `status` on each redemption. A redemption is `pending`
from the moment a coupon or promo code is applied to a purchase, and `approved` once the purchase is completed. A pending redemption is
removed when the payment fails or is canceled. A redemption of a product added to an invoice returns the invoice as `product.invoiceRef`.

**November 18, 2026**

A payment an administrator took in person with Tap to Pay has `payment.method.paymentGateway.inPerson` set to `true`. It is still a Stripe
payment, refunded like any other, but has no checkout page to complete. [Get a booking](https://www.spacebring.com/docs/developer/api/resources/get-a-booking.md), [retrieve
bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md), [get an order](https://www.spacebring.com/docs/developer/api/shop/get-an-order.md), [retrieve
orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md), [retrieve a ticket](https://www.spacebring.com/docs/developer/api/events/retrieve-a-ticket.md), [retrieve
tickets](https://www.spacebring.com/docs/developer/api/events/retrieve-tickets.md), [retrieve a money transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md)
and [retrieve money transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md) return it.

**November 17, 2026**

With `query`, `GET /customers/v1` finds a phone number typed the way it is dialled inside the country of the customer's location, without
the country code, when the location has a business address. In a location in Ukraine, `050 123` finds `+380501234567`. A query that starts
with `+` is still matched only from the beginning of the international number.

**November 17, 2026**

With `query`, `GET /customers/v1` matches a person by their email or phone number only when the caller can see it, as the response shows
it. A member who hides their email from other members is still found by name, but no longer by the beginning of their email. A company is
matched by its email only for an administrator of its location or a manager of the company. A person who blocked the caller is left out of
the results.

**November 17, 2026**

The deprecated `booking.price.netAmount` of a money transaction that charged a booking together with its add-ons is the booking's own net
amount. [Retrieve a money transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md) and [retrieve money
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md) used to subtract the booking's tax from the whole charge, add-ons
included.

**November 17, 2026**

A campaign can go out by SMS. [Create a campaign](https://www.spacebring.com/docs/developer/api/campaigns/create-a-campaign.md) and [update a
campaign](https://www.spacebring.com/docs/developer/api/campaigns/update-a-campaign.md) accept `sms` as the `channel`, with the text in `sms.body`, and [retrieve
campaigns](https://www.spacebring.com/docs/developer/api/campaigns/retrieve-campaigns.md) and [get a campaign](https://www.spacebring.com/docs/developer/api/campaigns/get-a-campaign.md) return it and filter
by `sms` in `channel`. A text longer than one SMS, 160 characters or 70 with a character outside the GSM-7 alphabet such as an emoji, goes
out as several, each charged. As with email, `charge` holds what sending cost once it starts.

**November 17, 2026**

[Get posts](https://www.spacebring.com/docs/developer/api/feed/get-posts.md) and [get a post](https://www.spacebring.com/docs/developer/api/feed/get-a-post.md) return `views`, the number of members who
viewed the post in the Spacebring member app, and `viewed`, whether the current user has viewed it. Views are counted from this release,
so `views` is missing on posts nobody has viewed since.

**November 17, 2026**

The deprecated `price.netAmount` and `price.taxAmount` of a money transaction's `booking`, `creditPackage` and `ticket` are in the
transaction's own currency for a customer who pays in an alternative currency. [Retrieve a money
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md) and [retrieve money
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md) used to subtract the tax in the location's currency from the amount
in the customer's, and `netAmount` is now rounded to the currency's decimals.

**November 17, 2026**

A fixed-amount coupon applied to a customer who pays in an alternative currency is converted at the exchange rate and rounded to that
currency's decimals. [Retrieve a money transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md) and [retrieve money
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md) return the rounded `discounts[].coupon.amountOff` for transactions
created from now on, such as `9.21` instead of `9.211` for a 10 USD coupon at a rate of 0.9211 EUR.

**November 17, 2026**

Plans name the plans members can buy together with them `crossSells` instead of `addons`. Send `crossSells.plans` as a list of plan ids in
offer order on [create a plan](https://www.spacebring.com/docs/developer/api/plans/create-a-plan.md) or [update a plan](https://www.spacebring.com/docs/developer/api/plans/update-a-plan.md), and leave it
out of an update to keep the plans already offered. [Retrieve a plan](https://www.spacebring.com/docs/developer/api/plans/retrieve-a-plan.md) and [retrieve
plans](https://www.spacebring.com/docs/developer/api/plans/retrieve-plans.md) return `crossSells.plans`. `addons` is no longer accepted or returned.

**November 17, 2026**

Plan tiers name the plans members can buy together with them `crossSells` instead of `addons`. Send `crossSells.plans` as a list of plan
ids in offer order on [create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) or [patch a
resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md), and leave it out to keep the plans a tier already offers. [Get a
resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md) and [retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) return
`crossSells.plans` on each tier. `addons` is no longer accepted or returned.

**November 16, 2026**

A visit has an end and can last several days. [Create a visit](https://www.spacebring.com/docs/developer/api/visitors/create-a-visit.md) takes an optional `endDate`, after
`date` and within 31 days, and the visitor checks in with the same code until then. Without it, the visit ends at the end of its day in
the location timezone. [Update a visit](https://www.spacebring.com/docs/developer/api/visitors/update-a-visit.md) takes `endDate` too, and leaving it out or sending the
current one moves the end by as many days as `date` moves. [Retrieve a visit](https://www.spacebring.com/docs/developer/api/visitors/retrieve-a-visit.md) and [retrieve
visits](https://www.spacebring.com/docs/developer/api/visitors/retrieve-visits.md) return `endDate` for every visit. Retrieve visits filters by `endDate` with `gt`, `gte`,
`lt`, and `lte`, and by `date` with `gt` and `lt` as well as `gte` and `lte`. `date[lt]` with `endDate[gt]` lists the visits that overlap
a period.

**November 16, 2026**

An event's start date can't change once an attendee has checked in. [Update an event](https://www.spacebring.com/docs/developer/api/events/update-an-event.md) and
[partially update an event](https://www.spacebring.com/docs/developer/api/events/partially-update-an-event.md) return `409` with the `eventAttendeeCheckedIn` code when the
request moves the start date of such an event. Other fields, including the end date, still change.

**November 16, 2026**

Every resource type can take day passes, not only hot desks. Set `dayPassesEnabled` to `true` on [create a
resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) or [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) for a room, an
office or any other type, and [create a booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) accepts a `dayPasses` payment method for it. A
booking takes one day pass per seat for each day it spans, and a room booking counts as one seat.

**November 16, 2026**

Subscriptions can issue upcoming invoices on a fixed day of the month. Set `advanceInvoicing.type` to `dayOfMonth` with a `dayOfMonth`
from 1 to 28 on [create a subscription](https://www.spacebring.com/docs/developer/api/subscriptions/create-a-subscription.md) or [update a
subscription](https://www.spacebring.com/docs/developer/api/subscriptions/update-a-subscription.md), and the invoice for the next period is issued on that day of the month
before it starts, with the bookings that started before that day. [Retrieve a
subscription](https://www.spacebring.com/docs/developer/api/subscriptions/retrieve-a-subscription.md) and [retrieve
subscriptions](https://www.spacebring.com/docs/developer/api/subscriptions/retrieve-subscriptions.md) return `advanceInvoicing.dayOfMonth` when invoices are issued on a
fixed day, and `advanceInvoicing.days` otherwise. A subscription with a daily or weekly period ignores the day of the month and issues
invoices when the period starts.

**November 16, 2026**

A delivery takes several photos. Pass every key from [create a media upload](https://www.spacebring.com/docs/developer/api/deliveries/create-a-media-upload.md) in `media`
on [create a delivery](https://www.spacebring.com/docs/developer/api/deliveries/create-a-delivery.md) or [update a delivery](https://www.spacebring.com/docs/developer/api/deliveries/update-a-delivery.md),
in display order. On update, `media` replaces the photos, so include the keys of the ones to keep. [Get a
delivery](https://www.spacebring.com/docs/developer/api/deliveries/get-a-delivery.md) and [retrieve deliveries](https://www.spacebring.com/docs/developer/api/deliveries/retrieve-deliveries.md) return them
in the same order.

**November 13, 2026**

Deliveries are in the API. [Retrieve deliveries](https://www.spacebring.com/docs/developer/api/deliveries/retrieve-deliveries.md) of the network, a location, a customer, or
a user, [get a delivery](https://www.spacebring.com/docs/developer/api/deliveries/get-a-delivery.md), [create](https://www.spacebring.com/docs/developer/api/deliveries/create-a-delivery.md) one with a photo
from [create a media upload](https://www.spacebring.com/docs/developer/api/deliveries/create-a-media-upload.md), [update](https://www.spacebring.com/docs/developer/api/deliveries/update-a-delivery.md) it,
for example to mark it `pickedUp`, and [delete](https://www.spacebring.com/docs/developer/api/deliveries/delete-a-delivery.md) it. OAuth apps request the new
`deliveries.readonly` or `deliveries` scope, and with bearer token authentication the user needs the `deliveries` area in
`locationPermissionLevels` of [retrieve registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md) for the delivery's location.

**November 13, 2026**

Plans and resource tiers can require a contract at sign-up. Set `selfSignup.contract.templateRef` on [create a
plan](https://www.spacebring.com/docs/developer/api/plans/create-a-plan.md), [update a plan](https://www.spacebring.com/docs/developer/api/plans/update-a-plan.md), [create a
resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) or [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md), and a customer who
signs up immediately signs a contract from that template. The subscription starts once the contract is signed, and its first invoice is
issued then. The template must belong to the location of the plan or resource, the location must have eSignature turned on, and the
sign-up type must be `immediate`. `selfSignup` is replaced as a whole, so sending it without `contract` stops requiring one, as does
switching the sign-up type to `request`. [Retrieve a plan](https://www.spacebring.com/docs/developer/api/plans/retrieve-a-plan.md), [retrieve
plans](https://www.spacebring.com/docs/developer/api/plans/retrieve-plans.md) and [get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md) return `selfSignup.contract`
when a contract is required.

**November 13, 2026**

[Create a booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) with [Basic
authentication](https://www.spacebring.com/docs/developer/api/authentication.md#basic-authentication) accepts a `paymentMethod`, such as `external` for a payment collected
outside Spacebring, and pays for the booking the way an administrator would, also on a resource only administrators can book. Pass the
`membershipRefOwner` of the customer the booking is paid for. Before, Basic authentication could create only free bookings and got `403`
for any payment method.

**November 13, 2026**

The new `booking.upcoming` webhook is sent an hour before a booking starts, and an hour before each date of a repeating booking, so an
integration can act on every date a resource is booked, such as sending a door code. A repeating booking is a single booking, so
`booking.created` is sent for it once, with its first date. `booking.upcoming` carries the date's own `startDate` and `endDate`, and an
`id` of `{bookingId}_{isoDate}` for each date after the first, as [retrieve bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md) returns
them with `singleBookings`. Only confirmed bookings are sent, and a booking made, paid or rescheduled less than an hour before it starts
is left out, as `booking.created`, `booking.paid` or `booking.updated` already carries it. See
[Webhooks](https://www.spacebring.com/docs/developer/webhooks.md#get-each-date-of-a-repeating-booking).

**November 12, 2026**

`refundPolicy` on resources has `partialRefunds`, and `refundPolicy.public` has its own for nonmembers: up to five shares refunded when a
booking is canceled after its full refund threshold has passed, each a `percent` from 1 to 99 and a `value` threshold. A cancellation gets
back the `percent` of the longest threshold it still meets, of what the booking was paid with by card, externally, in credits, in day
passes or on an invoice not yet issued, and nothing once every threshold has passed. Day passes are refunded whole, rounded down. Each
threshold must be shorter than `value`, unless `value` is `noRefund`, and a shorter threshold must refund a smaller share. [Create a
resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) accept them; a
patch that leaves `partialRefunds` out keeps the current ones, and an empty list removes them. [Get a
resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md), [retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) and resource webhook
payloads return them, as an empty list when there are none. A booking keeps the partial refunds of the policy it was made with. See
[Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**November 11, 2026**

[Retrieve subscriptions](https://www.spacebring.com/docs/developer/api/subscriptions/retrieve-subscriptions.md) accepts `requested` in `status`, and [retrieve a
subscription](https://www.spacebring.com/docs/developer/api/subscriptions/retrieve-a-subscription.md) can return it. A requested subscription is one a person asked for on a
plan that needs an administrator's approval: it bills nothing, grants no credits or day passes and holds no resource until it is approved.
A request ends as `declined` when an administrator declines it or nobody answers it within 30 days, and as `withdrawn` when the person
takes it back; `status` accepts both too. An approved request is returned as `approved`, and the subscription the approval created is a
separate one. Without `status`, the list still returns `active`, `scheduled` and `incomplete` subscriptions only.

**November 10, 2026**

Location payloads no longer carry `guidance` and `ticketReplies` in `supportLemAI`. Agents reply to support tickets, each with its own
instructions, so these fields had no effect. `supportLemAI.autoAssignTickets` stays. See [Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**November 10, 2026**

[Retrieve resource assignments](https://www.spacebring.com/docs/developer/api/resources/retrieve-resource-assignments.md) for a location with a bearer token needs resources
access to the location instead of analytics access, the same access [get a resource
assignment](https://www.spacebring.com/docs/developer/api/resources/get-a-resource-assignment.md) needs.

**November 10, 2026**

A booking made with [basic authentication](https://www.spacebring.com/docs/developer/api/authentication.md#basic-authentication) through [create a
booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) notifies its owner and attendees when `sendUpdates` is `all`, the default, as a
booking made with a bearer token already did, and attendees added with basic authentication through [update a
booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md) are notified too. Set `sendUpdates` to `none` to skip these notifications. The
`confirmationEmail` options of [create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [get a
resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md) now pick the email by the role of the customer the booking is for, not of the person
who made it.

**November 10, 2026**

`companyRequester` in [retrieve a ticket](https://www.spacebring.com/docs/developer/api/support/retrieve-a-ticket.md) and [retrieve
tickets](https://www.spacebring.com/docs/developer/api/support/retrieve-tickets.md) carries the company's `logo` with its `key` and `url` when an administrator uploaded
one, and `publicLogoUrl` derived from the company's website.

**November 9, 2026**

A support ticket can be requested for the requester's company, so every member of the company can read it and comment on it.
`userRequester` stays the member who opened it. [Create a ticket](https://www.spacebring.com/docs/developer/api/support/create-a-ticket.md) accepts an optional
`companyRefRequester`, the ID of the requester's company, and fails with `400` when the requester is not a member of that company or the
ticket's type is `discriminationAndHarassment`. [Retrieve a ticket](https://www.spacebring.com/docs/developer/api/support/retrieve-a-ticket.md) and [retrieve
tickets](https://www.spacebring.com/docs/developer/api/support/retrieve-tickets.md) return `companyRefRequester` and `companyRequester` with the company's `id` and `title`,
and a member sees the tickets requested for their company next to their own. Retrieve tickets also filters by `companyRefRequester`, one
or more comma-separated company IDs, for support admins of the company's location and for members of the company. Together with
`membershipRefRequester`, it lists the tickets that match either one. Members of the company can [create a ticket
comment](https://www.spacebring.com/docs/developer/api/support/create-a-ticket-comment.md) on the ticket. The `support.ticket.created` webhook carries `companyRefRequester`
too. A ticket without `companyRefRequester` stays visible to its requester only. See [Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**November 9, 2026**

[Campaigns](https://www.spacebring.com/docs/engagement/campaigns) are in the API. [Retrieve campaigns](https://www.spacebring.com/docs/developer/api/campaigns/retrieve-campaigns.md) and [get a
campaign](https://www.spacebring.com/docs/developer/api/campaigns/get-a-campaign.md) with its delivery statistics, and [create](https://www.spacebring.com/docs/developer/api/campaigns/create-a-campaign.md),
[update](https://www.spacebring.com/docs/developer/api/campaigns/update-a-campaign.md), and [delete](https://www.spacebring.com/docs/developer/api/campaigns/delete-a-campaign.md) drafts. The API never sends
a campaign: an administrator sends a draft from the admin web portal. OAuth apps request the new `campaigns.readonly` or `campaigns`
scope, and with bearer token authentication the user needs the `campaigns` area in `locationPermissionLevels` of [retrieve
registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md) for the campaign's locations.

**November 4, 2026**

Administrators have a `deliveries` area in `locationPermissionLevels` and `locationPermissions` of [retrieve
registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md). Every existing administrator starts out with `write`, and owners and
super administrators always have it. `read` lets an administrator see the deliveries kept at their locations, and `write` also lets them
add, change, and delete them.

**November 5, 2026**

[Retrieve bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md) accepts `requested` and `declined` in `status`. A booking request is what
a person creates when a resource's booking permission doesn't let them book it directly, and it holds no time until an administrator
approves it. `requested` lists the requests waiting for an answer, and `declined` the ones an administrator declined or nobody answered
before they started. Without `status`, the list still returns `tentative` and `confirmed` bookings only.

**November 3, 2026**

Administrators have a `visitors` area in `locationPermissionLevels` and `locationPermissions` of [retrieve
registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md). Every existing administrator starts out with `write`, and owners and
super administrators always have it. With `read`, an administrator can still [retrieve visits](https://www.spacebring.com/docs/developer/api/visitors/retrieve-visits.md),
[get requests](https://www.spacebring.com/docs/developer/api/visitors/get-requests.md), and [get contacts](https://www.spacebring.com/docs/developer/api/visitors/get-contacts.md), but [create a
request](https://www.spacebring.com/docs/developer/api/visitors/create-a-request.md), [create a contact](https://www.spacebring.com/docs/developer/api/visitors/create-a-contact.md), [check in a
visit](https://www.spacebring.com/docs/developer/api/visitors/check-in-a-visit.md), and [check out a visit](https://www.spacebring.com/docs/developer/api/visitors/check-out-a-visit.md) fail with `403`, and
[create a visit](https://www.spacebring.com/docs/developer/api/visitors/create-a-visit.md) and [update a visit](https://www.spacebring.com/docs/developer/api/visitors/update-a-visit.md) treat them like any
other member. With `none`, getting a single visit, request, or contact fails with `403` too, and the lists leave out the locations where
they hold it.

**November 3, 2026**

Administrators have a `checkIns` area in `locationPermissionLevels` and `locationPermissions` of [retrieve
registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md). Every existing administrator starts out with `write`, and owners and
super administrators always have it. With `read`, an administrator can still [get a check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md) and
[retrieve check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md), but [check in](https://www.spacebring.com/docs/developer/api/check-ins/check-in.md), [check
out](https://www.spacebring.com/docs/developer/api/check-ins/check-out.md), and [update a check-in](https://www.spacebring.com/docs/developer/api/check-ins/update-a-check-in.md) fail with `403`. With
`none`, getting a check-in fails with `403` too, and retrieving check-ins leaves out the locations where they hold it.

**November 3, 2026**

An administrator in [retrieve registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md) has `locationPermissionLevels` next to
`locationPermissions`: the access level they hold in each area of the locations they manage. `none` hides the area, `read` shows it
without changes, and `write` manages it. Analytics is only `none` or `read`, and settings only `none` or `write`. A permission in
`locationPermissions` is `true` only when its area holds the highest level, so an administrator with `none` and one with `read` both show
`false` there.

**October 30, 2026**

[Get a check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md) and [list check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md) return the new
`accessControl` value in `checkInMethod` for a check-in opened when a member unlocked a door through an access control integration.

**November 2, 2026**

A product and a benefit can have no category. [Create a product](https://www.spacebring.com/docs/developer/api/shop/create-a-product.md), [update a
product](https://www.spacebring.com/docs/developer/api/shop/update-a-product.md), [create a benefit](https://www.spacebring.com/docs/developer/api/benefits/create-a-benefit.md), and [update a
benefit](https://www.spacebring.com/docs/developer/api/benefits/update-a-benefit.md) accept `categoryRef` left out or `null`. [Partially update a
product](https://www.spacebring.com/docs/developer/api/shop/partially-update-a-product.md) and [partially update a
benefit](https://www.spacebring.com/docs/developer/api/benefits/partially-update-a-benefit.md) take a product or a benefit out of its category with `categoryRef: null`. A
product or a benefit without a category returns `categoryRef: null`. The `categoryRef` filter of [retrieve
orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md) and [retrieve applications](https://www.spacebring.com/docs/developer/api/benefits/retrieve-applications.md) accepts `none`
next to category IDs, for orders of products and applications for benefits that had no category.

**November 2, 2026**

The `receiptPdfUrl` of a money transaction now expires. A link stops working 190 days after it was issued, whether or not the transaction
is fetched again, and opening it after that fails with `400` and the code `receiptLinkExpired`. A link issued before this change got an
expiration date somewhere in the 180 days after it, so it keeps working for at least 10 more days. [Retrieve a money
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md) and [retrieve money
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md) return a new link once the current one is 180 days old, so fetch
the transaction again for the current link rather than storing it.

**November 2, 2026**

The `locationPermissions` of an administrator in [retrieve registrations](https://www.spacebring.com/docs/developer/api/registrations/retrieve-registrations.md) has a
`campaigns` permission: whether the administrator can manage campaigns in the locations they manage. It starts out with the value of
`feed`, and owners and super administrators always have it.

**October 30, 2026**

A resource can have a separate booking window for nonmembers in `bookingWindow.public`, with its own `enabled`, `bookAhead`, and
`minNotice`. While `bookingWindow.public.enabled` is `true`, a booking of a nonmember follows it instead of the rest of `bookingWindow`,
even when `bookingWindow.enabled` is `false`, and both values are required. Members keep following the rest of `bookingWindow`. [Create a
resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) accept it, and
[get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md) and [retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) return it.
[Create a booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md), [update a booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md), and [check
resource availability](https://www.spacebring.com/docs/developer/api/resources/check-resource-availability.md) apply it. [Retrieve
bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md) filters bookings by when they were created with `createDate[gt]`, `createDate[gte]`,
`createDate[lt]` and `createDate[lte]`, in any `order` and together with the start and end date filters. With `singleBookings`, each
occurrence of a repeating booking matches by the date the repeating booking was created. [Create a
booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) keeps the `attendees` of a booking an API key or an administrator makes for a
nonmember owner. They were left out before, as they still are when a nonmember books for themselves.

**October 29, 2026**

A visit's check-in in [list check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md) and [get a
check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md) returns the host's email in `visit.userHost.email`, and the host's company in
`visit.companyHost` with its `id` and `title`. `visit.companyHost` is absent when the host was not a member of a company when the visit
was created.

**October 22, 2026**

[Check in](https://www.spacebring.com/docs/developer/api/check-ins/check-in.md) with a `customerRef` accepts a past `checkInDate` to record an arrival nobody checked the
member in for. The member stays checked in from that date until they check out. Send a past `checkOutDate` as well to create the check-in
as checked out at those dates, even while the member is checked in right now, without the `checkInCheckedIn` or `checkInCheckedOut`
webhooks. [Get a check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md) and [list check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md)
return the new `backdated` value in `checkInMethod` and `checkOutMethod` for a past check-in an administrator added in the admin app.

**October 28, 2026**

[Retrieve invoices](https://www.spacebring.com/docs/developer/api/billing/retrieve-invoices.md) without `customerRef` or `locationRef`, [list invoice
items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md) without `customerRef`, `invoiceRef` or `locationRef`, and [retrieve credit
notes](https://www.spacebring.com/docs/developer/api/billing/retrieve-credit-notes.md) without `invoiceRef` or `locationRef` return the records of every location in the
network, with the same filters and pagination. Search by `q` works across the network too. An administrator limited to some locations
still has to pass one of the references.

**October 28, 2026**

[Create an alternative currency](https://www.spacebring.com/docs/developer/api/alternative-currencies/create-an-alternative-currency.md) and [update an alternative
currency](https://www.spacebring.com/docs/developer/api/alternative-currencies/update-an-alternative-currency.md) accept `null` again for the one of `exchangeRate` and
`provider` that is not used, and treat it as absent. Since October 20, a request with `"provider": null` or `"exchangeRate": null` was
rejected with "The provider is not supported." or "The exchange rate must be a positive number."

**October 27, 2026**

An external payment can record how the money was collected. [Pay an invoice](https://www.spacebring.com/docs/developer/api/billing/pay-an-invoice.md) and [create a money
transaction](https://www.spacebring.com/docs/developer/api/transactions/create-a-money-transaction.md) take an optional `paidBy` inside `payment.method.external`:
`bankTransfer`, `card`, `cash`, `check`, or `paymentLink`. The invoice payments in [retrieve an
invoice](https://www.spacebring.com/docs/developer/api/billing/retrieve-an-invoice.md) and the transaction in [retrieve a money
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md) return it in `payment.method.external.paidBy`, and the invoice PDF
names it in place of External. Absent when it was not recorded.

**October 26, 2026**

A check-in in [list check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md), [get a check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md),
and everywhere else check-ins are returned has a `checkInMethod` and a `checkOutMethod`: how the customer was checked in and out. The
values are `reception` for a code entered on the Reception app, `manual` for an administrator, `agent` for the AI agent, and `api` for an
API key or OAuth app. A check-out can also be `automatic`. The `checkInCheckedIn` and `checkInCheckedOut` webhooks carry them as
`check_in_method` and `check_out_method`. Check-ins made before methods were recorded have neither.

**October 26, 2026**

A contract with the `subscription` action carries the new `subscriptionRef` once it is issued, the ID of the subscription it created. [Get
a contract](https://www.spacebring.com/docs/developer/api/contracts/get-a-contract.md), [retrieve contracts](https://www.spacebring.com/docs/developer/api/contracts/retrieve-contracts.md), and [issue a
contract](https://www.spacebring.com/docs/developer/api/contracts/issue-a-contract.md) return it, and [retrieve a
subscription](https://www.spacebring.com/docs/developer/api/subscriptions/retrieve-a-subscription.md) already links back through `contract.id`.

**October 26, 2026**

[Update a check-in](https://www.spacebring.com/docs/developer/api/check-ins/update-a-check-in.md), `PATCH /check_ins/v1/{checkInId}`, changes the `checkInDate` or
`checkOutDate` of a check-in, both in the past. `checkOutDate` is accepted only for a check-in that is checked out. The booking, event
ticket, or visit behind the check-in returns the new dates too. No webhooks are sent.

**October 26, 2026**

A check-in in [list check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md), [get a check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md),
and everywhere else check-ins are returned has a `checkInMethod` and a `checkOutMethod`: how the customer was checked in and out. The
values are `reception` for a code entered on the Reception app, `manual` for an administrator, `agent` for the AI agent, and `api` for an
API key or OAuth app. A check-out can also be `automatic`. The `checkInCheckedIn` and `checkInCheckedOut` webhooks carry them as
`check_in_method` and `check_out_method`. Check-ins made before methods were recorded have neither.

**October 26, 2026**

Coupons can have a name. [Create a coupon](https://www.spacebring.com/docs/developer/api/discounts/create-a-coupon.md) and [update a
coupon](https://www.spacebring.com/docs/developer/api/discounts/update-a-coupon.md) accept an optional `title`, and [retrieve
coupons](https://www.spacebring.com/docs/developer/api/discounts/retrieve-coupons.md) and [get a coupon](https://www.spacebring.com/docs/developer/api/discounts/get-a-coupon.md) return it. A coupon without
a name has no `title`. Update a coupon now takes `title` and `limitedItems` each on its own, so any coupon can be renamed, and an empty
`title` removes the name. Sending `limitedItems` still needs a coupon created with limited items enabled. Plans can have a cover image.
[Create a media upload](https://www.spacebring.com/docs/developer/api/plans/create-a-media-upload.md), send the file, then pass its key as `media[0].key` to [create a
plan](https://www.spacebring.com/docs/developer/api/plans/create-a-plan.md) or [update a plan](https://www.spacebring.com/docs/developer/api/plans/update-a-plan.md). An empty `media` on update removes the
image. Every plan response, including [retrieve plans](https://www.spacebring.com/docs/developer/api/plans/retrieve-plans.md) and [retrieve a
plan](https://www.spacebring.com/docs/developer/api/plans/retrieve-a-plan.md), carries `media` with the image's `key` and public `url`. See [File
uploads](https://www.spacebring.com/docs/developer/api/file-uploads.md).

**October 23, 2026**

`bufferTime` now applies to desks as well as rooms. [Create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a
resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) store it for a `hotDesk`, `dedicatedDesk`, or `station`, and bookings of that desk
keep it free before and after them. Until now a desk dropped the `bufferTime` sent to it. Other resource types still ignore it. In
[retrieve a ticket](https://www.spacebring.com/docs/developer/api/support/retrieve-a-ticket.md), a reply an agent posted shows that agent: `lemAI` carries the new
`agentRef` with the agent's ID, and its `name` and `photoUrl` are the agent's. `photoUrl` is `null` when the agent has no photo. Replies
posted before agents keep the name Agent and the agent icon, without `agentRef`.

**October 23, 2026**

Location payloads carry which billing details customers see at checkout in new fields, `companyBillingDetailsFields` for companies and
`userBillingDetailsFields` for individual users, each with `legalName`, `address`, and `taxId` set to `required`, `optional`, or `hidden`.
The `customerBillingDetailsRequired` and `userBillingDetailsRequired` fields are deprecated and will be removed. Until then they are
`true` only while every field of that customer type is `required`. See [Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**October 21, 2026**

[Create a shop category](https://www.spacebring.com/docs/developer/api/shop/create-a-category.md) and [create a benefit category](https://www.spacebring.com/docs/developer/api/benefits/create-a-category.md)
need the Settings permission in the location, as reordering categories already did, instead of the Shop or Benefits permission. API keys
are not affected.

**October 20, 2026**

The request body of [create an alternative currency](https://www.spacebring.com/docs/developer/api/alternative-currencies/create-an-alternative-currency.md) and [update an
alternative currency](https://www.spacebring.com/docs/developer/api/alternative-currencies/update-an-alternative-currency.md) is now documented as one object with optional
`exchangeRate` and `provider`, of which exactly one is required. The same requests are accepted as before, and an unsupported `provider`
or a rate that is not positive is now reported on `altCurrency.provider` or `altCurrency.exchangeRate` with its own message instead of
"Either provider or exchange rate is required."

**October 20, 2026**

An invoice item in [list invoice items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md), [retrieve an invoice
item](https://www.spacebring.com/docs/developer/api/billing/retrieve-an-invoice-item.md) and everywhere else items are returned has a `status`: the status of the invoice it
is on, as the `status` filter of list invoice items reads it. An item on no invoice has none.

**October 20, 2026**

[Get posts](https://www.spacebring.com/docs/developer/api/feed/get-posts.md) no longer requires `locationRef`. Leave it out to list the posts of every location in the
network where the feed is on, pinned posts first and then newest first. Each location's feed visibility still applies: API keys see every
location's posts, and administrators and members see the posts of the locations whose feed they may open.

**October 20, 2026**

The reference now documents [void a credit note](https://www.spacebring.com/docs/developer/api/billing/void-a-credit-note.md), `PUT /billing/credit_notes/v1/{id}/void`,
which answers with the voided credit note in the shape [retrieve a credit note](https://www.spacebring.com/docs/developer/api/billing/retrieve-a-credit-note.md) returns.

**October 20, 2026**

[Get a resource assignment](https://www.spacebring.com/docs/developer/api/resources/get-a-resource-assignment.md) reads one assignment by id, in the shape [retrieve
resource assignments](https://www.spacebring.com/docs/developer/api/resources/retrieve-resource-assignments.md) lists them, so you can read an assignment back after
[updating it](https://www.spacebring.com/docs/developer/api/resources/update-a-resource-assignment.md). It needs resources access to the assignment's location. The
reference now also documents [delete a resource assignment](https://www.spacebring.com/docs/developer/api/resources/delete-a-resource-assignment.md) and [delete a
resource](https://www.spacebring.com/docs/developer/api/resources/delete-a-resource.md), which both answer `204 No Content`.

**October 19, 2026**

The `user` of a check-in in [retrieve check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md), [get a
check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md), [check in](https://www.spacebring.com/docs/developer/api/check-ins/check-in.md) and [check
out](https://www.spacebring.com/docs/developer/api/check-ins/check-out.md) has a `deleteDate` when the user account was deleted.

**October 19, 2026**

[Retrieve events](https://www.spacebring.com/docs/developer/api/events/retrieve-events.md) no longer requires `locationRef`. Leave it out to list the events of every
location in the network, with the same date filters and `order` as before; each event keeps the visibility it has in its own location.
[Retrieve tickets](https://www.spacebring.com/docs/developer/api/events/retrieve-tickets.md) no longer requires `locationRef`, `eventRef`, `customerRef` or `userRef`. Leave
all four out to list the tickets of every location, newest first. API keys see every ticket; administrators see the tickets of the
locations where they have events access and their own tickets elsewhere, and members only their own tickets.

**October 19, 2026**

[Retrieve visits](https://www.spacebring.com/docs/developer/api/visitors/retrieve-visits.md), [get contacts](https://www.spacebring.com/docs/developer/api/visitors/get-contacts.md) and [get
requests](https://www.spacebring.com/docs/developer/api/visitors/get-requests.md) no longer require `locationRef`. Leave it out to list the visits, contacts or pending
requests of every location in the network; visits then come newest visit date first. API keys see every location's records; administrators
see those of the locations they manage, plus the visits and requests they host elsewhere, and members only their own visits and requests.
Listing contacts without `locationRef` needs an administrator.

**October 19, 2026**

[Retrieve check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md) no longer requires `locationRef`. Leave it out to list the check-ins of
every location in the network. API keys see every check-in, and administrators see the check-ins of the locations they manage.

**October 19, 2026**

[Partially update an event](https://www.spacebring.com/docs/developer/api/events/partially-update-an-event.md), [partially update a
post](https://www.spacebring.com/docs/developer/api/feed/partially-update-a-post.md) and [partially update a product](https://www.spacebring.com/docs/developer/api/shop/partially-update-a-product.md) change
only the fields a request sets and keep the others, so renaming an event, a post or a product no longer means sending the whole record.
They answer `204 No Content`; read the result with [retrieve an event](https://www.spacebring.com/docs/developer/api/events/retrieve-an-event.md), [get a
post](https://www.spacebring.com/docs/developer/api/feed/get-a-post.md) or [get a product](https://www.spacebring.com/docs/developer/api/shop/get-a-product.md). [Update an
event](https://www.spacebring.com/docs/developer/api/events/update-an-event.md), [update a post](https://www.spacebring.com/docs/developer/api/feed/update-a-post.md) and [update a
product](https://www.spacebring.com/docs/developer/api/shop/update-a-product.md) still replace every field.

**October 19, 2026**

[Partially update a benefit](https://www.spacebring.com/docs/developer/api/benefits/partially-update-a-benefit.md) changes only the fields a request sets and keeps the
others, so renaming a benefit no longer means sending the whole benefit. It answers `204 No Content`; read the result with [retrieve a
benefit](https://www.spacebring.com/docs/developer/api/benefits/retrieve-a-benefit.md). [Update a benefit](https://www.spacebring.com/docs/developer/api/benefits/update-a-benefit.md) still replaces every
field.

**October 18, 2026**

[Retrieve products](https://www.spacebring.com/docs/developer/api/shop/retrieve-products.md) no longer requires `locationRef`, `categoryRef` or `id`. Leave them out to list
the products of every location in the network, newest first; each product's visibility still applies against its own location. [Retrieve
categories](https://www.spacebring.com/docs/developer/api/shop/retrieve-categories.md) no longer requires `locationRef`; leave it out to list the categories of every
location, grouped by location. [Retrieve orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md) no longer requires `locationRef`, `customerRef` or
`userRef`. Leave all three out to list the orders of every location, newest first, with the `status`, `categoryRef`, `productRef` and
`createDate` filters. API keys see every order, and administrators their own orders and those of the locations where they have shop
access; a caller who is not an administrator in the network gets 403.

**October 16, 2026**

Resources have a `refundPolicy` with the same shape as `duration` and `schedule`: `value` is the rescheduling policy, and `public` holds a
separate one for nonmembers, with `enabled` and `value`. [Create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a
resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) accept it, and [get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md), [retrieve
resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) and resource webhook payloads return it. When `public.enabled` is `true`, a
booking made for a customer who is not a member of the location follows `public.value`. A booking keeps the policy it was made with;
moving it to another resource takes that resource's policy for the customer. `refundThreshold` is deprecated: responses still return it
with the same value as `refundPolicy.value`, and a request that sends it without `refundPolicy` changes `refundPolicy.value` only. See
[Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**October 16, 2026**

With `query`, `GET /customers/v1` finds customers by the beginning of their phone number again. A query made only of digits, spaces, `+`,
`-`, `.` and brackets is compared by its digits, so `+380 67 12` finds `+380671234567`, and these matches come after email matches.

**October 16, 2026**

With `query`, `GET /customers/v1` matches customers by meaning, across a person's name, about text and company or a company's title and
website, and by the beginning of their email, instead of matching names, emails and phone numbers by spelling. Customers whose email
starts with the query come first. A query that contains `@` or is made only of digits is matched by email only, so it no longer finds a
customer by phone number.

**October 16, 2026**

[Create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) no longer lists an `id` field in its request body. Spacebring has always
given a new resource its own id and ignored the one sent, so requests that still send `id` keep working and get the same result.

**October 16, 2026**

[Retrieve a package](https://www.spacebring.com/docs/developer/api/packages/retrieve-a-package.md) returns one package by its id, with the same fields as [retrieve
packages](https://www.spacebring.com/docs/developer/api/packages/retrieve-packages.md). API keys read any package in the network; members read the packages of the locations
where they are a member, and administrators those of the locations where they have billing access.

**October 15, 2026**

[Create a company](https://www.spacebring.com/docs/developer/api/community/create-a-company.md) saves the `taxId` it is given; before, the company was created without a tax
ID.

**October 15, 2026**

[Retrieve tickets](https://www.spacebring.com/docs/developer/api/events/retrieve-tickets.md) applies `eventRef` together with `customerRef`, returning only that customer's
tickets for the event. Before, `eventRef` was ignored when `customerRef` was set.

**October 15, 2026**

[Update a plan](https://www.spacebring.com/docs/developer/api/plans/update-a-plan.md) changes only the fields the request sends. It used to reset `commitmentCycles`,
`credits`, `dayPasses` and `setupFee` to 0, `description` to empty and `exclusiveAccess` to no resources whenever the request left them
out, so a request that renamed a plan also cleared them.

**October 15, 2026**

With `query`, `GET /customers/v1` searches members and nonmembers when `membershipType` is left out, and returns at most 10 matches when
`limit` is left out, so a single search finds a former customer too. Pass `membershipType=member` to search current members only, or a
`limit` of up to 100. Without `query`, the defaults are unchanged: members only, 100 per page.

**October 15, 2026**

[Retrieve orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md) ignores spaces around each `status`, `categoryRef` and `productRef` value and names
the values it rejects: an unknown status reads `Invalid status: "shipped". Use one or more of canceled, completed, inProgress, new,
    pending, separated by commas.` (was `status should be new, inProgress, completed or canceled.`), and a `categoryRef` or `productRef` that
is not a UUID reads `Invalid categoryRef: "…". Use one or more UUIDs, separated by commas.` (was `categoryRefs should be uuid.` and
`productRef should be uuid.`). The reference now lists `pending`, which the `status` filter already accepted. [Retrieve
products](https://www.spacebring.com/docs/developer/api/shop/retrieve-products.md) ignores spaces around each `id` the same way, and an `id` that is not a UUID reads
`Invalid id: "…". Use one or more UUIDs, separated by commas.` (was `productIds should be a list of valid UUIDs.`).

**October 15, 2026**

[Retrieve subscriptions](https://www.spacebring.com/docs/developer/api/subscriptions/retrieve-subscriptions.md) no longer requires `locationRef` or `customerRef`. Leave
both out to list the subscriptions of every location in the network, grouped by location, with the `status`, `planRef` and `createDate`
filters; `order` still needs `locationRef`. API keys see the subscriptions of every location, and administrators those of the locations
where they have billing access.

**October 15, 2026**

The `status` filter of [retrieve invoices](https://www.spacebring.com/docs/developer/api/billing/retrieve-invoices.md), [list invoice
items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md) and [retrieve credit notes](https://www.spacebring.com/docs/developer/api/billing/retrieve-credit-notes.md), and the `type`
filter of list invoice items, ignore spaces around each comma-separated value, and a value they do not accept is reported as `Invalid
    status: "unpaid". Use one or more of draft, issued, paid, voided, separated by commas.` instead of `status should be draft, issued, paid or
    voided.`, and the same way for credit note statuses and item types. [Retrieve the upcoming
invoice](https://www.spacebring.com/docs/developer/api/billing/retrieve-the-upcoming-invoice.md), [list upcoming invoice
items](https://www.spacebring.com/docs/developer/api/billing/list-upcoming-invoice-items.md) and [retrieve a credit note](https://www.spacebring.com/docs/developer/api/billing/retrieve-a-credit-note.md)
report invalid parameters as a `validationError` that lists each rejected field in `issues`. The upcoming invoice reads `Subscription ref is
    required.` or `subscriptionRef should be a valid UUID.` (was `Subscription reference is not valid.`), a credit note id that is not a UUID
reads `creditNoteId should be a valid UUID.` (was `Credit note ref is not valid.`), and list upcoming invoice items keeps its messages. The
invoice, invoice item and credit note references now document `discounts[].promocode.expiration` as the `{ enabled, date }` object it has
always been, not a date.

**October 15, 2026**

`GET /customers/v1` takes an optional `query` that finds customers by a person's name, email or phone number, a company title, or the
company of a person. Matching is fuzzy and accent-insensitive, the `locationRef`, `type` and `membershipType` filters still apply, and the
response holds at most `limit` matches, best first, without a `nextPageToken`. An optional `userRef` lists the person customers of that
user, one per location they belong to, under the same filters; a `userRef` that is not a UUID reads `userRef should be a valid UUID.`. The
`type` and `membershipType` filters ignore spaces around each value, and a rejected value is now named with the accepted ones: `Invalid
    type: "person". Use one or more of user, company, separated by commas.` (was `type should be user or company.`), and the same for
`membershipType` (was `membershipType should be member or nonmember.`).

**October 15, 2026**

[Retrieve benefits](https://www.spacebring.com/docs/developer/api/benefits/retrieve-benefits.md) no longer requires `locationRef` or `categoryRef`. Leave both out to list
the benefits of every location in the network, newest first; each benefit's visibility still applies against its own location.
`categoryRef` on its own now only returns benefits of the caller's network. [Retrieve
categories](https://www.spacebring.com/docs/developer/api/benefits/retrieve-categories.md) no longer requires `locationRef`; leave it out to list the categories of every
location. [Retrieve applications](https://www.spacebring.com/docs/developer/api/benefits/retrieve-applications.md) no longer requires a filter: without `locationRef`,
`benefitRef`, `customerRef` or `userRef`, API keys see the applications of every location, administrators those of the locations where
they have benefits access and their own, and other users their own. Applications of a deleted location no longer appear in any list,
including the lists by benefit, customer or user.

**October 15, 2026**

[Retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) and [retrieve bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md) trim
spaces around each `type` and `status` value, and their error now names the rejected values and the accepted ones, for example `Invalid
    type: "castle". Use one or more of …, separated by commas.` (was `type is not valid.`, and `status is not valid.` for `status`). The
reference lists the accepted values from the same list the API checks. Bookings returned by [retrieve
bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md), [get a booking](https://www.spacebring.com/docs/developer/api/resources/get-a-booking.md), [create a
booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) and [update a booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md) always include
`isCheckInRequired`, as the reference documents: a free booking on a resource without auto-release now returns `false` instead of leaving
the field out.

**October 14, 2026**

[Retrieve visits](https://www.spacebring.com/docs/developer/api/visitors/retrieve-visits.md), [get contacts](https://www.spacebring.com/docs/developer/api/visitors/get-contacts.md) and [get
requests](https://www.spacebring.com/docs/developer/api/visitors/get-requests.md) report invalid parameters as a `validationError` that lists each rejected field in
`issues`, with the same messages as before. [Retrieve a visit](https://www.spacebring.com/docs/developer/api/visitors/retrieve-a-visit.md), [get a
contact](https://www.spacebring.com/docs/developer/api/visitors/get-a-contact.md) and [retrieve a request](https://www.spacebring.com/docs/developer/api/visitors/retrieve-a-request.md) report an id that is
not a UUID the same way. Two messages now name the actual problem: a `locationRef` that is not a UUID on retrieve visits reads `The
    locationRef should be a valid UUID.` (was `The locationRef is required.`), and a `visitId` that is not a UUID reads `visitId should be a
    valid UUID.` (was `visitId is required.`). The visit reference now documents that `location.address` is `null` for a location without an
address.

**October 14, 2026**

[Retrieve coupons](https://www.spacebring.com/docs/developer/api/discounts/retrieve-coupons.md), [get a coupon](https://www.spacebring.com/docs/developer/api/discounts/get-a-coupon.md), [retrieve
promocodes](https://www.spacebring.com/docs/developer/api/discounts/retrieve-promocodes.md), [get a promocode](https://www.spacebring.com/docs/developer/api/discounts/get-a-promocode.md), and [retrieve
redemptions](https://www.spacebring.com/docs/developer/api/discounts/retrieve-redemptions.md) reject an invalid parameter with a `validationError` whose `issues` name the
field, instead of an `invalidParams` error. The `type` filter of retrieve coupons takes the product types a coupon applies to, such as
`roomBookings,shopProducts`, as it always has; the reference now lists them, spaces around each value are ignored, and the error names the
values it rejects. Retrieve redemptions caps `limit` at 100. In redemptions, `limitedRedemption.usage` of the coupon and promocode is `0`
instead of missing when nothing was counted yet, `customer.user.photoUrl` is `null` for a member without a photo, and the reference marks
`customer.user.name` and `surname` optional, as a member who has not set them has neither.

**October 14, 2026**

[Retrieve events](https://www.spacebring.com/docs/developer/api/events/retrieve-events.md) documents the `createDate`, `startDate` and `endDate` filters it already
accepted, and reports invalid parameters as a `validationError` that lists each rejected field in `issues`, with the same messages as
before. [Retrieve an event](https://www.spacebring.com/docs/developer/api/events/retrieve-an-event.md) and [retrieve a ticket](https://www.spacebring.com/docs/developer/api/events/retrieve-a-ticket.md)
report an id that is not a UUID the same way. [Retrieve tickets](https://www.spacebring.com/docs/developer/api/events/retrieve-tickets.md) trims spaces around each `status`
value and names the rejected value and the accepted ones in its error. The event ticket reference no longer lists
`payment.method.paymentGateway.location` and `payment.method.external.location`, which tickets never returned.

**October 14, 2026**

[Retrieve tickets](https://www.spacebring.com/docs/developer/api/support/retrieve-tickets.md) no longer requires `locationRef`. Leave it out to list the tickets of every
location in the network, sorted by `order` as before. API keys see every ticket; administrators see the tickets of the locations where
they have support access and their own tickets elsewhere, and members only their own tickets.

**October 14, 2026**

PayTabs joins the payment gateways. [Create a money transaction](https://www.spacebring.com/docs/developer/api/transactions/create-a-money-transaction.md) charges a
customer's saved PayTabs card with `payment.method.paymentGateway.gateway` set to `paytabs`, and
[bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md), [orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md), [event
tickets](https://www.spacebring.com/docs/developer/api/events/retrieve-tickets.md), [invoice payments](https://www.spacebring.com/docs/developer/api/billing/pay-an-invoice.md), and money transactions paid
through PayTabs return `paytabs` as their payment gateway. The location in location webhooks includes `paytabsConnectionStatus`.

**October 14, 2026**

[Retrieve an alternative currency](https://www.spacebring.com/docs/developer/api/alternative-currencies/retrieve-an-alternative-currency.md) returns one alternative
currency by its id, with the same fields as [retrieve alternative
currencies](https://www.spacebring.com/docs/developer/api/alternative-currencies/retrieve-alternative-currencies.md). It takes the `invoices.readonly` or `invoices` scope.

**October 14, 2026**

[Revoking tokens](https://www.spacebring.com/docs/developer/api/authentication.md#revoking-access-token) now follows RFC 7009. Send `token` in an x-www-form-urlencoded body
with your `client_id` and `client_secret`, as you do when you get or refresh a token. A token in the query string is ignored, and the
`GET` variant of the endpoint is removed. You can revoke only tokens issued to your own client. Revoking a refresh token now also stops it
from issuing new access tokens.

**October 14, 2026**

[Create a resource assignment](https://www.spacebring.com/docs/developer/api/resources/create-a-resource-assignment.md) and [update a resource
assignment](https://www.spacebring.com/docs/developer/api/resources/update-a-resource-assignment.md) now end the assignment at 23:59 on the day of `endDate`, in the time
zone of the location, as assignments from subscriptions do. An assignment that ends on a day now overlaps another that starts that day.

**October 14, 2026**

[Create a ticket](https://www.spacebring.com/docs/developer/api/support/create-a-ticket.md) accepts Basic authentication, so an integration can create a support ticket for
a member without acting as a user. With Basic authentication, `userRefRequester` is required, and the ticket and its `ticketCreated`
activity have no creator.

**October 14, 2026**

[Retrieve packages](https://www.spacebring.com/docs/developer/api/packages/retrieve-packages.md) no longer requires `locationRef`. Leave it out to list the packages of
every location in the network, newest first. A member sees the packages of the locations where they are a member.

**October 14, 2026**

[Retrieve contracts](https://www.spacebring.com/docs/developer/api/contracts/retrieve-contracts.md) no longer requires `customerRef` or `locationRef`. Leave both out to
list the contracts of every location in the network; `status`, `createDate` and the `q` title search still apply. Administrators see the
contracts of the locations where they have billing access, and members their own contracts. [Retrieve
templates](https://www.spacebring.com/docs/developer/api/contracts/retrieve-templates.md) no longer requires `locationRef`; leave it out to list the templates of every
location in the network.

**October 14, 2026**

[Retrieve coupons](https://www.spacebring.com/docs/developer/api/discounts/retrieve-coupons.md) no longer requires `locationRef`. Leave it out to list the coupons of every
location in the network, or pass only `customerRef` to list the coupons of that customer's location. [Retrieve
promocodes](https://www.spacebring.com/docs/developer/api/discounts/retrieve-promocodes.md) lists the promocodes of every location when both `locationRef` and `couponRef`
are left out. API keys see the coupons and promocodes of every location, and administrators those of the locations where they have billing
access. [Retrieve guides](https://www.spacebring.com/docs/developer/api/guides/retrieve-guides.md) no longer requires `locationRef`. Leave it out to list the guides of
every location in the network, newest first. Each guide's visibility still applies, against the guide's own location.

**October 14, 2026**

[Retrieve plans](https://www.spacebring.com/docs/developer/api/plans/retrieve-plans.md) no longer requires `locationRef`. Leave it out to list the plans of every location
in the network. As with one location, API keys see every plan, administrators also see the plans without self sign-up in the locations
where they have billing access, and everyone else sees only plans with self sign-up enabled.

**October 14, 2026**

Events can have a `ticketsPerAttendee` limit on how many tickets one attendee can get. [Retrieve
events](https://www.spacebring.com/docs/developer/api/events/retrieve-events.md) and [retrieve an event](https://www.spacebring.com/docs/developer/api/events/retrieve-an-event.md) return it, and leave it
out when the event is unlimited. [Create an event](https://www.spacebring.com/docs/developer/api/events/create-an-event.md) and [update an
event](https://www.spacebring.com/docs/developer/api/events/update-an-event.md) accept it; omit it to make the event unlimited, including on an update. Purchasing more
tickets than the limit is rejected with the `eventTicketsPerAttendeeExceeded` error.

**October 12, 2026**

Locations no longer set a booking window for each resource type, so a resource whose `bookingWindow.enabled` is `false` has none: users
can book it up to its start and any time ahead. While `enabled` is `true`, its `minNotice` and `bookAhead` apply as before. [Create a
booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md), [update a booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md), and [check resource
availability](https://www.spacebring.com/docs/developer/api/resources/check-resource-availability.md) follow the resource's window, which [create a
resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md), [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md), [get a
resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md), and [retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) carry in
`bookingWindow`.

**October 12, 2026**

The `roomBookAhead`, `deskBookAhead`, `officeBookAhead`, `parkingBookAhead`, and `equipmentBookAhead` fields of location payloads, and the
`*BookingPeriod` fields already deprecated in their favor, are deprecated and will be removed. Bookings no longer follow them: each
resource has its own `bookingWindow`. See [Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**October 13, 2026**

[Retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) and [retrieve bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md) no
longer require `locationRef`. Leave it out to list the resources or bookings of every location in the network; the other filters, such as
`type`, `status`, and the date ranges, still apply. Retrieve bookings also accepts `userRefOwner` on its own, for the bookings a user made
in any location, and `customerRef` or `companyRefOwner` on their own, for the bookings in the customer's location. [Update a
booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md) can extend a booking paid with invoice, or add seats to it, after its invoice is
issued. The extra charge goes on a new pending invoice item and appears as its own entry in the booking's `payments`, with its
`method.invoice.invoiceItemRef`. Shortening such a booking or moving it to another resource still fails. When [delete a
booking](https://www.spacebring.com/docs/developer/api/resources/delete-a-booking.md) refunds a booking whose invoice is issued, it removes the pending invoice items of its
extensions.

**October 12, 2026**

[Retrieve tickets](https://www.spacebring.com/docs/developer/api/events/retrieve-tickets.md) and [retrieve a ticket](https://www.spacebring.com/docs/developer/api/events/retrieve-a-ticket.md) return
`checkOutDate`, the time the attendee last checked out. It is cleared when the attendee checks in again, so a ticket with a `checkInDate`
and no `checkOutDate` belongs to an attendee who is checked in.

**October 12, 2026**

[Update a money transaction](https://www.spacebring.com/docs/developer/api/transactions/update-a-money-transaction.md) accepts `internalNote`, a note about the payment that
only administrators see, such as how an external payment was collected. It can be changed on any money transaction, together with `status`
or on its own, and an empty string clears it. `status` is now optional, and a request must contain `internalNote` or `status`. The request
now needs the Billing permission in the transaction's location instead of Customers, including to approve or cancel a pending external
payment. [Retrieve a money transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md) and [retrieve money
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md) return `internalNote` to administrators.

**October 9, 2026**

The `customer` of a resource assignment includes the company `logo` and the user's `photoUrl` in [retrieve resource
assignments](https://www.spacebring.com/docs/developer/api/resources/retrieve-resource-assignments.md), [create a resource
assignment](https://www.spacebring.com/docs/developer/api/resources/create-a-resource-assignment.md), [update a resource
assignment](https://www.spacebring.com/docs/developer/api/resources/update-a-resource-assignment.md), [retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md), and
[get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md).

**October 9, 2026**

[Create a money transaction](https://www.spacebring.com/docs/developer/api/transactions/create-a-money-transaction.md) charges a customer's saved PayPal card with
`payment.method.paymentGateway.gateway` set to `paypal`.

**October 9, 2026**

[Create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) accept a
`bookingStepMinutes` of 60 for rooms, conference rooms, event spaces, meeting rooms, phone booths, and studios, next to 5, 10, 15, and 30.

**October 9, 2026**

[Create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) accept
a `bookingStepMinutes` of 60 for rooms, conference rooms, event spaces, meeting rooms, phone booths, and studios, next to 5, 10, 15, and
30\.
[Create a booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) invites people from outside the location. Each attendee is either an existing
user, `{ "user": { "id": "…" } }`, or a person by email, `{ "user": { "email": "…", "name": "…", "surname": "…" } }`. A person invited
by email is matched to the user with that email or added as a new user, and attends without a membership in the location. An `id` that
is not an existing user is rejected with the `attendeeNotValid` error, and an existing user who is not a member of the location is
now kept as an attendee instead of being left out.

**October 9, 2026**

[Update a subscription](https://www.spacebring.com/docs/developer/api/subscriptions/update-a-subscription.md) and [update a subscription
item](https://www.spacebring.com/docs/developer/api/subscriptions/update-a-subscription-item.md) ignore the deprecated `discounts` field of an item when the request carries
`grantedDiscounts`, so sending an item back as it was returned, with its `grantedDiscounts` edited, keeps exactly the coupons in that
list. Before, the `discounts` percentages the response derives from a granted coupon re-created that coupon when `grantedDiscounts` was
emptied in the same request. A request without `grantedDiscounts` still applies `discounts`.

**October 7, 2026**

A user whose profile the authorized user may not see is now left out of transactions instead of being returned with `null` fields, the
same as in bookings. The user object (`customer.user`, `userCreatedBy`, `userOwner`, a refund's or a booking's user) and every reference
to them (`userRefOwner`, `userRefCreator`, `customerRefCreatedBy`, `membershipRef`, `membershipRefCreator`) are omitted. Admins of the
location and requests authenticated with an API key still get every user.

**October 7, 2026**

Transactions retrieved with an OAuth2 access token respect the privacy settings of the users they embed. When the authorized user is not
an admin of the location, another user's `name`, `surname`, `photoUrl`, `about`, `email`, and `phoneNumber` are `null` unless that user
shares their profile, email, or phone number with them. Requests authenticated with an API key are unchanged. This applies to [retrieve
credit transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-credit-transactions.md), [retrieve a credit
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-credit-transaction.md), [retrieve day pass
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-day-pass-transactions.md), [retrieve a day pass
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-day-pass-transaction.md), [retrieve money
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-money-transactions.md), [retrieve a money
transaction](https://www.spacebring.com/docs/developer/api/transactions/retrieve-a-money-transaction.md), [retrieve scheduled credits
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-scheduled-credits-transactions.md), and [retrieve scheduled day pass
transactions](https://www.spacebring.com/docs/developer/api/transactions/retrieve-scheduled-day-pass-transactions.md).

**October 7, 2026**

[Retrieve visits](https://www.spacebring.com/docs/developer/api/visitors/retrieve-visits.md) filters by visitor with `userRefVisitor`, the id of the user who visits, as
returned in each visit's `userRefVisitor`.

**October 7, 2026**

A booking paid by invoice carries `payments[].method.invoice.invoiceRef`, the invoice its invoice item was added to. It is not set while
the item is pending. This applies to [get a booking](https://www.spacebring.com/docs/developer/api/resources/get-a-booking.md), [retrieve
bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md), [create a booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md), and [update a
booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md).

**October 6, 2026**

[List invoice items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md) accepts `invoiceRef` to list the items of one invoice, in place of
`customerRef` or `locationRef` or together with them. They page and sort like the rest of the list, and the other filters still apply.

**October 6, 2026**

[List invoice items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md) lists pending invoice items with `pending=true`, for one customer with
`customerRef` or for a whole location with `locationRef`. [List upcoming invoice
items](https://www.spacebring.com/docs/developer/api/billing/list-upcoming-invoice-items.md) is deprecated: use list invoice items with `pending=true` and `customerRef`
instead. It keeps working for existing integrations. Listing the items of one invoice (`GET /billing/invoices/v1/{invoiceId}/items`) is no
longer in the API reference and keeps working too. In list invoice items, `createDate[gte]` and `createDate[lte]` filter by when the item
was created, while `status`, `issueDate[gte]`, and `issueDate[lte]` filter by the invoice the item is on.

**October 6, 2026**

The OpenAPI spec lists the OAuth2 authorization, token, and refresh URLs on `https://oauth2.spacebring.com/api/oauth2/`, the same URLs the
[authentication](https://www.spacebring.com/docs/developer/api/authentication.md#oauth2) page documents. The `https://api.spacebring.com/oauth2/` URLs it listed before
reach the same endpoints and keep working, so existing integrations need no change.

**October 6, 2026**

Location `media` follows the order administrators arrange the photos and videos in, and the first one is the location's cover. Media added
since the last arrangement comes first, newest first, which is the order every location returned before. This applies to [get a
location](https://www.spacebring.com/docs/developer/api/locations/get-a-location.md), [retrieve all locations](https://www.spacebring.com/docs/developer/api/locations/retrieve-all-locations.md), and the
location in webhook payloads.

**October 6, 2026**

[Update a subscription item](https://www.spacebring.com/docs/developer/api/subscriptions/update-a-subscription-item.md) with `grantedDiscounts` now keeps exactly the
coupons in the list, and an empty list removes them all. Before, a coupon the item carried as a product-type percentage discount, the
deprecated `discounts` field, came back after the update.

**October 6, 2026**

A resource can charge different prices on some weekdays. `pricingRules` lists the rules, each with the `days` it covers and the `money`
and `credits` tiers that replace the regular ones for a booking starting on one of those days, in the location's time zone. Pass it when
you [create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) or [patch a resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md): the
list replaces the current rule, an empty list removes it, and a patch without it keeps it. The list holds at most one rule, a rule must
select at least one day, and a rule keeps only the prices the resource charges, so its `money` tiers are dropped while money is disabled
and its `credits` tiers while credits are disabled. [Get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md) returns the rules, and
[create a booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md) prices the booking with the rule covering its start day. Dynamic pricing
still applies on top of the day's tiers.

**October 6, 2026**

Invoice items carry `issueDate`, when their invoice was issued. It is returned once the item is on an issued invoice: [list invoice
items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md), [retrieve an invoice item](https://www.spacebring.com/docs/developer/api/billing/retrieve-an-invoice-item.md), [retrieve
an invoice](https://www.spacebring.com/docs/developer/api/billing/retrieve-an-invoice.md), and [issue an invoice](https://www.spacebring.com/docs/developer/api/billing/issue-an-invoice.md).

**October 5, 2026**

[List invoice items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md) accepts `pending`. With `true` it returns only pending items, the ones not
on an invoice and not part of a subscription, and with `false` only the rest.

**October 5, 2026**

A resource can have its own booking window. [Create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) and [patch a
resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md) accept `bookingWindow`, and [get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md)
and [retrieve resources](https://www.spacebring.com/docs/developer/api/resources/retrieve-resources.md) return it. While `bookingWindow.enabled` is `true`, `minNotice`, how
many minutes before it starts a booking has to be made, and `bookAhead`, how far ahead users can book (`oneDay`, `twoDays`, `oneWeek`,
`twoWeeks`, `oneMonth`, `threeMonths`, `sixMonths`, `oneYear`, or `unlimited`), replace the ones the location sets for the resource type,
and both are required. While it is `false`, the resource follows its location and keeps its own values. [Create a
booking](https://www.spacebring.com/docs/developer/api/resources/create-a-booking.md), [update a booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md), and [check resource
availability](https://www.spacebring.com/docs/developer/api/resources/check-resource-availability.md) apply the resource's window.

**October 5, 2026**

Location payloads carry how far ahead users can book in new fields, `roomBookAhead`, `deskBookAhead`, `officeBookAhead`,
`parkingBookAhead`, and `equipmentBookAhead`, with the values `oneDay`, `twoDays`, `oneWeek`, `twoWeeks`, `oneMonth`, `threeMonths`,
`sixMonths`, `oneYear`, and `unlimited`. The `roomBookingPeriod`, `deskBookingPeriod`, `officeBookingPeriod`, `parkingBookingPeriod`, and
`equipmentBookingPeriod` fields and their `BOOKING_PERIOD_*` values are deprecated and will be removed. Until then they keep the same
values. See [Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**October 2, 2026**

Invoice items carry the `customer` they are billed to, with the company name in `title` for a company and the member in `user`, the same
way invoices do. It is returned wherever an invoice item is: [list invoice items](https://www.spacebring.com/docs/developer/api/billing/list-invoice-items.md), [retrieve an
invoice item](https://www.spacebring.com/docs/developer/api/billing/retrieve-an-invoice-item.md), [create an invoice item](https://www.spacebring.com/docs/developer/api/billing/create-an-invoice-item.md),
[list upcoming invoice items](https://www.spacebring.com/docs/developer/api/billing/list-upcoming-invoice-items.md), [retrieve the upcoming
invoice](https://www.spacebring.com/docs/developer/api/billing/retrieve-the-upcoming-invoice.md), [retrieve an invoice](https://www.spacebring.com/docs/developer/api/billing/retrieve-an-invoice.md), and
[issue an invoice](https://www.spacebring.com/docs/developer/api/billing/issue-an-invoice.md).

**October 2, 2026**

A membership's `role` is read-only. Administrators are managed on the Administrators page, so [create a
membership](https://www.spacebring.com/docs/developer/api/community/create-a-membership.md) and [update a membership](https://www.spacebring.com/docs/developer/api/community/update-a-membership.md) no
longer take `role`, and `role` is no longer required on create. A `role` sent in the request is ignored and never changes the user's
administrator access. The `role` returned by [retrieve a membership](https://www.spacebring.com/docs/developer/api/community/retrieve-a-membership.md) and the other
membership endpoints still says whether the user administers the location, and removing a membership no longer removes that access.

**October 1, 2026**

[Update a booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md) can move a booking paid by card or externally to a pricier resource with
`resourceRef`. The difference is charged as a separate money transaction, the way an extension is: the booking stays `tentative` while the
charge is pending, and a failed charge returns it to its previous resource and interval. A move to a resource with a lower price is still
rejected with `bookingMovePriceMismatch`, and a move while an extra charge is pending is rejected with `bookingPaymentPending`.

**October 1, 2026**

Ticket comment and guide attachments can be uploaded through the API. Create an upload for a file of any type up to 50 MB with [ticket
comments](https://www.spacebring.com/docs/developer/api/support/create-a-ticket-media-upload.md) or [guides](https://www.spacebring.com/docs/developer/api/guides/create-an-attachment-upload.md), send the
file to the presigned URL with the headers returned, then pass the returned key in `activity.attachments` when you [create a ticket
comment](https://www.spacebring.com/docs/developer/api/support/create-a-ticket-comment.md) within 25 minutes, or in `attachments` when you [create a
guide](https://www.spacebring.com/docs/developer/api/guides/create-a-guide.md) or [update a guide](https://www.spacebring.com/docs/developer/api/guides/update-a-guide.md) within an hour. A key that is
unknown, expired, already attached, or uploaded by another network now fails with `400` and the code `fileUploadNotFound`, where a ticket
comment returned `404` and a guide dropped the attachment, and one whose file is still in transit fails with `409` and
`fileUploadPending`. See [File uploads](https://www.spacebring.com/docs/developer/api/file-uploads.md) for the full flow.

**September 30, 2026**

[Retrieve resource assignments](https://www.spacebring.com/docs/developer/api/resources/retrieve-resource-assignments.md) no longer returns an assignment that a
subscription reserved during a checkout that expired without completing. Such a reservation never held the resource, as creating or
updating an assignment already ignored it once expired, but it stayed in the list until it was deleted, which could take days.

**September 30, 2026**

Check-ins are part of the API. [Retrieve check-ins](https://www.spacebring.com/docs/developer/api/check-ins/retrieve-check-ins.md) lists a location's check-ins, newest
arrival first, filtered by arrival date, `status`, `type`, or `userRef`, and [get a check-in](https://www.spacebring.com/docs/developer/api/check-ins/get-a-check-in.md)
returns one by its id. [Check in](https://www.spacebring.com/docs/developer/api/check-ins/check-in.md) records an arrival for a booking, an event ticket, a visit, or a
member's subscription, found by its check-in id, by a location and a six-digit code, or by a location and a `customerRef`, and [check
out](https://www.spacebring.com/docs/developer/api/check-ins/check-out.md) records the departure. They come with their own OAuth scopes: reading needs `checkIns.readonly`
or `checkIns`, and checking in or out needs `checkIns`. With a bearer token, the user must be an administrator of the check-in's location.

**September 30, 2026**

Contract template files can be uploaded through the API. [Create a template upload](https://www.spacebring.com/docs/developer/api/contracts/create-a-template-upload.md) for
a .docx file of up to 50 MB, send the file to the presigned URL, then pass the returned key as `template.file.key` when you [create a
template](https://www.spacebring.com/docs/developer/api/contracts/create-a-template.md) or [update a template](https://www.spacebring.com/docs/developer/api/contracts/update-a-template.md). A key that is
unknown, expired, already used, or uploaded by another network now fails with `400` and the code `fileUploadNotFound` instead of `404`,
and one whose file is still in transit with `409` and `fileUploadPending`. An update that replaces the file fails with `409` and the code
`conflict` when another request replaced it first. See [File uploads](https://www.spacebring.com/docs/developer/api/file-uploads.md) for the full flow.

**September 29, 2026**

Product, resource, guide, and post media and company logos can be uploaded through the API. Create an upload with
[products](https://www.spacebring.com/docs/developer/api/shop/create-a-media-upload.md), [resources](https://www.spacebring.com/docs/developer/api/resources/create-a-media-upload.md),
[guides](https://www.spacebring.com/docs/developer/api/guides/create-a-media-upload.md), [posts](https://www.spacebring.com/docs/developer/api/feed/create-a-media-upload.md), or
[companies](https://www.spacebring.com/docs/developer/api/community/create-a-logo-upload.md), send the file to the presigned URL, then attach it: `media[0].key` on a
product, a key in `media` on a resource or a post, a Markdown image with the returned `url` in a guide `description`, or `logo.key` on a
company. Guides and posts also take MP4, QuickTime, and WebM videos up to 50 MB. [Create a
company](https://www.spacebring.com/docs/developer/api/community/create-a-company.md) and [update a company](https://www.spacebring.com/docs/developer/api/community/update-a-company.md) now accept `logo`,
where `null` removes it, and companies return `logo` with its `key` and `url`. An attached key that is unknown, expired, or already used
fails with `fileUploadNotFound`, and one whose file is still in transit with `fileUploadPending`. See [File
uploads](https://www.spacebring.com/docs/developer/api/file-uploads.md) for the full flow.

**September 28, 2026**

A resource can have up to 10 images. `media` lists them in display order, and `imageUrl` is the URL of the first one, the resource's
cover. When you [create a resource](https://www.spacebring.com/docs/developer/api/resources/create-a-resource.md) or [patch a
resource](https://www.spacebring.com/docs/developer/api/resources/patch-a-resource.md), `media` sets the whole list in the order given, so send the current keys in a new
order to reorder the images, or an empty list to remove them all. A patch without `media` keeps the current images. Before, a patch used
only the first key in `media` and ignored an empty list. See [Get a resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md).

**September 28, 2026**

[Retrieve bookings](https://www.spacebring.com/docs/developer/api/resources/retrieve-bookings.md) sorts by cancellation with `order=deleteDate:desc` or
`order=deleteDate:asc`. The list then holds only cancelled bookings, ordered by their `deleteDate`, and `status` defaults to `canceled`.
It works with every lookup the endpoint supports, but not with `singleBookings`, which returns a validation error as it does for
`createDate`.

**September 25, 2026**

Location and resource schedules can stay open past midnight. A schedule item's `hours.to` is counted from the start of its weekday, so a
day open from 6:00 PM to 2:00 AM returns `from: "18:00:00"` and `to: "26:00:00"`, at most 24 hours after `from`. Parse `hours.to` as a
number of hours and minutes rather than as a time of day. Bookings inside such a day can run past midnight, and a hot desk booking spends
one day pass per seat for each schedule day it covers. See [Get a location](https://www.spacebring.com/docs/developer/api/locations/get-a-location.md) and [Get a
resource](https://www.spacebring.com/docs/developer/api/resources/get-a-resource.md).

**September 24, 2026**

Orders can carry the `external` payment method, which an administrator uses to record a payment collected outside Spacebring, such as cash
or a bank transfer. When [getting an order](https://www.spacebring.com/docs/developer/api/shop/get-an-order.md) or [retrieving orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md),
such an order returns `payment.method.type` as `external` and the paying customer in `payment.method.external.customer`. When the payment
is recorded as still owed, `payment.status` stays `pending` until it is marked as paid. The `shop.order.created` and `shop.order.paid`
[webhooks](https://www.spacebring.com/docs/developer/webhooks.md) carry the same payment with `type` set to `external`.

**September 23, 2026**

[Update a booking](https://www.spacebring.com/docs/developer/api/resources/update-a-booking.md) paid by card or externally to extend it or add seats. The added part is
charged as a separate money transaction, so `payments` lists one entry per charge, the booking stays `tentative` while the charge is
pending, and a failed charge returns the booking to its previous interval instead of canceling it. Shortening such a booking is still
rejected with `bookingDurationChangeNotAllowed` for users and is not refunded for administrators, and a change to the duration or seats
while a payment is pending is rejected with `bookingPaymentPending`. See [Get a booking](https://www.spacebring.com/docs/developer/api/resources/get-a-booking.md) for the
`payments` field.

**September 23, 2026**

The `benefit.application.created` payload always includes the `benefit` object with the applied benefit's `id` and `title`, so an
integration no longer has to treat it as optional. No other field of the payload changes. See [Webhooks](https://www.spacebring.com/docs/developer/webhooks.md).

**September 22, 2026**

Shop orders paid through a payment gateway are created with the `pending` status and move to `new` once the payment succeeds. Pass
`status=pending` when you [retrieve orders](https://www.spacebring.com/docs/developer/api/shop/retrieve-orders.md) to list them; the default status filter still excludes
them. Updating a pending order fails with a validation error until its payment completes.

**September 22, 2026**

[Check resource availability](https://www.spacebring.com/docs/developer/api/resources/check-resource-availability.md) before creating a booking. Send the `startDate` and
`endDate` of the slot, plus `quantity` for seat-based resources such as hot desks, `entire` to check a whole office, or `recurrence` RRULE
lines for a repeating slot. The response returns `available`, and when the slot cannot be booked, a `reason` with the `code` and `message`
the booking would fail with, such as `bookingConflict` or `bookingScheduleConflict`. The same capacity, schedule, duration, and booking
window rules as booking creation apply.

**September 11, 2026**

Event cover images can be uploaded through the API. [Create a media upload](https://www.spacebring.com/docs/developer/api/events/create-a-media-upload.md) to get a
presigned URL, send the file to it, then pass the returned `key` as `media[0].key` when creating or updating an event. Creating or
updating an event with a key that is unknown, not yet uploaded, or expired now fails with the `fileUploadNotFound` code, or
`fileUploadPending` while the file is still in transit, instead of saving the event without an image. See [File
uploads](https://www.spacebring.com/docs/developer/api/file-uploads.md) for the full flow.

**September 10, 2026**

Transactions share one response format across credits, day passes, and money, and money transactions can now be updated and refunded through the API:

* **All transaction responses**: `customer` identifies the company or user the transaction belongs to, `product` links the transaction to its booking, ticket, order, invoice, or subscription and carries a display `title`, and `userCreatedBy` names who created it
* **Credits and day pass transactions**: `amounts` splits a charge across the expiring and permanent balances it was deducted from
* **Money transactions**: `payment` carries the payment method, price, surcharge, refunds, dispute, and whether the payment is still refundable, alongside top-level `currencyCode`, `customerName`, `customerTaxId`, `customerAddress`, and `receiptPdfUrl`
* **New money routes**: [update a money transaction](https://www.spacebring.com/docs/developer/api/transactions/update-a-money-transaction.md) to approve or cancel a pending external payment, and [refund a money transaction](https://www.spacebring.com/docs/developer/api/transactions/refund-a-money-transaction.md) fully or partially through the payment gateway it was paid with

The previous fields are deprecated and will be removed in a future release:

* `membershipRef`, `companyRef`, `company`, `user`, and `userOwner` — use `customer` and `customer.user` instead
* `membershipRefCreator`, `userCreator`, and `userRefCreator` — use `userCreatedBy` instead
* The `booking`, `ticket`, `order`, `invoice`, `plan`, and `creditPackage` embeds — use `product` instead
* `expiringAmount` and `permanentAmount` on credits transactions — use `amounts` instead
* `paymentMethod`, `refund`, `refunds`, `billingAddressBy`, and `billingAddressTo` on money transactions — use `payment.method`, `payment.refunds`, `locationAddress`, and `customerAddress` instead
* `membershipRef` and `companyRef` in transaction list queries and in create credit or day pass transaction requests — pass `customerRef` instead

The deprecated fields keep working for now, so existing integrations are not affected. We recommend migrating to the new fields at your earliest convenience.

**September 9, 2026**

Create booking requests accept a `paymentMethod` with the `external` type to record a payment collected outside Spacebring. Pass
`external.status` as `succeeded` to confirm the booking, or `pending` to keep it tentative until the payment is marked as paid. Spacebring
issues the invoice once the payment is confirmed.

**September 2, 2026**

New webhook event types for events, alongside the existing `event.created`:

* `event.updated` — sent when an event's details change
* `event.canceled` — sent when an event is canceled
* `event.deleted` — sent when an event is deleted

The event payload now includes `cancelDate` and `deleteDate`. Select the new event types for your endpoint in **Network Settings** > **Developers**.

**July 30, 2026**

Support ticket assignees are now users instead of memberships. The membership-based assignee fields are deprecated and will be removed in a future release:

* **Ticket responses**: `membershipAssignee` and `membershipRefAssignee` are deprecated — use `userAssignee` and `userRefAssignee` instead
* **Ticket activity responses**: `data.membershipAssignee` and `data.previousAttributes.membershipAssignee` are deprecated — use `data.userAssignee` and `data.previousAttributes.userAssignee` instead
* **Update ticket assignee requests**: `ticket.membershipRefAssignee` is deprecated — pass `ticket.userRefAssignee` with the ID of the user to assign, or `null` to unassign

The deprecated fields keep working for now, so existing integrations are not affected. We recommend migrating to the user-based fields at your earliest convenience.

**March 2026**

New API routes for floors management:

* Retrieve a list of all floors
* Delete a floor

New Discounts section with API routes for coupons and promocodes:

* Retrieve, create, get, update, and delete coupons
* Retrieve, create, get, and archive promocodes
* Retrieve promocode redemptions

**February 2026**

New API routes for credit notes management:

* Issue, preview and update credit notes

New API routes for invoice management:

* Update, delete, duplicate, issue, void, and resend invoices
* Cancel a payment on an invoice
* Retrieve an upcoming invoice preview
* Search invoices by code or number

New API routes for invoice item management:

* Retrieve, update, and delete invoice items
* List invoice items by invoice, scheduled, or upcoming

New API routes for guide management:

* Retrieve a single guide or list of all guides
* Add, modify, and delete guides

**January 2026**

Manage subscriptions with ease! With new API routes, you can:

* Retrieve subscription data
* Add, modify, and delete subscription items
* Patch subscription details, as advance invoicing, pause payment collection etc.

Streamline your subscription management and enhance customer experience!

**September 2025**

Check out new ways to manage visitors! With new API routes, you can:

* Check in and check out visitors
* Create visit requests
* Approve and reject requests
* Register contacts

Build better community with your customers using new capabilities!

**August 2025**

Comprehensive social feed management capabilities:

• **Feed Posts Management**
– Create, retrieve, update, and delete feed posts seamlessly
– Browse all posts with filtering by hashtags and pagination

• **Interactive Comments System**
– Add, retrieve, and manage comments on any feed post
– Enable rich discussions and community engagement

• **Social Engagement Features**
– Like and unlike both posts and comments

Build dynamic social experiences and foster community engagement with these powerful feed management tools!

**August 2025**

Introducing comprehensive support and subscription management capabilities:

• **Support**
– Open, update, and close support tickets effortlessly

• **Subscription Plans**
– Create, modify, and monitor customer plans

Unlock new possibilities for customer service and subscription management with these robust tools!

**June 2025**

Major expansion in product catalog and event coordination features:

• **Product & Order Management**
– Add or modify products with a single call
– Place, track, and update orders seamlessly

• **Event Management**
– Schedule events, manage details, and publish updates

Transform how you handle events—streamline operations like never before!

**April 2025**

Powerful new capabilities for benefits administration and visitor insights:

• **Benefits & Applications**
– Create, organize, and update benefit and their categories
– Submit and review user applications in one go

• **Visitor Tracking**
– Capture and query visitors data

Enhance your platform with better benefits and visitor management!

**October 2024**

Introducing New API & Webhooks

We’re thrilled to introduce the newly redesigned Spacebring API, built from the ground up to help you create more powerful, seamless integrations and automated workflows.

Expanded Endpoints: Take advantage of the restructured existing endpoints and many new ones to build more flexible, custom integrations.
Webhook Support: Receive real-time event notifications, enabling faster and more responsive interactions.
Improved Documentation: Get up and running with the development process more quickly thanks to helpful explanations in our newly added guides.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.