This is school-side infrastructure, not part of your integration. Ticketmaster is one of the systems participating schools run. Wishbone delivers completed donations into it on the school's behalf. Banks always call the same Wishbone endpoints with the same payload regardless of which platform a school uses — this page just shows where the money lands and what
school_confirmation_id refers to.Integration
POST https://app.ticketmaster.com/partners/v2/accounts/{account_id}/creditsWishbone → Ticketmaster
Wishbone issues a points-funded account credit through Ticketmaster's Partner API, applied to the fan's Ticketmaster account for use across the school's athletics events — no parallel wallet, no manual reconciliation.
View Docs ↗Bank App
Credit request
Wishbone
Validate & authorize
Ticketmaster
POST account credit
School CRM
Step 1
Bank submits POST /v1/donations/request. Wishbone creates a pending credit record.
Step 2
Wishbone validates the school and resolves the school's Ticketmaster partner account from encrypted config.
Step 3
Wishbone POSTs a credit instruction with the fan's account_id, amount, and an optional attraction/venue scope.
Step 4
Ticketmaster returns credit_id and status. Wishbone marks the donation completed and fires the webhook to the bank.
Request Body
Response
◎
Fire a request to see the response
What Wishbone does with the response
Store the Ticketmaster credit_id and status, mark the donation 'completed', and fire the donation.completed webhook to the bank. The credit lands on the fan's existing Ticketmaster account — ready to spend on the next home game.