developer.amazon.com Open in urlscan Pro
44.215.137.210  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Stornieren
Clear

SearchLoading

Anmelden
?
 * Support
 * Dokumentation
 * Contact Us

Anmelden
 * Home
 * Documentation
   
    * Login With Amazon for Android/Fire apps
    * Login With Amazon for IOS apps
    * Login With Amazon for Websites
    * Login With Amazon for TVs, Gaming, Other device
    * Style Guidelines
    * Button Guidelines
    * Solution-Providers
    * FAQ
    * Glossary

 * Login with Amazon Console

 * Support
   
    * Support
    * Dokumentation
    * Contact Us


Vielen Dank für deinen Besuch. Diese Seite ist nur in Englisch verfügbar.

No results found

Try a different or more specific query.
Clear

SearchLoading

Login with Amazon (LWA)

Collapse All | Expand All

 * Login with Amazon Overview
   * Documentation Overview
   * Release Notes
   * Frequently Asked Questions
   * Glossary
 * LWA for Websites
   * LWA for Websites Overview
   * Step 1: Register your Website
   * Step 2: Add a LWA Button
   * Step 3: Add the LWA SDK for JavaScript
   * Step 4: Implement Authorization Code Grant
   * Step 5: Dynamically Redirect Users
   * Step 6: Obtain Customer Profile Information
   * Step 7: Log out Users
   * Step 8: Integrate with your Existing Account System
   * Reference LWA SDK Docs for JavaScript
   * Requesting Scopes as Essential/Voluntary
 * LWA for iOS Apps
   * Login with Amazon for iOS Apps Overview
   * Customer Experience in iOS Apps
   * Step 1: Install the SDK for iOS
   * Step 2: Run the Sample app
   * Step 3: Register your iOS app with LWA
   * Step 4: Create a LWA Project
   * Step 5: Add a LWA Button to your App
   * Step 6: Use the SDK for iOS APIs
   * Step 7: Integrate with your Existing Account System
   * Reference SDK Docs for LWA iOS
   * Login with Amazon SDK for iOS 3.0.x Migration Guide
   * Login with Amazon SDK for iOS 3.1.x Migration Guide
 * LWA for Android and Fire Apps
   * LWA for Android and Fire Apps Overview
   * Customer Experience in Android and Fire Apps
   * Step 1: Install the SDK for Android
   * Step 2: Run the Sample app
   * Step 3: Register your Android/Fire app
   * Step 4: Create a LWA Project
   * Step 5: Add a LWA Button to your app
   * Step 6: Use the SDK for Android APIs
   * Step 7: Integrate with your Existing Account System
   * Reference LWA SDK Docs for Android
   * Login with Amazon SDK for Android 3.x Migration Guide
 * LWA for TVs and Other Devices
   * LWA for TVs and Other Devices Overview
   * Step 1: Register your Application
   * Step 2: Retrieve a User Code and Verification URL
   * Step 3: Display the User Code and Verification URL
   * Step 4: Retrieve an Access Token and Refresh Token
   * Step 5: Obtain Customer Profile Information
   * Step 6: Log out Users
   * Step 7: Integrate with your Existing Account System
 * Understanding LWA
   * LWA Conceptual Overview
   * Access Tokens
   * Authorization Code
   * Refresh Tokens
   * Customer Profile
   * Authorization Grants
   * Security Profile
   * Essential/Voluntary Scopes
 * Security Considerations
   * Cross-site Request Forgery
   * Impersonating a Resource Owner
   * Open Redirectors
   * Code Injections
   * Risks for Using WebView for Mobile Applications
 * Resources for Buttons, Styles, Providers
   * Button Guidelines
   * Style Guidelines
   * Solution Providers
   * Plugins
 * Older Documentation
   * Implicit Grant (Deprecated)
   * Choose an Authorization Grant
   * Use the Login with Amazon SDK for Android APIs (v2.0.2 and below)
   * Use the Login with Amazon SDK for iOS APIs (v2.1.2 and below)

--------------------------------------------------------------------------------

Other Resources
 * LWA Product Overview
 * LWA Forums
 * Amazon Blogs with LWA tags
 * Fire TV
 * Catalog Integration
 * Fire Tablets
 * Appstore Submission
 * App Testing
 * Revenue Reports and Promotions
 * Policy Center
 * Fling SDK
 * In-App Purchasing API
 * Submit Your Apps


