Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Current »

GET /payments

Verifies that the given paymentId exists in Club OS and you have access to it.  

GET https://api.club-os.com/payments?clubLocationId=[clubLocationId]&paymentId=[paymentId]

Parameters

The following fields must be included as parameters in the URL of the request.

 

VariableTypeDescription
clubLocationIdIntegerThe Club OS unique id for the club location you wish to access. Club OS will provide these to you.
paymentIdIntegerThe Club OS unique id for the payment you are requesting.

POST /payments

Add a payment to the system.

POST https://api.club-os.com/payments?clubLocationId=[clubLocationId]

Parameters

The following fields must be included as parameters in the URL of the request.

VariableTypeDescription
clubLocationIdIntegerThe Club OS unique id for the club location you wish to access. Club OS will provide these to you.
Request Body

The following fields must be included in the body of the HTTP request as a valid JSON string.

PropertyTypeRequiredDefaultDescription
memberIdIntegerY The Club OS unique id for the member who made the payment.
salespersonIdIntegerN The Club OS unique id for the salesperson who was responsible for the payment.
localPaymentIdStringY Your systems unique id for the payment.
clubServiceIdIntegerN The Club OS unique id for the club service that is being paid for. Use the /clubservices to get this id. Not required.
nameStringN The descriptive name of the product or service, i.e. 'Group Training', '30 Min Sessions', 'Multi-Vitamin'. Only required if no clubServiceId is used.
qtyDecimalY The qty purchased.
unitPriceDecimalY The unit price (cost of 1 item) of the product or service.
upcStringN The UPC for the product or service that was purchased.
taxesDecimalN The amount of taxes on the payment.
saleDateDate (M-d-YYYY)Y The date of the sale.
expireDateDate (M-d-YYYY)N The expiration date if one exists.
Response Messages

One of the following messages will be returned when the request succeeds.

MessageDescription
Payment CreatedPayment successfully created.
Payment FoundPayment exists in the system already.

 

POST /payments/batch

Add multiple payments to the system.

POST https://api.club-os.com/payments/batch?clubLocationId=[clubLocationId]

This method works identical to the above method, but the request body needs to be an array of payments, rather than a single payment.  Use this when there are multiple payments within a single order.

Note, if any payments in the batch fail, the entire batch will fail.  Validation errors will be returned for the first invalid payment.

 

  • No labels