> For the complete documentation index, see [llms.txt](https://esignature.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://esignature.govstack.global/7-data-structures.md).
# 7 Data Structures
## 7.1 Data Elements
### 7.1.1 eSignature operation
| Name | Type | Description |
| ------------------ | --------- | ------------------------------------------------------------------------------------------------------------ |
| SignatureId | String | Unique Signature Token for signature operations. This can be a random String as well. |
| SignatureType | Enum | Can be ONETIME or SCD |
| SignatureFormat | Enum | Signature format that should be applied. Can be XAdES, CAdES, ASIC, JWS, PAdES |
| Hash | String | Hash to be signed in hex characters or base64 |
| HashType | Enum | Hash type - SHA2-256, SHA2-384, SHA2-512, SHA3-256, SHA3-384, SHA3-512, BLAKE2B |
| DisplayData | String | Text string to be shown on user’s device (SCD). Limited to 256 characters. |
| Certificate | String | X509 Certificate in PEM format |
| RequestTimestamp | Timestamp | Timestamp of the request |
| Signature | Signature | Signature in base64 format |
| SignatureTimestamp | String | rfc3161 asn.1 in base64 |
| ResponseTimestmap | Timestamp | Timestamp of the response |
| Status | Enum | Request status enum. Can be OK, ERROR |
| StatusDesc | String | Description of status |
| CallbackURL | URL | URL to call back with results |
| Pseudonym | String | Unique pseudonym for the user that is bound to the specific SCD/Key id combo. We can call this as Key Handle |
### 7.1.2 eSignature operation header
| Name | Type | Description |
| ------------ | ------ | -------------------------------------- |
| AuthToken | String | JWT Token from ID Building Block |
| PaymentToken | String | Jwt Token from Payments Building Block |
### 7.1.3 User's Device Onboarding
| Name | Type | Description |
| ----------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AuthToken | String | JWT Token from ID Building Block |
| PaymentToken | String | JWT Token from Payments Building Block |
| CSR | String | Certificate signing request PKCS#10 in PEM format |
| SCDType | Enum | The SCD type that is used by user. Can be of REMOTE\_SCD\_APP\_APPLE, REMOTE\_SCD\_APP\_ANDROID, REMOTE\_SCD\_APP\_SE\_APPLE, REMOTE\_SCD\_APP\_SE\_ANDROID, REMOTE\_SCD\_SIM, REMOTE\_SCD\_ESIM,
REMOTE\_SCD\_SMARTID
|
| SCDKeyId | Number | Key id for case the SCD has multiple certificates |
| SCDRemoteId | String | Remote identifier for the SCD communication, for REMOTE\_SCD\_APP\* devices it is push ID, for REMOTE\_SCD\_ESIM/ REMOTE\_SCD\_SIM it is msisdn
For
REMOTE\_SCD\_SMARTID it is citizen id
|
| Pseudonym | String | Unique pseudonym for the user that is bound to the specific SCD/Key id combo. We can call this as Key Handle |
| CertReqTimestamp | Timestamp | Timestamp for the certificate request |
| CertId | String | Unique identifier for the certificate, SCD, Key id combo |
| Certificate | String | X509 Certificate in PEM format in ACTIVE status |
| CertRespTimestamp | Timestamp | Timestamp for the Certificate response |
| Status | Enum | Request status. Can be of of OK, ERROR |
| StatusDesc | String | Description of status |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://esignature.govstack.global/7-data-structures.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.