OBTAIN CUSTOMER PROFILE INFORMATION


 LWA FOR WEBSITES

STEP 1:
Register for LWA
→
STEP 2:
Add a LWA Button to Your Website
→
STEP 3:
Add the LWA SDK for JavaScript
→
STEP 4:
Implement Authorization Code Grant
→
STEP 5:
Dynamically Redirect Users
→
STEP 6:
Obtain Customer Profile Info
→
STEP 7:
Log Out Users
→
STEP 8:
Integrate with Your Account System

After the user grants your website access to their Amazon customer profile, you
will receive an access token. If you're using server-side scripting to request
an access token via the Authorization Code Grant, the access token is returned
in the access token response.

If you're on a Browser-Based app, and need the access token on the client side,
you can set options.pkce = true and call the retrieveToken API with the
authorization code to get the access token. For the API to work, the client
needs to have cookies enabled and the authorize call must be on the same domain
as the retrieveToken call. To access the authorized customer data, you submit
that access token to Login with Amazon using HTTPS.

In response, Login with Amazon will return the appropriate customer profile
data. The profile data you receive is determined by the scope you specified when
requesting access. The access token reflects access permission for that scope.

 * Use the Login with Amazon SDK for JavaScript
 * Call the profile Endpoint Server-side
 * Customer Profile Response
 * Get Customer Information to your Server


USE THE LOGIN WITH AMAZON SDK FOR JAVASCRIPT

If you are using the Login with Amazon SDK for JavaScript, use
amazon.Login.retrieveProfile to exchange an access token for a profile. For
example:

<script type="text/javascript">
    document.getElementById('LoginWithAmazon').onclick = function() {
       setTimeout(window.doLogin, l);
       return false;
    };
    window.doLogin = function() {
        options = {};
        options.scope = 'profile';
        options.pkce = true;
        amazon.Login.authorize(options, function(response) {
            if ( response.error ) {
                alert('oauth error ' + response.error);
            return;
            }
            amazon.Login.retrieveToken(response.code, function(response) {
                if ( response.error ) {
                    alert('oauth error ' + response.error);
                return;
                }
                amazon.Login.retrieveProfile(response.access_token, function(response) {
                    alert('Hello, ' + response.profile.Name);
                    alert('Your e-mail address is ' + response.profile.PrimaryEmail);
                    alert('Your unique ID is ' + response.profile.CustomerId);
                    if ( window.console && window.console.log )
                       window.console.log(response);
                });
            });
        });
   };
 </script>


The amazon.Login.retrieveProfile function returns three parameters: success,
error, and profile. success indicates whether the call was successful. error
contains an error message if an error occurred. If there was no error, profile
contains the user's profile. For more information on this method and its
parameters, see the Login with Amazon SDK for JavaScript Reference.

Tip: If you would like to use the Login with Amazon SDK for JavaScript to
request a customer profile, you must first have your page load the Login with
Amazon SDK for JavaScript.


CALL THE PROFILE ENDPOINT SERVER-SIDE

If you are calling the profile endpoint directly, you can specify the access
token in one of three ways: as a query parameter, as a bearer token, or using
x-amz-access-token in the HTTP header. For example:

https://api.amazon.com/user/profile?access_token=AtzaIIQEBLjAsAhRmHjNgHpi0UDme37rR6CuUpSR...


GET /user/profile HTTP/1.1
Host: api.amazon.com
Date: Wed, 0l Jun 20ll l2:00:00 GMT
Authorization: Bearer Atza|IQEBLjAsAhRmHjNgHpi0U-Dme37rR6CuUpSR...


GET /user/profile HTTP/1.1
Host: api.amazon.com
Date: Wed, 0l Jun 20ll l2:00:00 GMT
x-amz-access-token: Atza|IQEBLjAsAhRmHjNgHpi0U-Dme37rR6CuUpSR...


Tip: Access tokens contain characters that are outside the allowed range for
URLs. Therefore, you should URL encode access tokens to prevent errors. For more
information, see jackson-databind 2.13.3 API.

Login with Amazon only supports application/json as a content type and en-us as
a content language. Login with Amazon uses this content type and language by
default, even if they are not specified.

GET /user/profile HTTP/1.1
Host: api.amazon.com
Date: Wed, 0l Jun 20ll l2:00:00 GMT
x-amz-access-token: Atza|IQEBLjAsAhRmHjNgHpi0U-Dme37rR6CuUpSR...
Accept: application/json
Accept-Language: en-US


