Identity URLs

Optional. Specify the format of the returned output. Values are:

• json
• xml

The client can also specify the returned format in an accept-request header using one of the following formats.

• Accept: application/json
• Accept: application/xml
• Accept: application/x-www-form-urlencoded

The request header also supports the following.

• The */* wildcard is accepted and returns JSON.
• A list of values, which is checked left to right. For example: application/xml,application/json,application/html,*/* returns XML.

The format parameter takes precedence over the access request header.

Optional. Specify a valid JavaScript function name. You can use this parameter when the specified format is JSON. The output is wrapped in this function name (JSONP). For example, if a request to https://server/id/orgid/userid/ returns {"function":"name"}, a request to https://server/id/orgid/userid/?callback=baz returns baz({"function":"name"});.

Note JSONP is no longer returned for Identity Service requests due to strict MIME typing. Your requests must add 'format=jsonp' with the callback parameter so that the Identity Service returns JavaScript. When the Identity Service detects the JSONP format, it returns the required JavaScript type ('application/javascript').

Indicates whether the queried user’s email was verified by clicking a link in the “Welcome to Salesforce” email.

The email_verified value is set to true when users click a link in the email they receive after the following:For example, a Salesforce admin creates the user Roberta Smith. Roberta receives a “Welcome to Salesforce” email message with a link to verify her account. After she clicks the link, the email_verified value is set to true.

• They change their email address
• They change their password, or a Salesforce admin resets their password
• They verify their identity when logging in from a new device or browser
• A Salesforce admin creates them as a new user

Map of URLs to the queried user’s profile pictures, specified as picture or thumbnail.

Note Accessing these URLs requires passing an access token. See access token.

Queried user’s current Chatter status.

• created_date—xsd datetime value of the creation date of the last post by the user, for example, 2010-05-08T05:17:51.000Z.
• body—Body of the post.

Map containing various API endpoints that can be used with the queried user

Note Accessing the REST endpoints requires passing an access token. See access token.

• enterprise (SOAP)
• metadata (SOAP)
• partner (SOAP)
• rest (REST)
• sobjects (REST)
• search (REST)
• query (REST)
• recent (REST)
• profile
• feeds (Chatter)
• feed-items (Chatter)
• groups (Chatter)
• users (Chatter)
• custom_domain
  

  Note If the org doesn’t have a custom domain configured and propagated, this value is omitted.

Specific values for managing a mobile connected app. These values are available only when the connected app is installed in the current user’s org, the app has a defined session timeout value, and the mobile PIN has a length value defined.

• screen_lock—Length of time to wait to lock the screen after inactivity.
• pin_length—Length of the identification number required to gain access to the mobile app.

Set to apple if the connected app is registered with Apple Push Notification Service (APNS) for iOS push notifications. Set to androidGcm if it’s registered with Google Cloud Messaging (GCM) for Android push notifications.

The response value type is an array.

When a request includes the custom_permissions scope parameter, the response includes a map containing custom permissions in the org associated with the connected app. If the connected app isn’t installed in the org or has no associated custom permissions, the response doesn’t contain a custom_permissions map.

http://MyDomainName.my.salesforce.com/services/oauth2/authorize?response_type=token&client_
                    id=3MVG9lKcPoNINVBKV6EgVJiF.snSDwh6_2wSS7BrOhHGEJkC_&redirect_uri=http://www.example.org/qa/security/oauth
                    /useragent_flow_callback.jsp&scope=api%20id%20custom_permissions
                  

"custom_permissions":
                      {
                      "Email.View":true,
                      "Email.Create":false,
                      "Email.Delete":false
                      }