Drip
Version
This integration utilizes the Drip REST API v2.
Base URL
The base URL used for all Drip API endpoints:https://api.getdrip.com/v2
Endpoints Utilized
DataGrail uses the following endpoints to authorize and test the connection:
| Method | Endpoint | Purpose | Docs |
|---|---|---|---|
| GET | /accounts | Validate credentials | |
| GET | https://www.getdrip.com/oauth/authorize | Request authorization | |
| POST | https://www.getdrip.com/oauth/token | Get and refresh access token |
Authentication & Authorization
The DataGrail Drip integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.
Limits
Limits in Drip 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 Drip 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:
- Fetch list of the active Drip accounts.
- For each collected accounts, search Subscribers by the configured identifiers.
Endpoints Utilized
| Method | Endpoint | Purpose | Docs |
|---|---|---|---|
| GET | /accounts | Fetch all accounts | |
| GET | /{account_id}/subscribers | Search subscribers |
Deletion
DataGrail's Drip 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:
- Fetch list of the active Drip accounts.
- For each collected accounts, search Subscribers by the configured identifiers.
- Delete a Subscriber from the account.
Endpoints Utilized
| Method | Endpoint | Purpose | Docs |
|---|---|---|---|
| GET | /accounts | Fetch all accounts | |
| GET | /{account_id}/subscribers | Search subscribers | |
| DEL | /{account_id}/subscribers/{identifier} | Delete subscriber |
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.