OfficeSpace Software

OfficeSpace Software is a leading workplace management platform for space planning, employee experience, asset management, and occupancy analytics. Organizations build data-driven floor plans, manage desk and room booking, track seating, run moves and changes, and gain real-time utilization insights across their real estate portfolio. Its AI-driven analytics help facilities teams right-size their footprint.

Power end-to-end data operations for your OfficeSpace Software API with Nexla. Our bi-directional OfficeSpace Software connector is purpose-built for OfficeSpace Software, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to OfficeSpace Software or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your OfficeSpace Software workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

To connect Nexla to your OfficeSpace Software instance, you will need an active OfficeSpace account with administrator access and an API token for your OfficeSpace instance. OfficeSpace authenticates API requests using a token-based scheme — each request from Nexla is signed with your API token and routed to your specific instance subdomain.

Obtain Your OfficeSpace Instance Hostname

Your OfficeSpace instance hostname is the subdomain of your OfficeSpace URL. For example, if your OfficeSpace environment is accessed at mycompany.officespacesoftware.com, your hostname is mycompany.

• If you are unsure of your instance hostname, contact your OfficeSpace administrator or check the URL you use to log in to OfficeSpace.

Generate an OfficeSpace API Token

OfficeSpace API tokens are generated from the Admin section of your OfficeSpace instance. Only users with Super Administrator privileges can create and manage API keys.

1. Log in to your OfficeSpace instance with a Super Administrator account.

2. In the left-side navigation bar, locate and click the Admin section to expand the admin menu.

3. Select OfficeSpace API from the admin menu. This opens the API Key management screen.

4. Click the button to create a new API key. OfficeSpace currently supports Full Access as the API key scope — this grants Nexla the ability to read and write data through the OfficeSpace API.

5. Copy the generated API token and store it securely. You will need this token when creating the Nexla credential.

API keys are instance-specific and are tied to your OfficeSpace subdomain. Keep your API token secure and do not share it. For additional information about managing API keys in OfficeSpace, refer to the Managing API Keys article in the OfficeSpace Help Center.

Authenticate

Credentials required

Authenticate using your OfficeSpace instance hostname and API token.

Field	Required	Secret	Description
Instance Hostname	Yes	No	Your OfficeSpace subdomain. For mycompany.officespacesoftware.com, enter mycompany.
API Key	Yes	Yes	OfficeSpace API token. Generate from Admin > OfficeSpace API in your instance settings.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. OfficeSpace Software uses token-based authentication. Nexla will include your API token in the Authorization request header (formatted as Authorization: Token token=<your_api_key>) on every API call to your OfficeSpace instance. Enter your OfficeSpace instance subdomain in the Instance Hostname field. This is the portion of your OfficeSpace URL that precedes .officespacesoftware.com. For example, if your OfficeSpace environment is at mycompany.officespacesoftware.com, enter mycompany.

4. Enter your OfficeSpace API token in the API Key field. This is the token generated from the Admin > OfficeSpace API section of your OfficeSpace instance. The API key authenticates all Nexla requests to your OfficeSpace environment and should be kept secure.

   Important

   Your API Key is a sensitive credential. Do not share it or expose it in logs or source control. If you believe your key has been compromised, regenerate it immediately from the Admin > OfficeSpace API screen in your OfficeSpace instance.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the OfficeSpace Software connector tile, then select the credential that will be used to connect to the OfficeSpace Software instance, and click Next; or, create a new OfficeSpace Software credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common OfficeSpace Software endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get Employees

Retrieve all active employees in your OfficeSpace directory, including profile fields, seating status, seat URLs, and directory metadata. Use this endpoint to export your organization's complete employee roster for HR analytics, workforce planning, or synchronization with external systems.

• This endpoint requires no additional parameters. Selecting it will automatically retrieve all active employee records from your OfficeSpace instance.
• Each returned record includes employee profile fields (such as name, email, and department), their current seating assignment, seat URL, and any directory group memberships.

The OfficeSpace API returns employee data under the $.response[*] path. Nexla automatically applies this path when using the pre-built template. For additional details about the OfficeSpace employee data model, refer to the OfficeSpace API documentation.

Get Seats

Retrieve all seats in your OfficeSpace environment, including occupancy status, floor reference, seat label, and the current occupant URL. Use this endpoint for space utilization analysis, desk allocation reporting, or feeding occupancy data into downstream analytics tools.

• This endpoint requires no additional parameters. Selecting it will automatically retrieve all seat records across all floors and sites in your OfficeSpace instance.
• Each returned record includes the seat's label, its associated floor, its occupancy status (occupied or vacant), and a URL reference to the current occupant's employee record if occupied.

Seat data is particularly useful when combined with floor and site data from the Get Floors and Get Sites endpoints to build a complete picture of your organization's space utilization.

Get Floors

Retrieve all floors in your OfficeSpace environment, including floor labels, site associations, and directory group references. Use this endpoint to map your organization's physical space hierarchy or to enrich seat and employee data with floor-level context.

• This endpoint requires no additional parameters. Selecting it will automatically retrieve all floor records across all sites in your OfficeSpace instance.
• Each returned record includes the floor's label, its parent site association, and any linked directory groups that control visibility or access for that floor.

Floor IDs returned by this endpoint can be used to cross-reference seat records from the Get Seats endpoint, enabling complete floor-to-seat mapping in your Nexla data flows.

Get Sites

Retrieve all office sites in your OfficeSpace portfolio, including site name and site ID. Use this endpoint for multi-location portfolio analysis, real estate planning, or to provide site context when joining with floor and seat data.

• This endpoint requires no additional parameters. Selecting it will automatically retrieve all site records for your OfficeSpace instance.
• Each returned record includes the site's name and its unique OfficeSpace site ID, which can be used to associate floors and seats with specific physical office locations.

