The Google Photos Library API contains multiple scopes used to access media items and albums. The responses returned from various calls are different based on which scopes have been requested by the developer.
Every request your application sends to the Google Photos Library API must include an authorization token. The token also identifies your application to Google.
About authorization protocols
Authorizing requests with OAuth 2.0
All requests to the Google Photos Library API must be authorized by an authenticated user.
The details of the authorization process, or "flow," for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:
- When you create your application, you register it using the Google API Console. Google then provides information you'll need later, such as a client ID and a client secret.
- Activate the Google Photos Library API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)
- When your application needs access to user data, it asks Google for a particular scope of access.
- Google displays a consent screen to the user, asking them to authorize your application to request some of their data.
- If the user approves, then Google gives your application a short-lived access token.
- Your application requests user data, attaching the access token to the request.
- If Google determines that your request and the token are valid, it returns the requested data.
Some flows include additional steps, such as using refresh tokens to acquire new access tokens. For detailed information about flows for various types of applications, see Google's OAuth 2.0 documentation.
Here's the OAuth 2.0 scope information for the Google Photos Library API:
List items from the library and all albums, access all media items and list albums owned by the user, including those which have been shared with them.
For albums shared by the user, share properties
are only returned if
For more information, see Share media.
Access to upload bytes, create media items, create albums, and add enrichments. Only allows new media to be created in the user's library and in albums created by the app.
Intended to be requested together with the
Edit access only.
Access to change these details for albums and media items created by the developer:
Access to create an album, share it, upload media items to it, and join a shared album.
Not recommended. Only request access to the scopes you need with incremental authorization.
Access to both the
To request access using OAuth 2.0, your application needs the scope information, as well as information that Google supplies when you register your application (such as the client ID and the client secret).
Tip: The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the page with libraries and samples for more details.
As a general rule, choose the most restrictive scope possible and avoid requesting scopes that your app does not need. Users more readily grant access to limited, clearly described scopes. Users may hesitate to grant broad access to their media unless they trust your app and understand why it needs the information.
Incrementally requesting scopes
Following best practices for authorization, your application should only request scopes as they are needed. Avoid requesting all scopes for your application up-front at sign-in. Instead, provide justification and make the request in context. Clearly explain what you will do with your users' data and how they will benefit by granting access, as per the UX Guidelines and best practices to provide notice and ask for consent.
The Library API does not support service accounts. Your application must use the other OAuth 2.0 flows available such as OAuth 2.0 for web server applications or OAuth 2.0 for mobile and desktop apps.