REST Resource: partners.userSessions

Resource: UserSession

A user session contains a short-lived token that includes information required to interact with Google Payments Reseller Platform using the following web endpoints.

  • A user session token should be generated dynamically for an authenticated user. You should refrain from sharing a token directly with a user in an unauthenticated context, such as SMS, or email.
  • You can re-generate new session tokens repeatedly for same generate request if necessary, regardless of the previous tokens being expired or not. You don't need to worry about multiple sessions resulting in duplicate fulfillments as guaranteed by the same subscription id.

Please refer to the Google Managed Signup documentation for additional integration details.

JSON representation 
{
  "token": string,
  "expireTime": string
}
Fields
token

string

Output only. The encrypted token of the user session, including the information of the user's intent and request. This token should be provided when redirecting the user to Google.
expireTime

string (Timestamp format)

Output only. The time at which the user session expires.

A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".

Methods

generate

 This API replaces user authorized OAuth consent based APIs (Create, Entitle).