Site IDs are useful as join keys when building multi-source Nexla flows that combine site, floor, seat, and employee data for comprehensive occupancy reporting.

Get Directories

Retrieve all floor directories in your OfficeSpace environment, including system visibility groups such as Make Public and Make Private. Use this endpoint to understand how seat and floor data is organized and filtered across your organization.

• This endpoint requires no additional parameters. Selecting it will automatically retrieve all directory records for your OfficeSpace instance.
• Each returned record includes the directory name and its visibility configuration, which controls whether associated floors and seats appear in public or restricted views within OfficeSpace.

Directory data is primarily useful for administrative reporting and for understanding how OfficeSpace visibility rules affect seat and floor data returned by the Get Seats and Get Floors endpoints.

Get Employee by ID

Retrieve a single employee record by their OfficeSpace internal employee ID, including full seating details, profile fields, and directory membership information. Use this endpoint when you need to enrich or validate a specific employee's data in a targeted data flow.

• Enter the OfficeSpace internal employee ID in the Employee ID field. This is a required parameter. The employee ID is the unique identifier assigned to each employee by OfficeSpace — it is distinct from your HR system's employee ID.

  • To find an employee's OfficeSpace ID, first use the Get Employees endpoint to retrieve a list of all active employees. Each employee record in that response includes the OfficeSpace internal ID that can be used here.
• Once the Employee ID is entered, Nexla will retrieve the full record for that employee, including their profile fields, current seat assignment, seat URL, and directory group memberships.

The Get Employee by ID endpoint is best suited for targeted lookups or for flows where a specific employee ID is already known. To retrieve data for all employees, use the Get Employees endpoint instead.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

OfficeSpace Software data sources can also be manually configured to ingest data from any valid OfficeSpace API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

OfficeSpace API endpoints follow the pattern https://{hostname}.officespacesoftware.com/api/1/{resource} (e.g., employees, seats, floors, sites, directories). Responses wrap records in a top-level response object — set Path to Data in Response to $.response[*] for collection endpoints or $.response for single-record endpoints like Get Employee by ID. You do not need to include the Authorization header manually; Nexla automatically includes Authorization: Token token=<your_api_key> on every API call based on your configured credential.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new OfficeSpace Software data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the OfficeSpace Software destination, and select the Send to Destination option from the menu. Select the OfficeSpace Software connector from the list of available destination connectors, then select the credential that will be used to connect to the OfficeSpace Software organization, and click Next; or, create a new OfficeSpace Software credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common OfficeSpace Software endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Upsert Employees (Batch)

Batch create or update employee records in OfficeSpace from an external HRIS or enriched data pipeline source. Use this endpoint to synchronize your organization's employee directory with OfficeSpace — for example, to push new hires, update profile fields, or reflect organizational changes from an upstream HR system such as Workday, BambooHR, or ADP.

• This endpoint requires no additional configuration parameters beyond the credential selection. Nexla will POST the Nexset data as a JSON payload to the OfficeSpace batch import API endpoint at https://{hostname}.officespacesoftware.com/api/1/employee_batch_imports.

• Each record in the Nexset should correspond to one employee and should include the fields required by OfficeSpace's batch import API. Common fields include:

  • name — The employee's full name.
  • email — The employee's email address, used as a unique identifier for upsert operations.
  • department — The employee's department or team.
  • title — The employee's job title.
• OfficeSpace will create new employee records for employees that do not yet exist in the directory and update existing records for employees that are matched by email address.

After using the Upsert Employees (Batch) endpoint to stage employee records, use the Trigger Employee Directory Import destination in a subsequent flow step to migrate the staged records into the live OfficeSpace employee directory. For additional information about the OfficeSpace batch import process, refer to the OfficeSpace API documentation.

Trigger Employee Directory Import

Trigger the migration of staged employee records from a named source into the live OfficeSpace employee directory. Use this endpoint after completing an Upsert Employees (Batch) operation to finalize the synchronization and make the updated employee data visible in OfficeSpace.

• Enter the source system tag in the Source Name field. This is a required parameter. The Source Name must match the source tag used in the corresponding batch import step.

  • The default value is Nexla. Use this default value when the batch import was performed using Nexla's Upsert Employees (Batch) endpoint without a custom source tag.
  • If a custom source tag was used during batch import, enter that same tag here to ensure OfficeSpace imports the correct staged records.
• Nexla will POST a request to the OfficeSpace employee directory import API endpoint at https://{hostname}.officespacesoftware.com/api/1/employee_directory, triggering OfficeSpace to move the staged employee records into the live directory.

The Trigger Employee Directory Import endpoint is the second step in a two-stage employee synchronization workflow. Always run the Upsert Employees (Batch) endpoint first to stage employee records, then use this endpoint to commit those records to the live directory. Running this endpoint without a preceding batch import will have no effect.

Manual configuration

OfficeSpace Software destinations can also be manually configured to send data to any valid OfficeSpace API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the OfficeSpace Software API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

OfficeSpace API endpoints follow the pattern https://{hostname}.officespacesoftware.com/api/1/{resource} (e.g., employee_batch_imports, employee_directory); for update operations, include the ID of the object to be updated at the end of the URL. Most endpoints accept application/json, but the Trigger Employee Directory Import endpoint expects application/x-www-form-urlencoded — select Form URL Encoded as the content format for that endpoint. You do not need to include the Authorization header manually; Nexla automatically appends Authorization: Token token=<your_api_key> on every API call based on your configured credential. Batching is recommended when sending large numbers of employee records to the Upsert Employees (Batch) endpoint.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured OfficeSpace Software endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the OfficeSpace Software endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.