API Home Page

From ePrize Developers Wiki

(Difference between revisions)
Jump to: navigation, search
Line 68: Line 68:
|-
|-
| [[Award sweepstakes entry]]
| [[Award sweepstakes entry]]
-
| POST /v1/{apikey}/game/{game}/sweeps
+
| POST /v1/{apikey}/game/{gameid}/sweeps
|
|
|-
|-
| [[Award token|Award instant win token]]
| [[Award token|Award instant win token]]
-
| POST /v1/{apikey}/game/{game}/tokens
+
| POST /v1/{apikey}/game/{gameid}/tokens
|
|
|-
|-
| [[Fetch token]]
| [[Fetch token]]
-
| GET /v1/{apikey}/game/{game}/token/{token}
+
| GET /v1/{apikey}/game/{gameid}/token/{tokenid}
|
|
|-
|-
| [[Redeem token]]
| [[Redeem token]]
-
| POST /v1/{apikey}/game/{game}/token/{token}
+
| POST /v1/{apikey}/game/{gameid}/token/{tokenid}
|
|
|-
|-
| [[Fetch prize]]
| [[Fetch prize]]
-
| GET /v1/{apikey}/game/{game}/prize/{prize}
+
| GET /v1/{apikey}/game/{gameid}/prize/{prizeid}
|
|
|-
|-

Revision as of 16:32, 17 June 2009

EPrize_API.gif

ePrize Web Services API uses a REST architecture for communication between your client and the ePrize 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 ePrize 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.

ePrize Web Services API

API Request/Response

API Security

API Events and Logging

Promotions

Fetch promotions GET /v1

Profiles

Create profile POST /v1/{apikey}/profiles
Fetch profile by key GET /v1/{apikey}/profile({key})/{value}
Fetch profile GET /v1/{apikey}/profile/{uid}
Fetch unredeemed tokens GET /v1/{apikey}/profile/{uid}/tokens
Fetch awards GET /v1/{apikey}/profile/{uid}/awards

Games and Awards

Fetch games GET /v1/{apikey}/games
Award sweepstakes entry POST /v1/{apikey}/game/{gameid}/sweeps
Award instant win token POST /v1/{apikey}/game/{gameid}/tokens
Fetch token GET /v1/{apikey}/game/{gameid}/token/{tokenid}
Redeem token POST /v1/{apikey}/game/{gameid}/token/{tokenid}
Fetch prize GET /v1/{apikey}/game/{gameid}/prize/{prizeid}

Mail

Send email POST /v1/{apikey}/email/{template-id}

CAPTCHA

Create CAPTCHA challenge POST /v1/{apikey}/captcha
Fetch CAPTCHA challenge GET /v1/{apikey}/captcha/{challenge-id}

API Debugging

Output communication test GET /v1/{apikey}/test/communication
Input communication test POST /v1/{apikey}/test/communication
Input URL communication test PUT /v1/{apikey}/test/communication/{value}
Error response test PUT /v1/{apikey}/test/communication

ePrize Promotion Client Libraries

Retrieved from "https://code.helloworld.com/wiki/index.php/API_Home_Page"
Personal tools