Contents x
GetCallerIdentity (GET)
    • Print
    • Dark
      Light
    Contents

    GetCallerIdentity (GET)

      • Print
      • Dark
        Light
      Article summary

      Get
      /#/GetCallerIdentity

      Availability

      Early Access: July 1, 2026

      Early Access is gated; contact the Backblaze Sales team for access.

      Limited Availability: July 1, 2026

      This API is available only to customers with access to the Backblaze Enterprise Web Console. For more information, contact the Backblaze Sales team.

      Return details about the credentials used to call the API

      Actual request: GET /?Action=GetCallerIdentity&Version=2011-06-15 to sts.backblazeb2.com.

      Request parameters

      ParameterTypeRequiredDescription
      ActionstringyesGetCallerIdentity
      Versionstringyes2011-06-15

      Example response

       <GetCallerIdentityResponse xmlns="https://sts.amazonaws.com/doc/2011-06-15/">
  <GetCallerIdentityResult>
    <UserId>AROAEXAMPLE123456789:session-001</UserId>
    <Account>123456789012</Account>
    <Arn>arn:aws:sts::123456789012:assumed-role/analytics-role/session-001</Arn>
  </GetCallerIdentityResult>
  <ResponseMetadata>
    <RequestId>req-1234567890</RequestId>
  </ResponseMetadata>
</GetCallerIdentityResponse>

      Errors

      • AccessDenied
      • ValidationError
      Security
      API Key: sigv4
      Header parameter nameAuthorization

      AWS Signature Version 4. The Authorization header takes the form AWS4-HMAC-SHA256 Credential=..., SignedHeaders=..., Signature=.... For IAM and STS requests, the signing region is not validated; use any non-empty region value consistently. The signing service must be iam for IAM requests and sts for STS requests. When using temporary credentials, also include X-Amz-Security-Token: <session-token>.

      Query parameters
      Action
      stringRequired

      API operation name.

      Version
      stringRequired

      STS API version.

      Valid values[ "2011-06-15" ]
      Default"2011-06-15"
      Responses
      200

      The request succeeded. The response body is an XML document specific to the Action invoked, with a ResponseMetadata block containing a RequestId.

      string

      Action-specific XML response. See the example response for each operation.

      400

      The request was malformed or failed validation.

      HTTP StatusCodeDescription
      400ValidationErrorInvalid input parameter or failed validation.
      string
      403

      The caller is not authorized. For operations that reference IAM resources, authorization may be evaluated before resource existence is disclosed.

      HTTP StatusCodeDescription
      403AccessDeniedThe authenticated principal lacks permission for this action.
      string
      429

      The request was rate-limited.

      HTTP StatusCodeDescription
      429ThrottlingToo many requests. Use exponential backoff.
      string
      500

      The server encountered an unexpected condition.

      HTTP StatusCodeDescription
      500InternalFailureUnexpected server error.
      string
      Was this article helpful?
      What's Next