Skip to main content
POST
/
api
/
sys
/
automationtileaudits
Create AutomationTileAudit
curl --request POST \
  --url https://spaces.nexudus.com/api/sys/automationtileaudits \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "AutomationTileId": 123,
  "Description": "<string>",
  "Action": 123,
  "TileAuditType": 123
}
'
{
  "Status": 123,
  "Message": "<string>",
  "Value": "<any>",
  "WasSuccessful": true,
  "Errors": [
    {
      "AttemptedValue": "<any>",
      "Message": "<string>",
      "PropertyName": "<string>"
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt

Use this file to discover all available pages before exploring further.

An AutomationTileAudit is a log entry recorded each time an AutomationTile is scanned or tapped. It captures the outcome (success or failure), the action that was triggered, and the identity of the user who scanned the tile. Use this entity to review tile usage history, troubleshoot scanning failures, and track which customers are interacting with specific tiles.

​
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 AutomationTileAudit-Create role.

​
Enums

ValueName
1None
2UnlockAct365Door
3CheckIn
4CheckOut
5BookingCheckIn
6EventCheckIn
7ResourceCleaned
8RequestUrl
9RedirectUrl
10UnlockDoorDeckDoor
11UnlockKisiDoor
12BookResource
13BookDesk
14ShowNewBookingForm
15SmartLock
16ExtendBookingBy
17ShowAcsModal
18UnlockPadWordDoor
19UnlockOPaxtonNet2Door
ValueName
1Success
2Failure

​
Request Body

​
Required Fields

​
AutomationTileId
integer
required
Automation Tile Id.
​
Description
string
required
Human-readable description of what happened when the tile was scanned.
​
Action
integer
required
The action that was triggered when the tile was scanned (matches the tile’s configured action).
​
TileAuditType
integer
required
Outcome of the scan: Success or Failure.

​
Optional Fields

​
ActionBy
string
Name or identifier of the customer who scanned the tile.

​
Code Examples

curl -X POST \
  "https://spaces.nexudus.com/api/sys/automationtileaudits" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "AutomationTileId": 0,
    "Description": "",
    "Action": 0,
    "TileAuditType": 0
}'

​
Response

​
200

​
Status
integer
HTTP status code. 200 on success.
​
Message
string
A human-readable message confirming the creation.
​
Value
object
Contains the Id of the newly created record.
​
WasSuccessful
boolean
true if the automationtileaudit was created successfully.
​
Errors
array
null on success.
Example Response
{
  "Status": 200,
  "Message": "AutomationTileAudit was successfully created.",
  "Value": {
    "Id": 87654321
  },
  "OpenInDialog": false,
  "OpenInWindow": false,
  "RedirectURL": null,
  "JavaScript": null,
  "UpdatedOn": "2025-01-15T10:30:00Z",
  "UpdatedBy": "admin@example.com",
  "Errors": null,
  "WasSuccessful": true
}

​
400

​
Message
string
A summary of the validation error(s), in the format PropertyName: error message.
​
Value
any
null on validation failure.
​
Errors
object[]
Array of validation errors.
​
WasSuccessful
boolean
false when the request fails validation.
Example Response
{
  "Message": "Description: is a required field",
  "Value": null,
  "Errors": [
    {
      "AttemptedValue": null,
      "Message": "is a required field",
      "PropertyName": "Description"
    }
  ],
  "WasSuccessful": false
}