20.3. PDND e-Service Template

The PDND provides a specialized tool that enhances API co-design processes by optimizing e-service publication and reuse. This functionality is defined in this document.

  • "Linee Guida sull'infrastruttura tecnologica della Piattaforma Digitale Nazionale Dati per l'interoperabilità dei sistemi informativi e delle basi di dati" (PDND).

The template e-service serves as a standardized blueprint containing all necessary technical and descriptive metadata for an e-service. API Managers, who can be either Providers or Consumers within the PDND ecosystem, MAY create and maintain these templates.

Once a template e-service is published, it is accessible through the PDND Template Catalog, a centralized repository that facilitates discovery and reuse. This catalog enables any authorized PDND Participant to browse available templates and instantiate new e-services based on existing designs.

20.3.1. PDND Template e-service definition and guidelines

The PDND infrastructure supports the lifecycle management of Template E-Services, similar to that of traditional e-services. The lifecycle states include: Draft, Active, Suspended, and Deprecated. As with traditional e-services, PDND enforces role-based access control to govern status transitions.

20.3.1.1. Templates e-service Management

20.3.1.1.1. Template E-Service Creation

Participants are enabled to create Templates E-Service via a guided wizard accessible through the PDND Web GUI (APIs will be available in the future). The creation workflow closely mirrors that of standard e-service creation, with the following distinctions:

  • An additional field identifies the intended recipient of the template.

  • The "Audience" field is omitted.

  • Thresholds are optional and serve as recommendations for Participants implementing the template.

Participants are prohibited from creating multiple templates with the same name: template names MUST be unique per participant. Upon creation, a template is initially set to the Draft state. Templates can then be published to the Template Catalog, thereby making them accessible to all Participants.

20.3.1.1.2. Template E-Service Modification

Participants who have created a template may edit it. The scope of editable fields depends on the template’s lifecycle state:

  • If the template is in Draft state, all fields are editable.

  • For templates in other states, only a restricted subset of fields can be modified directly.

  • Fields that cannot be modified in published templates require the creation of a new template version to apply changes.

Template versioning operates similarly to that of e-services, given that changes to the blueprint can impact instantiated services and then the Participants who consume that instance.

The following fields may be edited without triggering a new template version:

  • Name

  • Intended Recipient

  • Description

  • Voucher Time Limit

  • Documentation (excluding the OpenAPI specification)

  • Attributes

20.3.1.1.3. Template E-Service Suspension

Templates, like e-services, can be Suspended. When suspended:

  • The template is removed from the templates public catalog.

  • Instantiation of new instances from the suspended template is disabled.

  • Previously instantiated instances remain unaffected.

  • Templates may be reactivated at any time.

  • Templates cannot be deleted.

20.3.1.1.4. Template E-Service Instantiation

Participants MAY instantiate a Template E-Service by browsing the Template Catalog and selecting a template. This process generates a new e-service.

Instantiation constraints include:

  • Only templates in the Active state are eligible for instantiation.

  • The instantiation is facilitated through a guided wizard in the PDND Web GUI.

  • Due to the standardization objective of templates, most fields are pre-populated and immutable during instantiation.

  • The following information cannot be modified during instantiation:

    • Documentation upload

    • Token expiration time

    • Name, description, and attributes

Instead, the following fields must be specified during instantiation:

  • Audience

  • Thresholds

  • Automatic/Manual Approval Policy

Additionally, although the OpenAPI specification is fixed, the following metadata fields can be provided so that PDND can automatically update the YAML specification:

  • Contacts (name, email, URL, Terms and Conditions URL)

  • Server URLs

Each instantiated e-service maintains an independent lifecycle analogous to standard e-services.

20.3.1.2. Version Management

Template versioning follows a controlled process:

  • Publishing a new template version sets it to Active.

  • The previously Active version is automatically transitioned to Deprecated.

  • Only one Active version per template is allowed at any time.

  • Templates may also have a single Draft version coexisting with the Active version.

Instances derived from templates maintain independent versioning since Participants may update instance-specific fields (e.g., server URLs) multiple times, while the instance remains linked to the originating template version.

Consequently, template versions and instance versions are independent and not directly correlated.

Participants instantiating a template may then update either the specific instance or, if available, upgrade to a newer template version.

