Loading...
Loading...
A Profile represents the information about the currently authenticated end-user.
In addition to financial data, Profiles can store important information about your end-users, such as their email, phone, birthday, address and more. While all customer data is encrypted at rest, Quiltt adds additional column-level encryption to sensitive fields that may contain PII.
Metadata
GraphQL is the recommended way to interface with Profile data. The following queries and mutations are available:
Profile GraphQL API Reference
profileReturns information about the authenticated Profile:
profileUpdateUpdates the Profile with supplied attributes. In this example, we are changing
Joe's name and adding some metadata fields:
Platform API Reference
While GraphQL is our recommended approach for interacting with Profiles, we also provide REST endpoints for scenarios where they may be more convenient. The following REST endpoints are available for managing Profiles:
GEThttps://api.quiltt.io/v1/profilesRetrieves a paginated list of all profiles in the current environment.
GEThttps://api.quiltt.io/v1/profiles/{profileId}Retrieves a specific profile by ID.
POSThttps://api.quiltt.io/v1/profilesCreates a new profile in the current environment. Supports optional UUID and other profile attributes.
PATCHhttps://api.quiltt.io/v1/profiles/{profileId}Updates an existing profile with new attributes.
DELETEhttps://api.quiltt.io/v1/profiles/{profileId}Triggers deletion of a profile by ID.
For interactive API documentation and to test these endpoints, visit the API Reference - Profiles.
profile.createdThis event fires once a new Profile is created in your Environment.
profile.deletedThis event fires when a Profile has been fully deleted from your Environment.
profile.readyThis event fires when Enrichment has been completed.