Detailed code samples are available in the following languages:

 * PHP
 * Python
 * Java
 * Ruby

PHP Sample

In your server-side application, handle the request made to /handle_login.php,
and obtain profile information using the access token and the Profile REST API.
If you use the following code sample, replace YOUR-CLIENT-ID with the Client ID
you obtained when you registered your application.

// verify that the access token belongs to us
$c = curl_init('https://api.amazon.com/auth/o2/tokeninfo?access_token=' . urlencode($_REQUEST['access_token']));
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);

$r = curl_exec($c);
curl_close($c);
$d = json_decode($r);

if ($d->aud != 'YOUR-CLIENT-ID') {
  // the access token does not belong to us
  header('HTTP/1.1 404 Not Found');
  echo 'Page not found';
  exit;
}

// exchange the access token for user profile
$c = curl_init('https://api.amazon.com/user/profile');
curl_setopt($c, CURLOPT_HTTPHEADER, array('Authorization: bearer ' . $_REQUEST['access_token']));
curl_setopt($c, CURLOPT_RETURNTRANSFER, true);

$r = curl_exec($c);
curl_close($c);
$d = json_decode($r);

echo sprintf('%s %s %s', $d->name, $d->email, $d->user_id);


Ruby sample

In your server-side application, handle the request made to /handle_login.php,
and obtain profile information using the access token and the Profile REST API.
If you use the following code sample, replace YOUR-CLIENT-ID with the Client ID
you obtained when you registered your application.

require "rubygems"
require "net/https"
require "json"
require "uri"

...

# verify that the access token belongs to us
uri = URI.parse("https://api.amazon.com/auth/o2/tokeninfo?access_token=" + URI.encode(access_token))
req = Net::HTTP::Get.new(uri.request_uri)
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_PEER

response = http.request(req)
decode = JSON.parse(response.body)

if decode['aud'] != 'YOUR-CLIENT-ID'
# the access token does not belong to us
raise "Invalid token"
end

# exchange the access token for user profile
uri = URI.parse("https://api.amazon.com/user/profile")
req = Net::HTTP::Get.new(uri.request_uri)
req['Authorization'] = "bearer " + access_token
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
http.verify_mode = OpenSSL::SSL::VERIFY_PEER

response = http.request(req)
decode = JSON.parse(response.body)

puts sprintf "%s %s %s", decode['name'], decode['email'], decode['user_id']


Java sample

In your server-side application, handle the request made to /handle_login.php,
and obtain profile information using the access token and the Profile REST API.
If you use the following code sample, replace YOUR-CLIENT-ID with the Client ID
you obtained when you registered your application.

Note: You must download the Jackson and HttpComponents libraries to use this
sample code.

import com.fasterxml.jackson.core.type.TypeReference;
import com.fasterxml.jackson.databind.ObjectMapper;
import org.apache.http.client.fluent.Content;
import org.apache.http.client.fluent.Request;
import java.net.URLEncoder;
import java.util.Map;

...

// verify that the access token belongs to us
Content c = Request.Get("https://api.amazon.com/auth/o2/tokeninfo?access_token=" + URLEncoder.encode(access_token, "UTF-8"))
               .execute()
               .returnContent();

Map m = new ObjectMapper().readValue(c.toString(), new TypeReference>(){});

if (!"YOUR-CLIENT-ID".equals(m.get("aud"))) {
// the access token does not belong to us
throw new RuntimeException("Invalid token");
}

// exchange the access token for user profile
c = Request.Get("https://api.amazon.com/user/profile")
       .addHeader("Authorization", "bearer " + access_token)
       .execute()
       .returnContent();

m = new ObjectMapper().readValue(c.toString(), new TypeReference>(){});

System.out.println(String.format("%s %s %s", m.get("name"), m.get("email"), m.get("user_id")));


Python sample

In your server-side application, handle the request made to /handle_login.php,
and obtain profile information using the access token and the Profile REST API.
If you use the following code sample, replace YOUR-CLIENT-ID with the Client ID
you obtained when you registered your application.

Note: You must download the pycurl library to use this sample code.

import pycurl
import urllib
import json
import StringIO

...

b = StringIO.StringIO()

# verify that the access token belongs to us
c = pycurl.Curl()
c.setopt(pycurl.URL, "https://api.amazon.com/auth/o2/tokeninfo?access_token=" + urllib.quote_plus(access_token))
c.setopt(pycurl.SSL_VERIFYPEER, 1)
c.setopt(pycurl.WRITEFUNCTION, b.write)

