Skip to main content
GET
Search AutomationTiles
An AutomationTile represents a physical NFC chip and QR code tile that triggers actions in a Nexudus-powered coworking space. Each tile is linked to a single action (e.g. check-in, booking, door unlock, HTTP request) that fires when a customer scans or taps the tile. The Action field determines what happens when the tile is scanned. Some actions require additional data in ActionParameters: Tiles can optionally be geo-fenced to restrict scanning to a physical area around the tile’s installed location. Enable EnableGeofence, set Latitude/Longitude, and choose a GeofencePrecission level. MaxDistanceMeters overrides the precision preset with a custom radius. Set CheckCustomerIn to also check the customer into the space when they scan the tile, regardless of the tile’s primary action.

Authentication

This endpoint requires OAuth2 authentication. Include a valid bearer token in the Authorization header. The authenticated user must be a full unrestricted administrator or have the AutomationTile-List role.

Enums

Query Parameters

Pagination & Sorting

integer
default:"1"
The page number to retrieve.
integer
default:"25"
The number of records per page.
string
The property name to sort results by (e.g. Name, CreatedOn).
integer
Sort direction. 0 for ascending, 1 for descending.

Filters

integer
Filter by iD of the business linked to this record.
string
Filter by tile name used to identify it in the admin panel.
string
Filter by unique tile identifier (GUID) auto-assigned on creation. Used to generate the QR code and NFC URL.
integer
Filter by action triggered when the tile is scanned: None, CheckIn, CheckOut, BookingCheckIn, EventCheckIn, ExtendBookingBy, RequestUrl, RedirectUrl, ResourceCleaned, BookResource, BookDesk, ShowNewBookingForm, UnlockAct365Door, UnlockDoorDeckDoor, UnlockKisiDoor, SmartLock, etc..
string
Filter by parameters for the selected action. Format depends on the action type — e.g. a resource ID, a URL, or a resource ID|duration pair.
boolean
Filter by whether to restrict the tile to a geographic area. When enabled, the tile only works if the user is within the configured radius of the tile’s coordinates.
boolean
Filter by whether to also check the customer into the space when they scan the tile, regardless of the primary action.
string
Filter by longitude of the tile’s installed location. Used for geofencing.
string
Filter by latitude of the tile’s installed location. Used for geofencing.
integer
Filter by geofence precision level: Low, Medium, High, or VeryHigh. Higher precision requires the user to be closer to the tile coordinates.
integer
Filter by custom maximum distance in meters from the tile’s coordinates. Overrides the precision preset when set.
string
Filter by custom message shown to the user when the tile action completes successfully.
string
Filter by custom error message shown to the user when the tile action fails.

Range Filters

integer
Filter by custom maximum distance in meters from the tile’s coordinates. Overrides the precision preset when set greater than or equal to this value.
integer
Filter by custom maximum distance in meters from the tile’s coordinates. Overrides the precision preset when set less than or equal to this value.
string
Filter records created on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records created on or before this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or after this date. Format: YYYY-MM-DDTHH:mm.
string
Filter records updated on or before this date. Format: YYYY-MM-DDTHH:mm.

Code Examples

Simple listing

Filtering by Name

Range filters

Response

200

AutomationTile[]
The list of AutomationTile records matching the query. See the Get one AutomationTile endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each AutomationTile. The following fields are not populated in the Records[] response: Action, GeofencePrecission.To get all fields, fetch the full record using the Get one AutomationTile endpoint.Important for updates: When updating a record via PUT, always retrieve the full record with a GET request first, apply your changes to that complete data, and then send the updated record. Do not use data from a listing response as the base for a PUT request, as missing fields may be unintentionally cleared.
integer
Current page number.
integer
Number of records per page.
string
The field used for sorting.
integer
The sort direction (0 = ascending, 1 = descending).
integer
Index of the first item on the current page.
integer
Index of the last item on the current page.
integer
Total number of matching records across all pages.
integer
Total number of pages.
boolean
Whether there is a next page of results.
boolean
Whether there is a previous page of results.
Example Response