Skip to main content
Every automation tile has a URL encoded in its NFC chip and QR code. When a phone reads the tile, that URL is launched — normally opening the tile’s execution page in the browser. If you are running a white-label Passport app, you can register it to intercept that URL so the tile launches your app directly.

How tile URLs work

The URL encoded in each tile always includes the tile’s unique ID:
You can find this URL in the record of each tile you created in the Nexudus dashboard, under the Execute tile URL field. The ID is what your app needs to trigger the tile’s action through the API. If the customer doesn’t have your app installed — or your app isn’t registered to handle the URL — the default browser opens the tile URL instead, and the customer signs in to their account before the action runs.

Registering your app for tile URLs

To make the phone launch your app when a tile is scanned or tapped, register your app to handle the tile domain using universal links (iOS) or deep links (Android). See this guide for how to set that up in Android and iOS. Nexudus already generates the apple-app-site-association and assetlinks.json files for the tiles domain, so you only need to configure your app’s identifiers with Nexudus: The same values are available through the REST API under the MobileApp.iOS.*, MobileApp.Android.*, and AutomationTiles.SharedSecret keys — see Get business settings.

Executing a tile action from your app

Once your app has the tile ID from the URL, it can trigger the tile’s configured action by calling the tile execution endpoint on your location’s domain.

1. Get a bearer token for the customer

Use the Get a bearer token endpoint with the customer’s email and password:

2. Call the tile execution endpoint

Pass the token in the Authorization header:
A successful response looks like:

Geofenced tiles

If a tile is geofenced, the request must include the customer’s location and a signature proving it came from your app:
  • latitude and longitude — the customer’s current position
  • signature — the SHA256 hash of {tileId}|{latitude}|{longitude}|{secret}, where {secret} is the automation tiles shared secret configured for the location
Two details matter when building the hash:
  • Use the tile ID in lowercase. The tile URL shows the ID in uppercase, but the server signs with the lowercase form, so hashing the uppercase ID from the URL will fail.
  • If you haven’t set a shared secret for the location, the server falls back to the customer’s account creation date as the secret, formatted as yyyy-MM-ddTHH:mm:ss. Set an explicit shared secret so your app doesn’t have to look up each customer’s registration date.
Keep the shared secret protected — anyone who has it can forge signatures for geofenced tiles. If you build your app with React Native, review the React Native security guidance for ways to keep secrets out of your app bundle.