> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/api-reference/extensions.md). # Extensions Connector-specific endpoints that bridge The Wallet Crew with third-party platforms. Each extension exposes the webhook receivers, sync operations, and data-push endpoints that a specific integration needs. Extensions are enabled per-tenant and scoped to the connector they serve. Connector-specific endpoints that bridge The Wallet Crew with third-party platforms. Each extension exposes the webhook receivers, sync operations, and data-push endpoints that a specific integration needs. Extensions are enabled per-tenant and scoped to the connector they serve. ### Marketing automation #### Actito Receives pass creation and update triggers from Actito scenarios. Enables wallet pass issuance and push notifications to be orchestrated directly from Actito journeys. [Actito connector guide](https://docs.thewalletcrew.io/connectors/marketing-automation/actito) #### Klaviyo Accepts Klaviyo flow actions to create passes, trigger updates, and send push notifications. Events flow back to Klaviyo as profile properties and metric events for segmentation. [Klaviyo connector guide](https://docs.thewalletcrew.io/connectors/marketing-automation/klaviyo) #### SFMC (Salesforce Marketing Cloud) Exposes Journey Builder activity endpoints for pass updates and notifications. Also provides AMPscript helpers for generating authenticated pass links in Email Studio. [SFMC connector guide](https://docs.thewalletcrew.io/connectors/marketing-automation/salesforce-marketing-cloud) ### Loyalty and CRM #### Cegid Integrates with **Cegid Retail Y2** and **Cegid UR** POS systems. Receives customer and transaction webhooks from Cegid to keep wallet passes in sync with loyalty balances and member data. [Cegid connector guide](https://docs.thewalletcrew.io/connectors/pos/cegid) #### Comarch Connects Comarch loyalty programs to Apple Wallet and Google Wallet. Processes Kafka events and REST hooks from Comarch to update pass data in real time. [Comarch connector guide](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/comarch) ### Ticketing #### Secutix Distributes event tickets issued by Secutix as wallet passes. Handles ticket creation, updates, and invalidation through Secutix webhook notifications. [Secutix connector guide](https://docs.thewalletcrew.io/connectors/ticketing/secutix) #### Aparte Connects the Aparté (now Tick\&Live) ticketing platform to wallet pass delivery. Manages ticket-to-pass mapping, lifecycle updates, and multi-template routing. [Aparté connector guide](https://docs.thewalletcrew.io/connectors/ticketing/aparte) #### Yurplan Delivers Yurplan event tickets as wallet passes, with automatic sync from the Yurplan confirmation flow. [Yurplan connector guide](https://docs.thewalletcrew.io/connectors/ticketing/yurplan) ### Wallet platform #### ApplePass Apple Wallet device registration and push notification delivery endpoints. Called directly by Apple devices during pass installation, update checks, and uninstallation — these are part of the [Apple PassKit Web Service](https://developer.apple.com/documentation/walletpasses/adding_a_web_service_to_update_passes) protocol and must not be called by your integration. #### GooglePass Google Wallet JWT issuance and class management endpoints. Called during pass distribution and update flows for Google Wallet. ### Security #### Turnstile (Cloudflare) Validates Cloudflare Turnstile tokens on enrolment form submissions to block automated bots. The token is sent by the form client and verified server-side before the customer record is created. [Turnstile guide](https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/validation-rules/cloudflare-turnstile) ### Authentication Extension endpoints use the same `X-API-KEY` authentication as the rest of the API, but the required scopes are connector-specific. Webhook receiver endpoints may additionally validate an HMAC signature or a shared secret from the originating platform. ### Further reading * [Connectors overview](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors) * [Custom connectors guide](https://docs.thewalletcrew.io/developers-guides/integration-guides/custom-connectors) * [Marketing automation connectors](https://docs.thewalletcrew.io/connectors/marketing-automation) * [POS connectors](https://docs.thewalletcrew.io/connectors/pos) * [Ticketing connectors](https://docs.thewalletcrew.io/connectors/ticketing) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.thewalletcrew.io/api-reference/extensions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.