c.perform()
d = json.loads(b.getvalue())

if d['aud'] != 'YOUR-CLIENT-ID' :
# the access token does not belong to us
raise BaseException("Invalid Token")

# exchange the access token for user profile
b = StringIO.StringIO()

c = pycurl.Curl()
c.setopt(pycurl.URL, "https://api.amazon.com/user/profile")
c.setopt(pycurl.HTTPHEADER, ["Authorization: bearer " + access_token])
c.setopt(pycurl.SSL_VERIFYPEER, 1)
c.setopt(pycurl.WRITEFUNCTION, b.write)

c.perform()
d = json.loads(b.getvalue())

print "%s %s %s"%(d['name'], d['email'], d['user_id'])



CUSTOMER PROFILE RESPONSE

If your access token is valid, you will receive the customer's profile data as
an HTTP response in JSON. For example:

HTTP/1.1 200 OK
 x-amzn-RequestId: 0f6bef6d-705c-lle2-aacb-93e6bf26930l
 Content-Type: application/json
 Content-Language: en-US
 Content-Length: 85
 {
    "user_id": "amznl.account.K2LI23KL2LK2",
    "email":"mhashimoto-04@plaxo.com",
    "name" :"Mork Hashimoto",
    "postal_code": "98052"
 }


The Request-Id is for logging and can be ignored. If you are troubleshooting an
issue with the Login with Amazon team you may be asked to supply the Request-Id.

If there is a problem fulfilling your profile request, you will receive an HTTP
error. The error codes for an access request include:

Status Error code Description 200 Success The request was successful. 400
invalid_request The request is missing a required parameter or otherwise
malformed. 400 invalid_token The access token provided is expired, revoked,
malformed, or invalid for other reasons. 401 insufficient_scope The access token
provided does not have access to the required scope. 500 ServerError The server
encountered a runtime error.

In addition to the error code, you may receive a JSON payload with more
information. For example:

HTTP/1.1 400 Bad Request
Content-Type: application/json;charset=UTF-8
Content-Length: 74
{
"error": "machine-readable error code",
"error_description": "human-readable error description",
"request_id": "bef0c2f8-e292-4l96-8c95-8833fbd559df"
}



GET CUSTOMER INFORMATION TO YOUR SERVER

You can get customer profile information obtained from Amazon on your backend
server to identify the signed-in user on your server, or to create a more
personalized account for the user. To do so securely, send the access token from
your client to your server using HTTPS. Then, from server-side, call the profile
endpoint using that access token. See Call the profile endpoint server-side for
details and code samples in multiple languages. Login with Amazon will return a
customer profile response with values (such as user_id, email, name, and/or
postal_code) you can keep on your server.

Taking this step will ensure the profile data you save to your server belongs to
the customer who is signed into your client. See our guide on Integrating with
your Existing Account System for more information on combining and managing user
accounts in your backend.


Zurück zum Seitenanfang


TERMS & AGREEMENTS

 * App Distribution Agreement
 * Program Materials License Agreement
 * Mobile Ad Network Publisher Agreement
 * Mobile Ad Network Program Participation Requirements
 * Trademark Guidelines
 * Terms of Use
 * Alexa Voice Service Agreement


AMAZON APPSTORE

 * Amazon Fire TV
 * Fire Tablets
 * Fire OS & Android
 * Cross-Platform Engines


ALEXA

 * Alexa Skills Kit
 * Alexa Voice Service
 * Alexa Fund
 * Amazon Tap


SERVICES & APIS

 * Amazon Fling SDK
 * App Testing Service
 * App Submission API
 * Device Messaging
 * In-App Purchasing
 * Live App Testing
 * Login with Amazon
 * Merch by Amazon
 * Mobile Ads


BLOGS

 * Amazon Developer Blog
 * AWS Blog


SUPPORT

 * Amazon Developer Support
 * Forums
 * FAQs

Language
German (Deutsch)
 * English
 * Chinese (中文)
 * Japanese (日本語)
 * German (Deutsch)
 * French (Français)
 * Italian (Italiano)
 * Spanish (España)
 * Spanish (México)
 * Portuguese (Brasil)

Folgen Sie uns:

Alexa
Amazon Appstore
Amazon Web Services
© 2010-2024, Amazon.com, Inc. und Tochtergesellschaften. Alle Rechte
vorbehalten.