20.3.1.3. Authentic Source Template

The template e-service functionality is employed to standardize data transmission from Authentic Sources to Credential Issuers. The template e-service SHOULD be published within PDND by the Credential Issuer and is accessible through the PDND Template Catalog.

20.3.1.3.1. Authentic Source Template Parameters

The template e-service MUST adhere to the following specifications:

  • Name: IT Wallet - Authentic Source - <Credential name>

  • Intended Recipients: IT Wallet - Authentic Source - <Authentic Source domain>

  • Description: Description text useful to the Credential Issuer about the new Credential <Credential name>

  • Technology: REST

  • Data variation via Signal Hub: True

  • Version changelog: Authentic Source e-service via template implementation

  • Voucher Time Limit: 20

  • Suggest custom threshold: False

  • Suggest manual agreement approval policy: False

  • Attributes: <Offcial name of the Credential Issuer Public Authority>

20.3.1.3.2. Authentic Source Template Instantiation

Each Authentic Source SHOULD instantiate the IT Wallet - Authentic Source template e-service in PDND. The instantiation process will result in a new e-service that MUST satisfy the following requirements:

  • Signal Hub: True

  • Manual agreement approval policy: False

  • Daily API calls threshold for each provider: greater than 10000

  • Daily API calls threshold: greater than 10000

Additional information required during the creation process is provider-dependent.

20.3.1.3.3. Authentic Source PDND OpenAPI Specification

Below is the complete Open API Specification for the Authentic Source PDND e-services:

  1openapi: 3.0.1
  2info:
  3  title: IT Wallet API - AS web services
  4  version: 0.2.0
  5  description: IT Wallet Authentic Source e-Service exposed via PDND.
  6  termsOfService: "https://authentic-source.example.it/tos/"
  7  contact:
  8    name: IT-Wallet <credential_name> <credential_provider>
  9    url: https://github.com/italia/eid-wallet-it-docs
 10  x-api-id: ASITW-01
 11  x-summary: IT-Wallet Authentic Source API.
 12servers:
 13  - url: https://test.authentic-source.example.it/v0.2.0
 14    description: Authentic Source API test server
 15  - url: https://authentic-source.example.it/v0.2.0
 16    description: Authentic Source API production server
 17security:
 18  - BearerAuth: []
 19  - DPoPAuth: []
 20paths:
 21  /status:
 22    get:
 23      tags:
 24        - status
 25      summary: Get Authentic Source API status.
 26      description: Health-check endpoint that returns the operational status of the Authentic Source API.
 27      operationId: authenticSourceStatus
 28      responses:
 29        "200":
 30          description: Service available
 31          content:
 32            application/problem+json:
 33              schema:
 34                $ref: "#/components/schemas/ProblemDetails"
 35          headers:
 36            Cache-Control:
 37              $ref: "#/components/headers/CacheControlHeader"
 38            RateLimit-Limit:
 39              $ref: "#/components/headers/RateLimitLimitHeader"
 40            RateLimit-Remaining:
 41              $ref: "#/components/headers/RateLimitRemainingHeader"
 42            RateLimit-Reset:
 43              $ref: "#/components/headers/RateLimitResetHeader"
 44        "429":
 45          description: Too Many Requests
 46          content:
 47            application/problem+json:
 48              schema:
 49                $ref: "#/components/schemas/ProblemDetails"
 50          headers:
 51            RateLimit-Limit:
 52              $ref: "#/components/headers/RateLimitLimitHeader"
 53            RateLimit-Remaining:
 54              $ref: "#/components/headers/RateLimitRemainingHeader"
 55            RateLimit-Reset:
 56              $ref: "#/components/headers/RateLimitResetHeader"
 57        "503":
 58          description: Service Unavailable
 59          content:
 60            application/problem+json:
 61              schema:
 62                $ref: "#/components/schemas/ProblemDetails"
 63          headers:
 64            Retry-After:
 65              $ref: "#/components/headers/RetryAfterHeader"
 66
 67  /attribute-claims/{datasetId}:
 68    post:
 69      tags:
 70        - credential
 71      summary: Get Attribute Claims
 72      description: >-
 73        This service provides the Credential Issuer with all attribute claims necessary for the issuance of a Digital Credential
 74      operationId: attributeClaims
 75      parameters:
 76        - in: path
 77          name: datasetId
 78          schema:
 79            type: string
 80          required: true
 81          description: Identifier of the dataset as registered in the Authentic Source Registry
 82        - name: DPoP
 83          in: header
 84          description: Use only if the DPoP voucher has been requested from PDND.
 85          schema:
 86            type: string
 87            format: JWT
 88          required: false
 89        - name: Agid-JWT-Signature
 90          in: header
 91          description: >-
 92            JWT containing the signature of the message headers whose integrity
 93            needs to be guaranteed, to comply with the INTEGRITY_REST_02
 94            security pattern (see <a target="blank"
 95            href="https://italia.github.io/eid-wallet-it-docs/versione-corrente/en/e-service-pdnd.html">e-Service PDND</a>). <br/><br/>
 96
 97            <a target="blank" href="https://jwt.io/#debugger-io?token=eyJhbGciOiJFUzI1NiIsImtpZCI6ImQ0YzNiMmExLTk4NzYtNTQzMi0xMGZlLWRjYmE5ODc2NTQzMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI4MjkxNGIzZi02MGIyLTQ1MjktYjRkNi0zZDRlNjdmMGE5MzMiLCJzdWIiOiI4MjkxNGIzZi02MGIyLTQ1MjktYjRkNi0zZDRlNjdmMGE5MzMiLCJhdWQiOiJodHRwczovL2F1dGhlbnRpYy1zb3VyY2UuZXhhbXBsZS5pdCIsImlhdCI6MTczMzM5Nzg0MCwibmJmIjoxNzMzNDAxNjI4LCJleHAiOjE3MzM0MDE0NDAsImp0aSI6ImQzZjdiMmM5LTI3NGEtNDJiNy04ZjhkLTJlOWQ4YjE3MzRiMCIsInNpZ25lZF9oZWFkZXJzIjpbeyJkaWdlc3QiOiJTSEEtMjU2PTcyZTE4YmRkZGYxM2M5MTFiNGRkNTYyZWUyMTk3OWE1YzlmMjM1YzNhMDFiZDE0MjZlODU3ZDhjMWEyODJmNDEifSx7ImNvbnRlbnQtdHlwZSI6ImFwcGxpY2F0aW9uL2pzb24ifV19.tG5-P96CCA6N1IYC-xk4GumoVkA3NFolpbBn2vQ2e9vpWQ8f5Sm2l4-1VrXfKTx-CUVz_puiwqkBhulrNKj2fA">EXAMPLE
 98            ON JWT.IO</a>
 99          required: true
