From ePrize Developers Wiki
(Difference between revisions)
|
m |
| (14 intermediate revisions not shown.) |
Current revision
New to HelloWorld Web Services? Read this first: Getting Started
HelloWorld Web Services API uses a REST architecture for communication between your client and the HelloWorld servers. This is the same architecture used by the web, so you can explore the API with a web browser. While exploring the API, its basic features become clear:
- All URLs represent resources available to you. URLs are never actions.
- All actions on resources are basic HTTP methods such as GET, POST and PUT.
- All responses to your actions use basic HTTP status codes such as "200 OK" and "400 Bad Request".
- All responses include information on sub-resources and actions that may be performed.
- All responses use simple, regular media types that can be easily processed.
- All GET and PUT actions are idempotent; POST actions are not.
These features come at a cost however: the API consists of very small building blocks that do not directly provide the promotion services you expect in an HelloWorld promotion. For example, game plays are not automatically awarded upon login—there isn't even a login call! If you want to build clients using these more specific promotion features, you must use a client library. A library assembles the small building blocks into bigger features that you can reuse when building your promotion.
It is important to note that all communication to and from the HelloWorld Web Services API uses UTF-8 encoding.
It is important to note that the HTTP verb OPTIONS for CORS is not currently supported by default. Please reach out to your HelloWorld contact if you require this functionality
HelloWorld Web Services API
