Data Request Templates

Data Request Templates serve as the foundational blueprint for each Data Request, ensuring a uniform structure and standardized format for each inquiry.

One must select an appropriate Data Request Template to initiate a Data Request.

Our Explorer platform coming soon) will provide insights into the most popularly utilized Data Request Templates, allowing you to make more informed decisions. While Gateway has already curated a selection of templates designed to meet a broad range of data and verification needs, we also offer the flexibility to create custom templates through our API for specialized requirements.

How it works?

Data Request Templates offer a streamlined mechanism for verifiers to aggregate data from multiple sources, such as your Listening History from Spotify, KYC details from Coinbase, and Purchase History from Amazon, all within a single request.

This efficiency eliminates the need for users to navigate through multiple requests, allowing them to grant permission for data sharing in one simple action. These templates also serve to standardize the data request process, making it easier for multiple verifiers with similar data or verification needs to quickly integrate and start retrieving the information they require via our dashboard. Additionally, the popularity of certain data models within these templates can influence Issuers to adopt those models, creating a more robust and widely-used data ecosystem.

Request Types

The protocol empowers developers to craft highly customizable data requests by integrating an array of dynamic parameters. Whether you're interested in specific data models, issuers, claim details, or issuance dates, you can combine these elements to formulate the ideal template for your needs.

⚠️ As a best practice, verifiers should focus on data minimization, requesting only the essential information required for their verification/data use process. This proactive approach not only streamlines the data exchange but also mitigates risks in the event of a data breach.

Below are some of the parameters you can create a template with:

⚠️ By default, verifiers only receive PDAs that have the “Valid” status.

Data Models

Verifiers enjoy the flexibility to request Private Data Assets (PDAs) that span multiple data models. For example, one could craft a request that simultaneously seeks PDAs from both the "Top 1% Listener" and "Top Merchandise Buyer" Data Models, offering a holistic snapshot of a recipient's behaviors and preferences across different contexts. If you're new to the concept of a Data Model, please visit this page for more information.


Each request must contain at least 1 data model asked but can contain up to 10.

Customizing Quantity of PDAs

Verifiers can precisely tailor the number of Private Data Assets (PDAs) they wish to request from a specific data model. They have the option to define their request in the following ways:

  1. Exactly "X" PDAs
  2. More than "X" PDAs
  3. Up to "X" PDAs

For example, TicketMaster may stipulate a requirement for exactly 2 PDAs from the "Top 1% Listener" Data Model, while SongKick may seek more than 3 PDAs from the same model.

**Adjusting Request Optionality**

Additionally, verifiers have the option to designate certain PDA requests as optional within a data model. This means that recipients are not obliged to provide those optional PDAs. For instance, TicketMaster might require PDAs from the "Top 1% Listener" Data Model, while making PDAs from the "Year in Review" Data Model optional.

⚠️ If you're setting a specific quantity requirement for PDAs within a data model, be sure that the issuer has indeed produced that many PDAs. Otherwise, you risk a high rate of unsuccessful user responses.

Toggling Claims

Verifiers have the ability to pinpoint specific claim fields within required data models to meet specialized criteria. For an in-depth understanding of the different types of claims your data model may encompass, please consult our API documentation. Here are a few illustrative examples:

  1. Within the "Top 1% Listener" data model, verifiers might specify that they only wish to receive PDAs from those who are within the top ".5%" of listeners.
  2. Another verifier using the "Top 1% Listener" data model might stipulate that the PDA must indicate the individual is a top 1% listener of "Taylor Swift."
  3. Verifiers have the freedom to combine these criteria to formulate an even more targeted request.


These examples are just the tip of the iceberg! To explore more versatile and intriguing ways to leverage claim data, please refer to our API documentation.


Verifiers also have the capability to tailor their requests by specifying particular IssuerIDs within a given data model. For instance, within the "Top 1% Listener" Data Model, verifiers can precisely request Private Data Assets (PDAs) that you hold from designated platforms such as Apple Music and Spotify.