100          schema:
101            type: string
102            format: JWT
103            example: eyJhbGciOiJFUzI1NiIsImtpZCI6ImQ0YzNiMmExLTk4NzYtNTQzMi0xMGZlLWRjYmE5ODc2NTQzMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI4MjkxNGIzZi02MGIyLTQ1MjktYjRkNi0zZDRlNjdmMGE5MzMiLCJzdWIiOiI4MjkxNGIzZi02MGIyLTQ1MjktYjRkNi0zZDRlNjdmMGE5MzMiLCJhdWQiOiJodHRwczovL2F1dGhlbnRpYy1zb3VyY2UuZXhhbXBsZS5pdCIsImlhdCI6MTczMzM5Nzg0MCwibmJmIjoxNzMzNDAxNjI4LCJleHAiOjE3MzM0MDE0NDAsImp0aSI6ImQzZjdiMmM5LTI3NGEtNDJiNy04ZjhkLTJlOWQ4YjE3MzRiMCIsInNpZ25lZF9oZWFkZXJzIjpbeyJkaWdlc3QiOiJTSEEtMjU2PTcyZTE4YmRkZGYxM2M5MTFiNGRkNTYyZWUyMTk3OWE1YzlmMjM1YzNhMDFiZDE0MjZlODU3ZDhjMWEyODJmNDEifSx7ImNvbnRlbnQtdHlwZSI6ImFwcGxpY2F0aW9uL2pzb24ifV19.tG5-P96CCA6N1IYC-xk4GumoVkA3NFolpbBn2vQ2e9vpWQ8f5Sm2l4-1VrXfKTx-CUVz_puiwqkBhulrNKj2fA
104        - name: Digest
105          in: header
106          description: >-
107            Digest of the message payload, to comply with the INTEGRITY_REST_02
108            security pattern. According to <a target="blank" href="https://www.rfc-editor.org/rfc/rfc3230.html#section-4.2">RFC
109            3230 §4.2</a>, the format MUST be the following: digest-algorithm=encoded
110            digest output.
111          required: true
112          schema:
113            type: string
114            example: SHA-256=72e18bdddf13c911b4dd562ee21979a5c9f235c3a01bd1426e857d8c1a282f41
115        - name: Agid-JWT-TrackingEvidence
116          in: header
117          description: >-
118            If the Voucher type is Bearer, this header represents a JWT acting as a proof of possession, to comply with the REST_JWS_2021_POP security
119            pattern using the POP_TPoP implementation. Otherwise, it is a JWT containing the data tracked in the Consumer's domain, to comply with AUDIT_REST_02 (see <a target="blank"
120            href="https://italia.github.io/eid-wallet-it-docs/versione-corrente/en/e-service-pdnd.html">e-Service PDND</a>). <br/><br/>
121            <a target="blank" href="https://jwt.io/#debugger-io?token=eyJhbGciOiJFUzI1NiIsImtpZCI6ImQ0YzNiMmExLTk4NzYtNTQzMi0xMGZlLWRjYmE5ODc2NTQzMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI4MjkxNGIzZi02MGIyLTQ1MjktYjRkNi0zZDRlNjdmMGE5MzMiLCJhdWQiOiJodHRwczovL2F1dGhlbnRpYy1zb3VyY2UuZXhhbXBsZS5pdCIsImV4cCI6MTczMzA1MjYwMCwibmJmIjoxNzMzMDM2NDUwLCJpYXQiOjE3MzMwMzY0MDAsImp0aSI6ImE0YjVjNmQ3LWU4ZjktYWJjZC1lZjEyLTM0NTY3ODkwMTIzNCIsImRub25jZSI6NjUyODQyNDIxMzY4NSwicHVycG9zZUlkIjoiYjJjM2Q0ZTUtZjZnNy1oOGk5LWowazEtbG1ubzEyMzQ1Njc4IiwidXNlcklEIjoiYThiN2M2ZDUtZTRmMy1nMmgxLWk5ajAta2xtbm9wcXJzdHV2IiwibG9hIjoic3Vic3RhbnRpYWwifQ.y42yfMeW2H9h0b0j0BODUml8yF20stY9q3BwoVU5BB90afBj852Q0QlInncdhjXhUjLS1V76cGBxkutDNvxRNA">EXAMPLE
122            ON JWT.IO</a>
123          required: false
124          schema:
125            type: string
126            format: JWT
127            example: eyJhbGciOiJFUzI1NiIsImtpZCI6ImQ0YzNiMmExLTk4NzYtNTQzMi0xMGZlLWRjYmE5ODc2NTQzMiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI4MjkxNGIzZi02MGIyLTQ1MjktYjRkNi0zZDRlNjdmMGE5MzMiLCJhdWQiOiJodHRwczovL2F1dGhlbnRpYy1zb3VyY2UuZXhhbXBsZS5pdCIsImV4cCI6MTczMzA1MjYwMCwibmJmIjoxNzMzMDM2NDUwLCJpYXQiOjE3MzMwMzY0MDAsImp0aSI6ImE0YjVjNmQ3LWU4ZjktYWJjZC1lZjEyLTM0NTY3ODkwMTIzNCIsImRub25jZSI6NjUyODQyNDIxMzY4NSwicHVycG9zZUlkIjoiYjJjM2Q0ZTUtZjZnNy1oOGk5LWowazEtbG1ubzEyMzQ1Njc4IiwidXNlcklEIjoiYThiN2M2ZDUtZTRmMy1nMmgxLWk5ajAta2xtbm9wcXJzdHV2IiwibG9hIjoic3Vic3RhbnRpYWwifQ.y42yfMeW2H9h0b0j0BODUml8yF20stY9q3BwoVU5BB90afBj852Q0QlInncdhjXhUjLS1V76cGBxkutDNvxRNA
128      requestBody:
129        required: true
130        content:
131          application/json:
132            schema:
133              $ref: "#/components/schemas/CredentialClaimsRequest"
134      responses:
135        "200":
136          description: OK
137          headers:
138            Agid-JWT-Signature:
139              description: JWT containing the signature of the message headers whose integrity needs to be guaranteed, to comply with the INTEGRITY_REST_02 security pattern (see <a target="blank" href="https://italia.github.io/eid-wallet-it-docs/versione-corrente/en/e-service-pdnd.html">e-Service PDND</a>). <a target="blank" href="https://jwt.io/#debugger-io?token=ew0KICAiYWxnIjogIkVTMjU2IiwNCiAgImtpZCI6ICJhMWY1YzhkMi00YjM3LTRlOTEtYjBkMi03OWUzZjBjNGE4ZWYiLA0KICAidHlwIjogIkpXVCINCn0.ew0KICAiaXNzIjogIjEyMzRhYmNkLWVmNTYtZ2g3OC1pOWowLWtsbW5vcHFyc3R3eCIsDQogICJzdWIiOiAiMTIzNGFiY2QtZWY1Ni1naDc4LWk5ajAta2xtbm9wcXJzdHd4IiwNCiAgImF1ZCI6ICJodHRwczovL2ZydWl0b3JlLmV4YW1wbGUvZW50ZS1leGFtcGxlL3YxIiwNCiAgImlhdCI6IDE3MzMzOTc4NDAsDQogICJuYmYiOiAxNzMzNDAxNjI4LA0KICAiZXhwIjogMTczMzQwMTQ0MCwNCiAgImp0aSI6ICI4ZTEyZjRiNy05YzNhLTRmODMtOWI4ZC01MWEyYzdmNmU5ZDQiLA0KICAic2lnbmVkX2hlYWRlcnMiOiBbDQogICAgew0KICAgICAgImRpZ2VzdCI6ICJTSEEtMjU2PTc5YTIwYTc0NDMzNjQyMDMwMTgzMDYwMGFkOWJkY2E5OTM1OTNmODc2MjA5YTAwNGI1OTliNTgzMDk1YjBhNjEiDQogICAgfSwNCiAgICB7DQogICAgICAiY29udGVudC10eXBlIjogImFwcGxpY2F0aW9uL2pzb24iDQogICAgfQ0KICBdDQp9.DpuBNo2UgQhL7WLin4mpdZrbIpQq3tPvCX6HfktkxG7L5mk6a8OK1Hg0mQcZfFi3gelS-aL9kFS-6MoSy4csBg">EXAMPLE
140              required: true
141              schema:
142                type: string
143            Digest:
144              description: Digest of the message payload, to comply with the INTEGRITY_REST_02 security pattern. According to RFC 3230 Section 4.2 <a target="blank" href="https://www.rfc-editor.org/rfc/rfc3230.html#section-4.2">RFC 3230 §4.2</a>, the format MUST be the following digest-algorithm=encoded digest output.
145              required: true
146              schema:
147                type: string
148                example: SHA-256=79a20a744336420301830600ad9bdca993593f876209a004b599b583095b0a61
149            Cache-Control:
150              $ref: "#/components/headers/CacheControlHeader"
151            RateLimit-Limit:
152              $ref: "#/components/headers/RateLimitLimitHeader"
153            RateLimit-Remaining:
154              $ref: "#/components/headers/RateLimitRemainingHeader"
155            RateLimit-Reset:
156              $ref: "#/components/headers/RateLimitResetHeader"
157          content:
158            application/json:
159              schema:
160                $ref: "#/components/schemas/CredentialClaimsResponse"
161              example:
162                interval: 864000
163                userClaims:
164                  given_name: "Mario"
165                  family_name: "Rossi"
166                  birth_date: "1980-01-10"
167                  birth_place: "Roma"
168                  tax_id_code: "TINIT-RSSMRA80A01H501Z"
169                  personal_administrative_number: "12345A123A"
170                attributeClaims:
171                  - object_id: "6F9619FF-8B86-D011-B42D-00C04FC964FF"
172                    status: "VALID"
173                    last_updated: "2025-01-15T10:30:00Z"
174                    institute_name: "Nome Istituto Universitario"
175                    programme_type_name: "Laurea Magistrale"
176                    degree_course_name: "Computer Science - Informatica"
177                    academic_qualification_date: "2025-06-25"
178                  - object_id: "7A0720AB-9C97-E122-C53E-11D05FD075GG"
179                    status: "VALID"
180                    last_updated: "2025-01-10T08:00:00Z"
181                    institute_name: "Nome Istituto Universitario"
182                    programme_type_name: "Laurea Triennale"
183                    degree_course_name: "Informatica"
184                    academic_qualification_date: "2022-11-27"
185                metadataClaims:
186                  - object_id: "6F9619FF-8B86-D011-B42D-00C04FC964FF"
187                    issuance_date: "2025-06-25"
188                  - object_id: "7A0720AB-9C97-E122-C53E-11D05FD075GG"
189                    issuance_date: "2022-11-27"
190        "400":
191          description: Bad Request
192          content:
193            application/problem+json:
194              schema:
195                $ref: "#/components/schemas/ProblemDetails"
196          headers:
197            RateLimit-Limit:
198              $ref: "#/components/headers/RateLimitLimitHeader"
199            RateLimit-Remaining:
200              $ref: "#/components/headers/RateLimitRemainingHeader"
201            RateLimit-Reset:
202              $ref: "#/components/headers/RateLimitResetHeader"
203        "401":
204          description: Unauthorized
205          content:
206            application/problem+json:
207              schema:
208                $ref: "#/components/schemas/ProblemDetails"
209          headers:
210            RateLimit-Limit:
211              $ref: "#/components/headers/RateLimitLimitHeader"
212            RateLimit-Remaining:
213              $ref: "#/components/headers/RateLimitRemainingHeader"
214            RateLimit-Reset:
215              $ref: "#/components/headers/RateLimitResetHeader"
216            WWW-Authenticate:
217              $ref: "#/components/headers/WWWAuthenticateHeader"
218        "404":
219          description: Claims not found
220          content:
221            application/problem+json:
222              schema:
223                $ref: "#/components/schemas/ProblemDetails"
224          headers:
225            RateLimit-Limit:
226              $ref: "#/components/headers/RateLimitLimitHeader"
227            RateLimit-Remaining:
228              $ref: "#/components/headers/RateLimitRemainingHeader"
229            RateLimit-Reset:
230              $ref: "#/components/headers/RateLimitResetHeader"
231        "429":
232          description: Too Many Requests
233          content:
234            application/problem+json:
235              schema:
236                $ref: "#/components/schemas/ProblemDetails"
237          headers:
238            RateLimit-Limit:
239              $ref: "#/components/headers/RateLimitLimitHeader"
240            RateLimit-Remaining:
241              $ref: "#/components/headers/RateLimitRemainingHeader"
242            RateLimit-Reset:
243              $ref: "#/components/headers/RateLimitResetHeader"
244        "500":
245          description: Internal Server Error.
246          content:
247            application/problem+json:
248              schema:
249                $ref: "#/components/schemas/ProblemDetails"
250          headers:
251            Retry-After:
252              $ref: "#/components/headers/RetryAfterHeader"
253        "503":
254          description: Service Unavailable
255          content:
256            application/problem+json:
257              schema:
258                $ref: "#/components/schemas/ProblemDetails"
259          headers:
260            Retry-After:
261              $ref: "#/components/headers/RetryAfterHeader"
262
263tags:
264  - name: status
265    description: Endpoint di health check dell'API.
266  - name: credential
267    description: Retrieve information about the credential.
268
269components:
270  securitySchemes:
271    BearerAuth:
272      type: http
273      scheme: bearer
274      bearerFormat: JWT
275      description: PDND Bearer Token
276    DPoPAuth:
277      type: apiKey
278      in: header
279      name: DPoP
280      description: DPoP proof JWT (RFC 9449).
281
282  headers:
283    CacheControlHeader:
284      schema:
285        type: string
286        enum:
287          - no-store
288      description: no-store
289    RateLimitLimitHeader:
290      schema:
291        type: integer
292        format: int32
293        minimum: 0
294      description: Maximum number of requests within the time window.
295    RateLimitRemainingHeader:
296      schema:
297        type: integer
298        format: int32
299        minimum: 0
300      description: Remaining requests within the time window.
301    RateLimitResetHeader:
302      schema:
303        type: integer
304        format: int32
305        minimum: 0
306      description: UTC epoch in seconds, corresponding to when the window for the current rate limit will reset.
307    RetryAfterHeader:
308      schema:
309        type: integer
310        format: int32
311        minimum: 0
312      description: Seconds to wait before receiving another response.
313    WWWAuthenticateHeader:
314      schema:
315        type: string
316        example: >-
317          Bearer error="invalid_token", error_description="The access token expired"
318      description: The request cannot be fulfilled because the Voucher is expired, revoked or otherwise malformed. See <a target="blank" href="https://datatracker.ietf.org/doc/html/rfc6750.html#section-3">RFC6750</a> and <a target="blank" href="https://datatracker.ietf.org/doc/html/rfc9449.html#section-7.1-11">RFC9449</a> for details.
319
320  schemas:
321    CredentialClaimsResponse:
322      type: object
323      properties:
324        userClaims:
325          description: List of User Claims.
326          type: object
327          properties:
328            given_name:
329              description: Current First Name.
330              type: string
331              example: "Mario"
332            family_name:
333              description: Current Family Name.
334              type: string
335              example: "Rossi"
336            birth_date:
337              description: Date of Birth.
338              type: string
339              example: "1980-01-10"
340            birth_place:
341              description: Place of Birth.
342              type: string
343              example: "Roma"
344            tax_id_code:
345              description: National tax identification number. REQUIRED if personal_administrative_number is absent.
346              type: string
347              example: "TINIT-XXXXXXXXXXXXXXXX"
348            personal_administrative_number:
349              description: National unique identifier of a natural person. REQUIRED if tax_id_code is absent.
350              type: string
351              example: "XX00000XX"
352        attributeClaims:
353          description: List of Datasets of Attribute.
354          type: array
355          items:
356            type: object
357            properties:
358              object_id:
359                description: Unique identifier of the Dataset.
360                type: string
361                example: "6F9619FF-8B86-D011-B42D-00C04FC964FF"
362              status:
363                description: Status of the Dataset.
364                type: string
365                enum: ["VALID", "INVALID", "SUSPENDED"]
366                example: "VALID"
367              last_updated:
368                description: Last time the status or attributes of the Dataset have been updated. Its format is `YYYY-MM-DDTHH:MM:SSZ`.
369                type: string
370                example: "2025-01-15T10:30:00Z"
371            additionalProperties:
372              type: string
373            required: [object_id, status, last_updated]
374        metadataClaims:
375          description: List of Metadata Claims.
376          type: array
377          items:
378            type: object
379            properties:
380              object_id:
381                description: Unique identifier of the Dataset.
382                type: string
383                example: "6F9619FF-8B86-D011-B42D-00C04FC964FF"
384              issuance_date:
385                description: Administrative validity start date of the Dataset
386                type: string
387                example: "2025-01-01"
388              expiry_date:
389                description: Administrative expiry date of the Dataset.
390                type: string
391                example: "2025-12-31"
392            required: [object_id]
393        interval:
394          description: Required if claims parameter is not present. This represents the estimated amount of time (in seconds) required before making the request of the attribute claims again.
395          type: integer
396          format: int64
397          example: 864000
398    CredentialClaimsRequest:
399      required:
400        - unique_id
401      type: object
402      properties:
403        unique_id:
404          type: string
405          description: ID ANPR or Tax identification number
406        object_id:
407          type: string
408          description: Unique identifier of the Credential dataset or `jti` of the Agid-JWT-Signature Credential Issuer deferred flow's request. If this parameter is present only the indicated dataset is returned
409    ProblemDetails:
410      type: object
411      description: RFC7807-compliant problem details object for error responses.
412      properties:
413        type:
414          type: string
415          format: uri
416          description: An absolute URI that identifies the problem type.
417        title:
418          type: string
419          description: A short, human-readable summary of the problem type.
420        status:
421          type: integer
422          format: int32
423          description: The HTTP status code generated by the origin server for this occurrence of the problem.
424        detail:
425          type: string
426          description: A human-readable explanation specific to this occurrence of the problem.
427        instance:
428          type: string
429          format: uri
430          description: An absolute URI that identifies the specific occurrence of the problem.
431      required: [title, status, detail]