| 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 PersonSubscription entity, as the name implies, is the combination of a Person and a Subscription. This is what the end user usually simply refers to as a "Subscription" : Mr X. "has" a subscription. |
|
You can Add and Update PersonSubscriptions in your network by issuing a POST request to http://api.resengo.com/SUB/PersonSubscription.
The PersonSubscriptionIDs returned in the response should be saved in your database.
If possible, always use a PersonSubscriptionID when updating a PersonSubscription in the network. If you do not have a PersonSubscriptionID yet (because you are uploading the PersonSubscription for the first time) and you are sending multiple PersonSubscriptions at once, you can differentiate between the results by specifying a SMS_PersonSubscriptionID or SMS_PersonSubscription for each posted PersonSubscription. These should correspond to the primary key of your local database. Request to SUB/PersonSubscription (POST):
Fields of <PersonSubscription>:
Response of SUB/PersonSubscription (POST):
Fields of <PersonSubscription>:
|