Reference · built on requestConnectorHospitality & property systems

OfficeRnD

Members, bookings, resources, check-ins, visitors, and billing events from OfficeRnD, with booking and visitor proposals.

Request accessPricing ↗

About

OfficeRnD is a flexible workspace management platform. Its data model covers companies, members, and users; locations, floors, resources, and assignments; bookings, visitors, and visits; payments, charges, fees, plans, contracts, and memberships; and events, posts, issues, and check-ins. API v2 is a server-to-server interface at https://app.officernd.com/api/v2, with every path scoped to /organizations/{orgSlug}. Webhooks post member, company, booking, invoice, membership, contract, ticket, and pass events to an endpoint you register.

Through Fibric, an operator reads bookings against check-ins, visitor lists, and membership changes, then proposes a booking, a pre-registered visitor, a ticket, or a member check-in. Nothing is written until you approve, and each approved write is logged with its reason.

This is a reference listing. It documents what Fibric would read from OfficeRnD and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Members and companies through GET /organizations/{orgSlug}/members and /companies, with member.created, member.updated, and company.updated webhook events
  • Booking series, one-off bookings, and expanded occurrences through GET /organizations/{orgSlug}/bookings and /bookings/occurrences, plus booking.created, booking.updated, and booking.removed events
  • Locations, floors, and resources such as rooms and desks through GET /organizations/{orgSlug}/resources and the Space Management reference
  • Check-ins through GET /organizations/{orgSlug}/checkins, filtered by member, location, source, and start or end with $gte and $lte
  • Visitors and visits through GET /organizations/{orgSlug}/visitors and /visits
  • Invoices, charges, fees, memberships, and contracts through invoice.*, fee.*, membership.*, and contract.* webhook events and the Billing reference
  • Day pass sets and occupancy slots through GET /organizations/{orgSlug}/passes and the pass.updated and occupancyslot.created events

Proposed actions

  • Target capability: propose a booking through POST /organizations/{orgSlug}/bookings with start, end, and resource, sent with enforceBookingPolicy
  • Target capability: propose cancelling a confirmed booking through POST /organizations/{orgSlug}/bookings/{bookingId}/cancel, which may notify the member or generate a cancellation fee
  • Target capability: propose a pre-registered visitor through POST /organizations/{orgSlug}/visitors with type preregistration
  • Target capability: propose a ticket through POST /organizations/{orgSlug}/tickets for an issue a member reports
  • Target capability: propose a member check-in through the Check in a Member call on /checkins

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Free a room that stayed empty

    Booking occurrences give the expected arrivals. Check-ins filtered by location and start show whether the member came. If not, the operator proposes cancelling the booking so the room returns to inventory.

    With Meeting Room Reset

  • Pre-register tomorrow's guests

    Bookings that name visitors are read the evening before. The operator proposes one visitor record per guest with type preregistration, and reception sees the list once you approve.

    With Visitor Pre-Registration

  • Route a member's ticket

    A ticket.created event carries the issue. The operator matches it to the location and resource and proposes an owner and a reply for your approval.

    With Request Routing

  • Pull door access when a membership ends

    membership.removed and contract.updated events mark the end. The operator proposes revoking the member's credential in your access control system and keeps the record of who approved it.

    With Access Offboarding

Requirements

  • An OfficeRnD organization and an application created under Settings/Data & Extensibility/Developer Tools with resource-level permissions
  • A scope for each resource the operator touches, named product.category.resource.permission, for example flex.space.bookings.create
  • Your organization slug from Settings > My Account, used in every /organizations/{orgSlug} path
  • A server-side token exchange; CORS is disabled on the token endpoint
Authentication
OAuth 2.0 client credentials: an application's client_id and client_secret exchanged at https://identity.officernd.com/oauth/token for a bearer token that lasts 3600 seconds and carries the scopes you request.

Limits

  • 400 read and 100 write requests per minute per integration per organization, up to 20,000 reads and 5,000 writes a day
  • Pages hold at most 50 items and advance with $cursorNext; an $in filter takes at most 50 values
  • API v1 scopes officernd.api.read and officernd.api.write do not work on v2 endpoints, and $populate is deprecated
  • Webhook signing and retry behavior are not covered on the pages read for this listing

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request OfficeRnD ↗

Questions and answers

Which OAuth flow does OfficeRnD API v2 use?
Client credentials only. Post client_id, client_secret, grant_type=client_credentials, and scope to https://identity.officernd.com/oauth/token. Tokens are valid for 3600 seconds. Scopes are resource-level, such as flex.community.members.read or flex.billing.payments.create; the flex prefix refers to the platform codebase, not a plan.
What are the API rate limits?
400 read requests per minute, up to 20,000 a day, and 100 write requests per minute, up to 5,000 a day. Limits apply per user or integration per organization, and reads and writes are counted separately.
Which webhook events can OfficeRnD send?
company, member, invoice, invoice.charge, fee, membership, booking, contract, and ticket events for created, updated, and removed; pass.created and pass.updated; occupancyslot.created and removed; and integration.removed. Endpoints are added under Settings, Developer Tools, Webhooks or through /webhooks. Payloads carry event, eventType, data.object, and createdAt.
Ask about OfficeRnD

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with OfficeRnD through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy