> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/intro/issuer_data.md).

# Issuer Data Description

This document explains the details available in the **Issuer Details** section of the One-Click Deployment dashboard. An Issuer is identified by a **Decentralized Identifier (DID)** that the service creates and hosts itself. Every action described here is performed against the Issuer's API using a valid admin **Bearer (JWT)** token in the `Authorization` header.

***

## Issuer Details

When you select an Issuer from the dashboard, you are taken to a detailed view organized into the following information and tabs.

### General Information

* **id:** The Issuer's identifier, which is its Decentralized Identifier (DID) — for example `did:web:example-name.evdi.app:<uuid>` or `did:key:...`. This is the same DID shown in the full DID document below; the deployment's unique id is the `<uuid>` embedded in the `did:web` path.
* **fullHost:** The base URL where the Issuer service is accessible (for example, `https://example-name.evdi.app`). The Issuer's interactive OpenAPI documentation is served from this host at `/api-docs` (the raw OpenAPI JSON is available at `/api-docs-json`).
* **status:** The current deployment status of the Issuer (for example, `ACTIVE`, `PENDING`, `INIT`, `UPGRADE`, `FAILED`).
* **version:** The deployed version of the Issuer's configuration.
* **networkName:** The deployment-environment selector for this Issuer. Its value comes from `{MAINNET, TESTNET}`; it names the environment the deployment runs in, not an on-chain network the Issuer uses.
* **issuerDomainName:** The subdomain label chosen for the deployment (for example, `example-name-issuer`).
* **issuerName:** The name assigned to the Issuer during creation.
* **swaggerApi:** The URL of the interactive API docs, served from `fullHost` at `/api-docs`.
* **adminGuiUrl:** The URL of the operator console (Issuer Admin) for this deployment.

### Cryptographic Information

* **didDocument:** A JSON object describing the Issuer's DID. For a `did:web` identity, the service hosts this document publicly at `/:uuid/did.json` (also reachable at `/:uuid/.well-known/did.json`), so wallets and verifiers can resolve the Issuer's keys over HTTPS. It includes:
  * **id:** The DID identifier (for example, `did:web:example-name.evdi.app:<uuid>`).
  * **@context:** The JSON-LD contexts for the document, including the DID v1 context and the Ed25519 2018 signature suite context.
  * **verificationMethod:** The Issuer's signing keys. Each entry uses an **Ed25519** key (`type: "Ed25519VerificationKey2018"`), with an **id**, a **controller** (the DID that controls the key), and a **publicKeyBase58** (Base58-encoded Ed25519 public key).

***

## Issuer Tabs (Operator Console)

On an Issuer's detail page in the **operator console**, the following tabs are available (the portal's own deployment view exposes separate operational tabs such as Details, Service Accounts, Logs, Backups, Domain Linking, Keycloak Config, Instruction, and Actions):

* **Schemas:** View the schemas assigned to this Issuer, assign published schema versions, and issue credentials from them via each version's **Issue credential** action. Assigning a schema version makes its credential configuration ids (such as `EmployeeBadge@1:sd-jwt`) available to offers. Schemas themselves are defined and versioned on the separate **Schemas** screen.
* **Issuance Sessions:** Track issuance sessions (Session ID, State, Created/Expires). Open a session's dashboard to re-display its offer QR code, copy the `openid-credential-offer://` URL, or claim the credential straight into a cloud wallet. New offers are created from the **Schemas** tab's Issue credential action.
* **DID Config:** The Issuer's OpenID4VCI metadata document (served under `.well-known/did-configuration`), which describes the credentials the Issuer can offer.
* **DID Document:** The full DID document in JSON, as served from the Issuer's hosted `did.json`.

High-impact operations are available from the deployment's header on the dashboard rather than as a tab.

***

## Actions

1. **Upgrade Version:**
   * Upgrade the Issuer to a newer version.
2. **Delete:**
   * Permanently remove the Issuer from the system.

To rotate the deployment's admin credentials, use the Keycloak admin console (the Realm Admin URL shown when the deployment was created) — see [Authenticating to Your Deployment](/develop/intro/authenticating-to-your-deployment.md).

***

## Example View

Here is an example of an Issuer's details as displayed on the dashboard:

```plaintext
issuerId: did:web:example-name.evdi.app:646941a4-1d89-60e7-d66e-6afddccb7a68
issuerName: example-name-issuer
fullHost: https://example-name.evdi.app
swaggerApi: https://example-name.evdi.app/api-docs
status: ACTIVE
version: 0.0.4
networkName: TESTNET

didDocument:
{
  "id": "did:web:example-name.evdi.app:646941a4-1d89-60e7-d66e-6afddccb7a68",
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/suites/ed25519-2018/v1"
  ],
  "verificationMethod": [
    {
      "id": "did:web:example-name.evdi.app:646941a4-1d89-60e7-d66e-6afddccb7a68#key-1",
      "type": "Ed25519VerificationKey2018",
      "controller": "did:web:example-name.evdi.app:646941a4-1d89-60e7-d66e-6afddccb7a68",
      "publicKeyBase58": "<base58-encoded-public-key>"
    }
  ],
  "authentication": [
    "did:web:example-name.evdi.app:646941a4-1d89-60e7-d66e-6afddccb7a68#key-1"
  ],
  "assertionMethod": [
    "did:web:example-name.evdi.app:646941a4-1d89-60e7-d66e-6afddccb7a68#key-1"
  ]
}
```

<figure><img src="/files/q0x6fzdbTPKOeTEhFcRz" alt="Issuer Details in the One-Click portal"><figcaption><p>Deployment details in the One-Click portal (Issuer Details): Full Host, Swagger Api, Admin Gui Url, and status</p></figcaption></figure>


---

# 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://docs.empe.io/develop/intro/issuer_data.md?ask=<question>&goal=<endgoal>
```

`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.