search

mozvat / WSPAPIPrototype

Web Services 2.0 prototype work.
1 stars 2 forks source link

Product differentiation #1

Open mozvat opened 11 years ago

mozvat commented 11 years ago

Comment by Bobby Bonestell

I don’t like “api.mercurypay.com/payments/v1/credit” because it doesn’t differentiate which platform (HC, PWS, TWS, WS, etc).

The question: Is it important to differentiate the products through physical endpoints or can the documentation differentiate?

esear commented 11 years ago

I don't believe we need to differentiate products between endpoints/hostnames. I think any and all web services (APIs) that support mercury products should be exposed through a single hostname and naming structure.

I think this is especially true since we don't actually 'sell' these products - meaning, we would only give Developers access to a certain subset of APIs unless they paid for/bought that product. We should be able to adequately differentiate the APIs by the customer use cases and what they are trying to accomplish. For example... Building a POS to support a credit/debit transactions at a full service restaurant? use these [subset] services. Want to use Mercury Gift Cards? use these [subset] services Want to accept credit/debit cards on your website? use these [subset] services (i.e. hosted checkout)