Junction
Version
This integration utilizes the Junction Junction API v2.
Base URL
The base URL used for all Junction API endpoints contains the Environment and Region:https://api.environment.region.tryvital.io/v2
Endpoints Utilized
DataGrail uses the following endpoints to authorize and test the connection:
Authentication & Authorization
The DataGrail Junction integration connects using API Key authentication which requires an API Key.
Limits
Limits in Junction are calculated using the leaky
bucket algorithm. All requests that are made after rate limits have been
exceeded are throttled and an HTTP 429 Too Many Requests
error is returned.
Requests succeed again after enough requests have emptied out of the bucket.
- DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
- DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).
Capabilities
Access
DataGrail's Junction integration provides Synchronous Access capabilities for the following supported identifier categories: Email, Service ID, and User ID.Data Interactions
For Access requests, DataGrail will take the following actions:
- Search users using configured identifiers.
- Search user demographics.
- Search user latest insurance
Endpoints Utilized
Deletion
DataGrail's Junction integration provides Synchronous Deletion capabilities for the following supported identifier categories: Email, Service ID, and User ID.Data Interactions
For Deletion requests, DataGrail will take the following actions:
- Delete extracted users data after a 7-day grace period. Deregister their all provider connections immediately.
Endpoints Utilized
Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.