Update a Transit pass

Pass updates are an important way to engage with your users after the pass is created. For example, by updating the balance of a user's card for a purchase made from your app.

To update the way passes are displayed, such as when the logo changes, you only need to update or patch the transit pass class or use the Google Pay and Wallet Console. Google propagates this information to every transit pass object associated to the updated transit pass class. This is the case for all fields defined at the transit pass class level.

To update a single pass, such as when the transit pass points balance changes, you need to update or patch a single transit pass object. This is the case for all fields defined at the transit pass object level.

Note:

Any update logic should begin with a GET request to retrieve the class or object. This ensures that the latest version of the class or object is used. Fields that you omit are cleared.

In general, it's much safer to use patch when you only supply data for the fields that you want to change. Fields that you omit aren't cleared. However, you should take extra care when you modify arrays. Patch requests that contain arrays also replace the existing array with the one you provide. You cannot modify, add, or delete items in an array in a piecemeal fashion.

Sometimes, you might not know when a change happens, or when to trigger an update or patch request. In cases like that, periodically schedule update or patch requests for each and every class and object. You can find all classes of a particular issuer account if you call the Transit class list method. You can find all objects of a particular class if you call the Transit object list method.