REST API: Performance's prices vs PerformancePrices

Former Member
Former Member $organization

The REST API exposes two methods that seem conceptually similar.

  • /Txn/Performances/Prices/
  • /Txn/PerformancePrices/

What is the difference between these resources, in terms of the Tessitura domain?  When is it best to use one over the other?

(x-post from http://developer.tessituranetwork.com/display/devportal/REST+API%3A+Performance%27s+prices+vs+PerformancePrices)



[edited by: Bryan Drenner at 9:54 AM (GMT -6) on 13 May 2014] fixed grammar and formatting
Parents
  • Normal 0 false false false EN-US X-NONE X-NONE

    I hope this explains it better:

    Txn/PerformancePrices is for maintenance of performance prices, like creating, updating, deleting performance prices.

     Txn/Performance/Prices is GET of prices for a set of performances that takes parameters like mode of sale, order datetime etc in consideration while calculating the current effective prices for those performances.

Reply
  • Normal 0 false false false EN-US X-NONE X-NONE

    I hope this explains it better:

    Txn/PerformancePrices is for maintenance of performance prices, like creating, updating, deleting performance prices.

     Txn/Performance/Prices is GET of prices for a set of performances that takes parameters like mode of sale, order datetime etc in consideration while calculating the current effective prices for those performances.

Children