Cancellation via API - Can it be done?

Hi Menno,

Are you talking about returning and refunding an order through the client, TNEW or the API?

There's not a "cancel order" button, per se.  Many if not most Tessitura-using orgs tend to be very limited in their refund offerings.  We allow exchanges to subscribers, and have only recently been offering refunds at all beyond show cancellations.  Also, every organization is likely to have a different idea about what exactly a refund should entail (e.g. one lineitem, the whole order?  Are fees refunded?  If so, which ones?).  You notice I'm talking about refunds, not cancellation.  A standard ticket order in Tessitura is not a process that can be interrupted.  You push the button, your money is transferred, and your reservation is set.  There's no time period wherein the fulfillment of your order is yet to occur after placement, even if you are distributing physical tickets, they are merely tokens of the reservation you already have.

Since there's no agreed-upon method for how refunds are processed, they are necessarily manual: seats must be released, fees must be overridden, and finally a new payment action applied to the new balance, which typically is going to involve sending a new request to the payment processor which includes a reference number from the original payment..  This is handled by multiple separate steps in the client.  There is no built-in system in TNEW.  The API...if you're looking for a process there I'll have to refer you someone else I'm afraid.  If you are doing a lot of Tessitura API work, you should look into getting an account on the developer's slack channel as well (although this is also a perfectly good place to ask questions).

Hi Menno,

Are you talking about returning and refunding an order through the client, TNEW or the API?

There's not a "cancel order" button, per se.  Many if not most Tessitura-using orgs tend to be very limited in their refund offerings.  We allow exchanges to subscribers, and have only recently been offering refunds at all beyond show cancellations.  Also, every organization is likely to have a different idea about what exactly a refund should entail (e.g. one lineitem, the whole order?  Are fees refunded?  If so, which ones?).  You notice I'm talking about refunds, not cancellation.  A standard ticket order in Tessitura is not a process that can be interrupted.  You push the button, your money is transferred, and your reservation is set.  There's no time period wherein the fulfillment of your order is yet to occur after placement, even if you are distributing physical tickets, they are merely tokens of the reservation you already have.

Since there's no agreed-upon method for how refunds are processed, they are necessarily manual: seats must be released, fees must be overridden, and finally a new payment action applied to the new balance, which typically is going to involve sending a new request to the payment processor which includes a reference number from the original payment..  This is handled by multiple separate steps in the client.  There is no built-in system in TNEW.  The API...if you're looking for a process there I'll have to refer you someone else I'm afraid.  If you are doing a lot of Tessitura API work, you should look into getting an account on the developer's slack channel as well (although this is also a perfectly good place to ask questions).