# Obtain Signing Identity Information

# Alias

`SignIdentityReading`

# Description

Provides information on a signing identity.

# Request

`GET /trustedx-resources/esigp/v1/sign_identities/{sign_identity_id}`

## Parameters

Name | Type | Usage | Description
`sign_identity_id` | path | Required | Identifier of the signing identity information is being requested on.

## Authorization

The request must contain a bearer access token generated by a trusted authorization server of the service from which the information on the signing identity is requested and that is associated to the domain to which the identity belongs. This token must be used as explained in RFC 6750. It must have the `urn:safelayer:eidas:sign:identity:profile` or the `urn:safelayer:eidas:sign:identity:manage` scope or the registration scope of this type of identity (mobile or server) in the schema that the identity belongs to (e.g. `urn:safelayer:eidas:sign:identity:register`). Basically, the token must be included in an HTTP Authorization header as follows:

`Authorization: Bearer <token>`

The access token can be obtained via an authorization code grant or client credentials grant OAuth 2.0 flow.

## Example

`GET /trustedx-resources/esigp/v1/sign_identities/12345678 HTTP/1.1`
`Authorization: Bearer mF_9.B5f-4.1JqM`

# Response

## Status-Line

If the information is obtained successfully, the HTTP response will contain the following Status-Line (see HTTP Response Status for all the possible cases):

`HTTP/1.1 200 OK`

## Content-Type Header

`Content-Type: application/json;charset=UTF-8`

## Body

Signing identity on which information was requested.