The invitation page now displays when an invitation has been completed or a connection has been established via DIDComm.

The short URLs used to access the invitation pages for DIDComm verifications, DIDComm issuance, or DIDComm connections will no longer expire.

So they are now also usable for long term usage.

We're excited to introduce our new SD-JWT VC debugger, a powerful tool designed for developers working with Selective Disclosure JWT VCs (SD-JWT VCs).

This debugger enables you to:

• Decode SD-JWT VCs into a human-readable format
• Visualize the structure of SD-JWT VCs, including headers, payload, and disclosures
• Analyze the cryptographic components of SD-JWT VCs
• Experiment with selective disclosure by toggling individual claims

Whether you're a developer implementing SD-JWT VCs, or simply curious about the technology behind decentralized identity, this debugger helps you understand the workings of SD-JWT Verifiable Credentials.

Try it out now and let us know what you think!

The API reference got some great usability upgrades! When you are signed in, the projectId field will be automatically pre-filled with the projects available to you. Even when you switch endpoints in the API explorer, the projectId you selected will stay selected.

If you're using the API reference link on the credential and presentation template page, the current projectId will be selected, so you only have to care about copying the JSON payload.

Working with templates is now a lot easier with a new template overview screen. Here you can find everything you need to start using your template. It also shows an overview of all the activity related to your template.

The template overview has also gotten a refresh and now displays all your templates in a grid. You can quickly filter your templates by type, or using the search bar.

There's now a Paradym SDK for TypeScript! 🛠️⚡️ The Paradym API currently enables you to issue, verify, and revoke SD-JWT credentials over OpenID4VC as well as issue and verify AnonCreds credentials over DIDComm. Now you can choose to do all that with the SDK instead.

The SDK is available on npm and can be installed with npm install @paradym/sdk.

For detailed instructions on using the SDK, visit the Paradym SDK for TypeScript documentation page.

You can now issue and request presentation of SD-JWT VCs with nested attributes. This means you don't have to provide all properties top-level anymore, but you can define nested attributes such as user.firstName and address.streetName.

Usage of nested attributes is not supported for Anoncreds credentials and only available through the API for now. You can read more about using nested attributes in the docs.

We have redesigned the invitation page to make it more intuitive and user-friendly. It now includes the branding of the initiator. For example, didcomm invitations will display the branding of the invitation.

We have added support for DIDComm custom messages in the API. With this feature you are able to receive custom messages from agents and send custom messages to agents.

The following APIs and Events have been added:

• DIDComm Custom Messaging API
• DIDComm Custom Message Received Event

We have added support for DIDComm and AnonCreds to the new dashboard and API! In the dashboard you can now create Anoncreds credential and presentation templates, and the new DIDComm APIs allow you to issue, verify, connect and exchange basic messages. All features supported by the Workflow Builder are now available in the API.

The following APIs have been added:

• Anoncreds Credential Templates
• DIDComm Invitations
• DIDComm Connections
• DIDComm Issuance
• DIDComm Verification
• DIDComm Messaging

You can now revoke SD-JWT VCs, allowing you to invalidate a credential after is has been issued. To allow revocation on an SD-JWT VC, you must enable the revocable configuration option (in the dashboard or through the API). You can revoke a credential (or multiple) using the new Batch Revocation endpoint.

Direct issuance of SD-JWT VC

In addition to revocation for SD-JWT VCs, it's now also possible to directly issue an SD-JWT VC without using OpenID4VC as an exchange protocol. You can start issuing SD-JWT VCs directly using the new Issuance API.