ceven

Passcreator

Issues digital wallet passes for Apple and Google Wallet based on customer events, updates pass details in real time, and tracks pass adoption across your user base.

Try Passcreator in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Passcreator integration

    • Describe the outcome and Ceven picks the right Passcreator calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Passcreator data, across all 11 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Passcreator access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Passcreator, when, and on whose behalf.
    • The agent pauses and asks when Passcreator is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Passcreator.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Passcreator action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Passcreator, and when to use it.

Check pass existence
Use this when verifying if a pass already exists for a specific external id before attempting to create a duplicate.
List passes
Pull a list of all issued passes using filters or paging to audit delivery rates.
Search passes
Query for specific passes based on user metadata or external identifiers.
List pass templates
Retrieve all available pass templates for your account to identify which design to use for a new campaign.
Create pass
Issue a new digital wallet pass to a customer using a specific template and user data.
Update pass
Change the fields or values on an existing pass, such as updating a loyalty balance or a seat number.
Delete pass
Revoke or remove a pass from the system when a membership expires or a ticket is canceled.
Get pass details
Pull the full configuration and current state of a single pass by its id.
Get template details
Pull the specific layout and field mapping for a single pass template.
Create template
Define a new pass layout and set of fields for a new type of wallet card.
Update template
Modify the design or default values of an existing pass template.
Delete template
Remove an obsolete pass template from the account.
List/Search Passes
Tool to list or search passes. use when you need to retrieve passes by filters or paging.

13 actions · scroll to see them all

Frequently asked questions

Ceven uses the Passcreator API to abstract the differences between the two platforms. When you trigger a create pass action, the agent sends the data to Passcreator, which then generates the appropriate file format for either Apple or Google. The agent can be told to issue both or just one depending on the customer device data stored in your CRM. Because Passcreator handles the actual signing of the Apple.pkpass files, Ceven only needs to manage the data payload. This means your workflow remains the same regardless of which wallet the end user prefers to use on their mobile device.
Yes. This is one of the strongest features of the integration. When Ceven calls the update pass action, Passcreator sends a push notification to the user device via the Apple or Google Wallet cloud services. The pass updates in the background, and the user sees the new information the next time they open their wallet. You can use this to change a ticket barcode, update a membership tier, or alert a customer that their coupon is about to expire. The agent manages the mapping between your internal user ID and the Passcreator external ID to ensure the right pass is updated.
Ceven is subject to the rate limits defined by your specific Passcreator subscription tier. Most standard plans have a limit on the number of API requests per minute. If your workflow triggers a massive batch of pass issuances, such as after a large email blast, Passcreator may return a 429 too many requests error. To handle this, Ceven implements an automatic retry logic with exponential backoff. However, for lists exceeding ten thousand passes, we recommend scheduling the workflow in smaller chunks to avoid hitting these hard API ceilings and ensuring smooth delivery to all users.
No. Ceven never stores the binary.pkpass files or the Google Wallet JSON objects. We only store the metadata and the external IDs required to reference the passes within Passcreator. When a user needs to access their pass, the agent provides the link generated by Passcreator, which redirects the user to the secure hosting environment provided by the vendor. This architecture ensures that sensitive cryptographic keys used to sign the passes remain exclusively within Passcreator and are never exposed to the workflow layer or the AI model.
You define the template logic within your Ceven workflow. For example, you can tell the agent to use the template named Loyalty Card for repeat customers and the template named Welcome Discount for first time buyers. The agent uses the list pass templates action to find the correct template ID associated with those names. If you change a template name in Passcreator, you will need to update the name in your workflow prompt or mapping so the agent can continue to find the correct ID for issuance.
Ceven can track the delivery and issuance status through the Passcreator API, but it cannot see real time open events inside the Apple or Google Wallet apps due to privacy restrictions imposed by Apple and Google. However, you can track when the pass link was first clicked or when the pass was successfully generated. To track actual usage, you should use the scan event from your point of sale system, which Ceven can then ingest to mark the pass as used or to trigger a follow up thank you message.
If a user deletes a pass from their wallet, Passcreator is not always notified immediately because the wallet apps do not always send a deletion webhook. However, if you try to update a pass that has been deleted, the pass will simply remain updated in the cloud. If the user decides to re add the pass using the original link, the most recent version of the data will be downloaded. Ceven continues to manage the pass state in Passcreator regardless of whether it is currently installed on a physical device.
Yes. You first define the custom fields within the Passcreator template editor. Once the fields are defined, Ceven can populate them using the update pass or create pass actions. The agent treats these as key value pairs. For example, if you have a custom field for Member Since, the agent can pull the join date from your database and push it into that specific field. This allows for a high level of personalization, ensuring that each digital card feels unique to the individual customer.

Alternatives to Passcreator

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

PassKit logoPassKitWalletly logoWalletlyAirship logoAirship

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Passcreator and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free