Skip to main content
When configuring custom integration operations, you can use dynamic values to automatically insert real-time data into your API requests. These values are replaced at runtime with actual player information, ticket context, dates, and more. Dynamic values follow the format {{category.field}} and can be used in operation parameters, headers, and URLs.

​
Player Data

Access information stored on the player record:
ValueDescription
{{contact.email}}Player email
{{contact.firstName}}First name
{{contact.lastName}}Last name
{{contact.phone}}Phone number
{{contact.customAttributes.X}}Any custom attribute (replace X with attribute name)
Custom attributes are workspace-specific fields stored on player records. Common examples:
  • {{contact.customAttributes.sessionId}} - Session identifier
  • {{contact.customAttributes.vipLevel}} - Player tier

​
Ticket Data

Access current support ticket context:
ValueDescription
{{supportTicket.id}}Ticket ID
{{supportTicket.humanId}}Human-readable ticket number

​
Workspace Data

Access workspace configuration:
ValueDescription
{{workspace.companyName}}Workspace name
{{workspace.boApiUrl}}Back-office API base URL

​
Brand Data

Access brand-specific values (useful for multi-brand setups):
ValueDescription
{{brand.slug}}Brand identifier (configurable per brand in Settings → Brands → Advanced Configuration)
{{brand.apiDomain}}Custom API domain for this brand
Multi-brand example: Configure a single operation with a dynamic URL: 
https://{{brand.apiDomain}}/api/v1/player/balance
The system substitutes the current brand’s domain automatically, so the same operation works across all your brands.

​
Date Values

Generate timestamps relative to the current time. Respects workspace timezone.
ValueResult
{{date.today}}Current date/time
{{date.yesterday}}1 day ago
{{date.tomorrow}}1 day ahead
{{date.7dAgo}}7 days ago
{{date.30dAgo}}30 days ago
{{date.NdAgo}}N days ago (any number)

​
Date Formatting

Add format modifiers for different output formats:
ValueResult
{{date.today}}2025-01-15T14:30:00.000Z (ISO with timezone)
{{date.today|format:'YYYY-MM-DD'}}2025-01-15
{{date.today|format:'noZ'}}2025-01-15T14:30:00 (no timezone)
{{date.today|format:'unix'}}1736952600 (seconds)
{{date.today|format:'unixMs'}}1736952600000 (milliseconds)

​
Operation Parameters

Use {{param.paramName}} to place parameter values directly into the URL path. This is useful for building RESTful URLs: Example: Transaction lookup operation
  • URL: https://api.example.com/transactions/{{param.transactionId}}
  • Parameter: transactionId - The transaction ID to look up
Parameters used in the URL path are automatically removed from the query string or request body, so the same value won’t be sent twice. If your API requires the same value in both the path and query string, create a second parameter with a different name.

​
Fallbacks and Defaults

Values support fallback chains and default values: 
{{contact.email|contact.customAttributes.email|default:'unknown'}}
This tries contact.email first, then contact.customAttributes.email, then falls back to the literal string 'unknown'.