API Calls versus Active Passes



On a mission to help all businesses profit from passes.
Share on facebook
Share on twitter
Share on linkedin

Did you know that redeeming a Passbook Pass normally takes at least 2 API calls?

  1. To retrieve the status of the Pass (e.g. to check that the coupon is valid, or to confirm the balance of a store card is sufficient), and;
  2. The other to then change and update the status of the Pass (e.g. to change the coupon status to redeemed so it can’t be used again, or to subtract (or add) value to a store card when buying something or adding value to the Pass)

Depending on the API there could even be 2 separate calls to change change and then update the status.  PassKit’s API is designed so the particular scenarios described above will only be 2 calls.
But fortunately you don’t need to worry about any of that when using PassKit; you only pay for number of Actives Passes in devices. An Active Pass is defined as a pass that has been installed on a device and with updates switched on. If the Pass owner has turned off automatic updates then the Pass is not considered active until they switch it back on again or manually refresh the Pass.
With PassKit you can make unlimited number of API calls and updates to PassKit Passes at any time – so if someone chooses to use their store value card in your coffee shop 3 times a day you don’t have to worry about paying more.  You just pay for the Active Pass.
To join in the discussion on Active Passes and other helpful conversations about how to get the most out of Passbook and PassKit check out our forums or please go ahead and ask questions or leave comments below.

Join The Cause

Your subscription could not be saved. Please try again.
Your subscription has been successful.

Related Posts