Differences from Play Store API
Our goal is to make the app submission API simple and easy to use. If you have implemented the submission API for the Google Play store, you need to make only a few changes to be compatible with the Amazon Appstore app submission API.
Feature Differences
| Feature | Google Play API | App Submission API | Comments |
|---|---|---|---|
| Edit sync between API and Console |
N/A | Yes | When you update the open Edit using the API, these updates are visible in the Developer Console. |
| Device Targeting | N/A | Yes | Selecting the types of devices that can use this app. |
| HTTP PATCH | Yes | No | You use PATCH to make partial updates to an entity (PUT updates the entire entity). |
| LAT (Live App Testing) | Yes | No | You cannot use the API to create or update the LAT version of your app. |
Comparison of API Resource Types
For comparison purposes, see the Play Store API Edits reference.
The API methods use the following resources in the requests and responses.
| Resource | Play Store API | App Submission API | Comments |
|---|---|---|---|
| Edits |
{
"id": string,
"expiryTimeSeconds": string
}
|
{
"id": string
}
|
Amazon Edits do not expire |
| Edits.details |
{
"defaultLanguage": string,
"contactWebsite": string,
"contactEmail": string,
"contactPhone": string
}
|
Same fields as Play Store API | No differences |
| Edits.listings |
{
"language": string,
"title": string,
"fullDescription": string,
"shortDescription": string,
"video": string
}
|
{
"language": string,
"title": string,
"fullDescription": string,
"shortDescription": string,
"videos": string[]
}
|
Appstore parameter is a list of videos. |
| Edits.images |
{
"images": [
{
"id": string,
"url": string,
"sha1": string
}
]
}
|
{
"images": [
{
"id": string
}
]
|
Appstore does not use url or sha1 parameter |
| Edits.apks |
{
"versionCode": integer,
"binary": {
"sha1": string,
"sha256": string
}
}
|
{
"versionCode": integer,
"binary": {
"id": string,
"name": string
}
|
Appstore has no sha1 or sha256 fields, and adds two new fields. |
| Edits.targeting | n/a |
{
targeting: {
[ "device": string,
"status": string ]
}
}
|
New endpoint for Appstore |
Play Store API supports additional resources (such as testers and tracks) that the Appstore currently does not support.
Comparison of API Methods
| Resource | Play Store API | App Submission API | Comments |
|---|---|---|---|
| Edits |
commit delete get insert validate |
commit delete get insert validate |
Same methods |
| Edits.details |
get patch update |
get – update |
Amazon API does not support Patch |
| Edits.listings |
list delete get patch update |
list delete get – update |
Amazon API does not support Patch |
| Edits.images |
list delete deleteall upload |
list delete deleteall upload |
Amazon API methods support images and videos |
| Edits.listings |
list delete deleteall get patch update |
list delete – get – update |
Amazon API does not support Delete All or Patch |
| Edits.apks |
addexternallyhosted list upload – – – |
– list upload get delete replace |
|
| Edits.availability | n/a |
get put |
New endpoint for Appstore |
| Edits.targeting | n/a |
get modify |
New endpoint for Appstore |
| Edits. apkInjectionChoice |
n/a |
get put |
New endpoint for Appstore |
Play Store API supports additional API methods (for resources such as as testers, tracks, bundles, and in-app purchases) that the Amazon Appstore currently does not support.