This document explains how to integrate Gataca’s SSI Credential Verification Service into your infrastructure. The integration enables your system to verify Verifiable Credentials (VCs) in compliance with W3C DID and Verifiable Credentials standards.
Target Audience
Developers, solution architects, and system administrators responsible for integration.
Ensure compliance with international SSI standards for trusted verification.
Enhance trust by confirming data authenticity and integrity.
Enable decentralized and privacy-preserving credential verification.
Streamline user experiences with fast and secure verification processes.
Prerequisites
Internet access to consume the exposed APIs over HTTPS.
Ports: 443 (TLS/SSL).
Integration Workflow
The following steps outline the workflow for credential verification:
The client sends a credential verification request to the API.
The API validates the request and processes the data.
The backend verifier verifies the data exchanged.
Sequence Diagram
The diagram below illustrates the SSI authentication flow. This documentation will only focus on the steps relevant to the integration process.
User Wallet: Gataca Wallet
Relying Party App (also known as a service provider): refers to the web or mobile application that requires authentication from a user - this is your organization.
Connect: Verifier component in Gataca Studio
API Endpoints
Detailed API endpoint documentation (including request/response formats, parameters, and error codes) is provided in the Swagger documentation.
Step-by-Step Integration Guide
Initial Configuration
1. Generate API Key
Log in to the Gataca Studio portaland generate an API key, ensuring it is linked to a specific Verification Template if required. Once the API key is successfully generated, click the Save button to confirm the configuration.
2. Obtain API Key Credentials
After generating the API key, the associated credentials will be displayed. Store this information securely, as it will be required for authenticating requests to the platform. Note that the credentials may not be retrievable again.
Authentication
3. Obtain an Access Token
Use the platform’s login endpoint to retrieve an Access Token. This token is required to authenticate and authorize all protected operations within the system. Make sure to securely store the token for subsequent API requests.
API-KEY-CREDENTIALS: base64(api-key id:api-key secret) - You must provide the API Key ID (UUID) and secret given when creating the API Key in Studio, encoded in base64 format in the HTTP request header.
TENANT: A tenant is a logical instance that isolates data and configurations, identified by a unique tenant ID to ensure separation from other clients.
TEMPLATE-ID: Identifier of the template used for this verification. These identifiers are configured in Studio.
To verify a Verifiable Credential and ensure its association with a subject, the credential’s authenticity and integrity must first be confirmed. This requires a verification process, where the credential is validated against its associated DID (Decentralized Identifier) and checked for compliance with cryptographic proofs.
Once the credential and its associated data are successfully validated, the verifier can trust the information it contains and proceed to grant access or perform the required action based on the verified details.
ACCESS-TOKEN: Access token received from the authentication request (This authentication must be executed by an application linked to the tenant selected into the authentication request).
VERIFICATION-TEMPLATE-ID: This is the Verification Template Identifier you gave in the configuration settings when creating your verification template in Gataca Studio.
This response is too big to be displayed in a QR code, so only the authentication_request field is shown to represent the session in the QR code. This session identifier (id) is required for the following step, so make sure to copy it.
In the section requested are all the Verifiable Credentials requested by the Verifier, which all follow the same structure. In this example, it is requesting this VC type.
Email Name: emailCredential
The structure of the Verifiable Credential shows the credential type (email), that the credential must be shared (it is mandatory), needs to be issued by a trusted issuer as the Trust Level is 1 (Validation), and the purpose for requesting the credential (authentication).
The session generation step can be automatic using GatacaQR, a JavaScript component allowing any relying party to generate a session in a simple way.
You will find the GatacaQR component code repositories at the end of this documentation.
5. Validating the Issuance Process
Getting the information from a specific verification process is also possible using the command below. Instead of retrieving information from a set of verification processes, this command retrieves the information from a specific verification process (using the process identifier).
Request Example
http
GET /api/v3/sessions/[VERIFICATION-ID]
Host: connect.gataca.io
Authorization: jwt [ACCESS-TOKEN]
Content-Type: application/json
VERIFICATION-ID : Session identifier. It must be recovered from the generated session response (Step 3). In this case, 4m8TLXcRUDpMrXkzorhoTpwMu6pkw4pUtHVSBf422c98 .
ACCESS-TOKEN: Access token received from the authentication request (This authentication must be executed by an application linked to the tenant selected into the authentication request).
The field PresentationSubmission includes the information the user shares, which in this case is only the email.
With this information, the user has been authenticated, which is used to authorize or not the user in the client service.
Integrating the GatacaQR Component for Identity Wallet Interaction
To streamline the interaction with identity wallets, Gataca offers the GatacaQR component, a versatile JavaScript library designed for seamless session management. This component simplifies the integration process for relying parties, enabling them to generate and manage sessions effortlessly while enhancing user experience.
Key Features of GatacaQR
QR Code Rendering: Displays a QR code that users can scan to initiate interactions with their identity wallet.
Real-Time Communication: Supports features such as polling and WebSocket integration for efficient session updates.
Deep Link Triggering: Allows for direct interaction with mobile devices via deep links, bypassing the need for QR scanning in certain use cases.
Customizable Layout: Offers flexibility to adapt the appearance of the QR code and its surrounding elements to align with the relying party’s branding and design preferences.
Ease of Integration: Simplifies complex session management workflows, providing a user-friendly API for developers.
Getting Started with GatacaQR
Developers can access comprehensive manuals and resources for using the GatacaQR component through the following repositories:
By leveraging GatacaQR, developers can focus on building intuitive user journeys while relying on a robust, pre-built solution for wallet interactions. This component ensures a streamlined, secure, and highly adaptable way to integrate identity wallet capabilities into your application.
WebHooks
The Gataca Studio platform introduces support for web-hooks, providing users with a flexible mechanism to receive real-time notifications about specific events within the system. Web-hooks can be configured directly through the graphical user interface (GUI), enabling seamless integration with external systems or workflows.
How Web-Hooks Work
Configuration: Users will define web-hooks via the Studio interface, specifying the target endpoint (URL). This functionality will be available for each of the templates that define the issuance and verification processes.
Triggering Events: When an event of interest occurs, Studio sends an HTTP POST request to the user-defined endpoint.
Payload: The POST request contains a structured payload with relevant data about the event. This allows external systems to process the information immediately and take appropriate actions.
Webhook Payload Structure
The payload sent to the configured endpoint will follow this format:
payload: [OPTIONAL] Map with the claims shared by the subject (avoid including id). If there is no info into the credential subject this field won’t be included.
verificationResult: List of results (steps passed, warnings and errors)
Benefits of Web-hook Integration
• Real-Time Updates: Enables immediate processing of events by external systems.
• Custom Workflows: Allows users to automate responses or actions based on Studio events.
• Scalability: Supports integration with diverse applications, including CRMs, analytics platforms, or custom systems.
The majority of Gataca endpoints are protected to avoid unauthorized access and security issues. This protection is based on access tokens issued using .
Details:
If you have any questions or need assistance integrating Gataca Studio, please get in touch with our support team at for further assistance.
