For the complete documentation index, see llms.txt. This page is also available as Markdown.
Advanced customization
Extend Aparté ticket mapping, routing, and connector behavior when the default setup is not enough.
Why advanced customization matters
The default setup covers most Aparté projects. It works well when one pass template is enough.
Advanced customization is useful when ticket display or template routing needs more control.
Real-world examples
Multiple ticket families: use different pass templates for different ticket types.
Custom display rules: transform source values before showing them on the pass.
Specific routing: apply a different template based on ticket metadata.
Start simple first
A first rollout should stay simple. Start with the default pass type, validate the result, then add custom rules only when needed.
When extra data is needed, inspect the raw Aparté payload under debug.aparte.ticket. This confirms which fields are available before changing the pass design.
What can be customized
Advanced customization usually covers two areas.
Display rules: adjust how Aparté data appears on the pass.
Template routing: send some tickets to a different pass type.
The connector Default pass type remains the fallback when no custom rule selects another template.
Recommended rollout
Use this order to keep the setup easy to validate:
Start with one default pass type.
Check the source payload in debug.aparte.ticket.
Add small display rules if needed.
Add template routing only when one pass type is no longer enough.
Get help with advanced customization
Advanced customization can be reviewed with The Wallet Crew support team. This is useful when the right routing or mapping approach is not yet clear.
Support can help define the simplest rule set before implementation.
FAQ
Should every Aparté project use advanced mapping?
No. Most projects work well with the default setup and one pass type.
Where can the raw Aparté payload be inspected?
The full source payload is available under debug.aparte.ticket.
When should template routing be added?
Add routing when one default pass type no longer covers the ticket variants cleanly.
