| Security |
| Xml or Json ? |
| C# example: a HTTP GET request |
| Validation Errors |
| Module | Entity |
|---|---|
| FI | Transaction |
| PL | Person |
| RES | PartnerReservation |
| RES | PartnerReservationContacts |
| RES | PartnerReservations |
| SUB | PersonSubscription |
| SUB | Subscription |
| SUB | SubscriptionTransaction |
| WS | Order |
| WS | OrderItem |
|
The SubscriptionTransaction entities describe the movement of credits to and from a PersonSubscription.
The total value of all SubscriptionTransactions for any PersonSubscription is the amount of credits left on that PersonSubscription.
Do not confuse with FI/Transaction, which are payments with money.
|
|
You can Add and Update SubscriptionTransactions in your network by issuing a POST request to http://api.resengo.com/SUB/SubscriptionTransaction.
The SubscriptionTransactionIDs returned in the response should be saved in your database.
If possible, always use a SubscriptionTransactionID when updating a SubscriptionTransaction in the network. If you do not have a SubscriptionTransactionID yet (because you are uploading the SubscriptionTransaction for the first time) and you are sending multiple SubscriptionTransactions at once, you can differentiate between the results by specifying a SMS_SubscriptionTransactionID or SMS_SubscriptionTransaction for each posted SubscriptionTransaction. These should correspond to the primary key of your local database. Request to SUB/SubscriptionTransaction (POST):
Fields of <SubscriptionTransaction>:
Documentation on fields is not yet available.
Response of SUB/SubscriptionTransaction (POST):
Fields of <SubscriptionTransaction>:
Documentation on fields is not yet available.
|