Skip to main content
Subscribe to our newsletter to be notified about developer platform updates.
​
MCP
The MCP server reads check-ins with two new tools: getCheckIns lists the arrivals and departures in a location for desk and room bookings, event tickets, visits, and subscriptions, filtered by status, type, user, or arrival date range, and getCheckIn returns one check-in by its id. Both need the checkIns.readonly or checkIns scope, which the server now requests. See Retrieve check-ins and Get a check-in for the fields they return.
​
REST API
Check-ins are part of the API. Retrieve check-ins lists a location’s check-ins, newest arrival first, filtered by arrival date, status, type, or userRef, and get a check-in returns one by its id. Check in 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 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.
​
REST API
Contract template files can be uploaded through the API. Create a template upload 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 or update a template. 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 for the full flow.
​
REST API
Product, resource, guide, and post media and company logos can be uploaded through the API. Create an upload with products, resources, guides, posts, or companies, 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 and update a company 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 for the full flow.
​
REST API
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 or patch a resource, 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.
​
REST APIMCP
Retrieve bookings 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. The MCP server’s getBookings tool accepts the same order.
​
REST API
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 and Get a resource.
​
REST APIWebhooks
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 or retrieving orders, 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 carry the same payment with type set to external.
​
REST API
Update a booking 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 for the payments field.
​
Webhooks
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.
​
REST API
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 to list them; the default status filter still excludes them. Updating a pending order fails with a validation error until its payment completes.
​
REST API
Check resource availability 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.
​
REST API
Event cover images can be uploaded through the API. Create a media upload 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 for the full flow.
​
REST API
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 to approve or cancel a pending external payment, and refund a money transaction 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.
​
REST API
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.
​
Webhooks
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.
​
REST API
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.
​
REST API
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
​
REST API
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
​
REST API
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!
​
REST API
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!
​
REST API
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 commentsBuild dynamic social experiences and foster community engagement with these powerful feed management tools!
​
REST API
Introducing comprehensive support and subscription management capabilities:• Support – Open, update, and close support tickets effortlessly• Subscription Plans – Create, modify, and monitor customer plansUnlock new possibilities for customer service and subscription management with these robust tools!
​
REST API
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 updatesTransform how you handle events—streamline operations like never before!
​
REST API
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 dataEnhance your platform with better benefits and visitor management!
​
REST APIWebhooks
Introducing New API & WebhooksWe’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.