Skip to main content
GET
Search AccessTokens
WiFi Access Tokens provide unique network access codes for customers and visitors. They work alongside the Mikrotik, IronWifi, and Layer8 integrations. Access tokens can be shared with customers and visitors as part of visitor and booking confirmation emails. Each token includes a number of minutes of WiFi access and, optionally, an expiration date and user limit.

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 AccessToken-List role.

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 unique network access code used to connect to WiFi.
string
Filter by free-text description of this access token.
integer
Filter by total minutes of WiFi access included in this token.
string
Filter by start date from which this token can be used.
string
Filter by expiration date after which this token is no longer valid.
integer
Filter by maximum number of users that can use this token simultaneously.
integer
Filter by remaining minutes of WiFi access available on this token.
string
Filter by mAC address of the device associated with this token.
string
Filter by unique identifier (GUID) for the booking.
string
Filter by unique identifier (GUID) for the visitor.
string
Filter by date and time this token was last used to connect.

Range Filters

integer
Filter by total minutes of WiFi access included in this token greater than or equal to this value.
integer
Filter by total minutes of WiFi access included in this token less than or equal to this value.
string
Filter by start date from which this token can be used greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
string
Filter by start date from which this token can be used less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
string
Filter by expiration date after which this token is no longer valid greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
string
Filter by expiration date after which this token is no longer valid less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
integer
Filter by maximum number of users that can use this token simultaneously greater than or equal to this value.
integer
Filter by maximum number of users that can use this token simultaneously less than or equal to this value.
integer
Filter by remaining minutes of WiFi access available on this token greater than or equal to this value.
integer
Filter by remaining minutes of WiFi access available on this token less than or equal to this value.
string
Filter by date and time this token was last used to connect greater than or equal to this value. Format: YYYY-MM-DDTHH:mm.
string
Filter by date and time this token was last used to connect less than or equal to this value. Format: YYYY-MM-DDTHH:mm.
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 AccessCode

Range filters

Response

200

AccessToken[]
The list of AccessToken records matching the query. See the Get one AccessToken endpoint for the full list of properties returned for each record.
Partial records — The listing endpoint returns a summary representation of each AccessToken. The following fields are not populated in the Records[] response: MinutesIncluded, ValidTo, UserLimit.To get all fields, fetch the full record using the Get one AccessToken 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