Overview
Push Integration
→
→
→
Overview
In the Prime Gaming push integration, your services will link a customer's Amazon ID to a game or platform ID that you control. Whenever a customer claims one of your Prime Gaming offers, Prime Gaming's web services will call an API on your systems to fulfill the newly created entitlement to your game's content. (An "entitlement" is the receipt or proof of a user's entitlement to a digital good. "Fulfillment" is the process of delivering that digital good.)
Push integrations require a little more up-front work than pull integrations in exchange for a more efficient live service. Your fulfillment API is called just once per claim; in a pull integration, your service needs to repeatedly poll a Prime Gaming endpoint for entitlements. The Login with Amazon (LWA) account linking process is similar to a pull integration's, but with one additional Prime Gaming API call per account link.
Since entitlements are "pushed" to your service as they're claimed, you also have more flexibility in handling fulfillments. While players should still be able to access their content as soon as possible after a claim, push integrations naturally lend themselves to asynchronous processes and queueing solutions. These often lead to a more optimized workflow.
Prerequisites
The following things are required to implement a Prime Gaming push integration:
- A web backend or game server for your title(s) that can be updated with your own code, make external API calls, accept authenticated external traffic, and add new content to a player's account or inventory
- An account or profile system that can uniquely identify your players
- A data or persistence layer, such as a database, where you can save additional metadata for your players and each of your Prime Gaming offers
- Experience creating web APIs that meet an existing API specification
- Basic working knowledge of the OAuth 2.0 specification, especially Authorization Code Grants, for account linking via Login with Amazon (LWA)
User Flow
