Get recipients
Use this endpoint to retrieve a list of Recipients based on your specified criteria. Use this when building a recipient picker in your UI, syncing recipients to your system, or finding recipients by name, email, or external ID.
Filtering options:
firstNamesquery parameter - comma-separated list of first nameslastNamesquery parameter - comma-separated list of last namesemailsquery parameter - comma-separated list of email addresses (each must be a valid email format)emailOverridesquery parameter - comma-separated list of email override addressesexternalIdsquery parameter - comma-separated list of your-system IDsaccountIdsquery parameter - comma-separated list of Account IDssourcesquery parameter - comma-separated list of recipient sources (apiIntegration,hrisIntegration,manual,ftpIntegration,fileSync)fieldsquery parameter - comma-separated field projection. Valid values:id,createdAt,updatedAt,firstName,lastName,email,emailOverride,mobilePhone,country,externalId,accounts,updatedBy,source,owner,type,recipientCustomFields,birthday,fullcompanyIdquery parameter - Company ID (when not inferable from the calling key)Request-Sourceheader - source of the request (api_native,api_zapier,api_salesforce,api_ftp,api_make)
Pagination:
skipquery parameter - number of records to skip (default0)limitquery parameter - max records per page (1-200, default200)
Please note:
- All array filters use OR semantics - passing multiple
firstNamesreturns recipients matching any of the supplied names. - PII fields are masked unless your API key has the
recipients:read:unmaskedscope.
Permissions
- Requires:
recipients:read:maskedorrecipients:read:unmasked
Authorizations
Company Level Authentication
Company level authentication provides access to all resources under your company, including accounts, campaigns, gifts, and recipients.
Getting Your API Key
- Create an API Key: Use the
POST /v2/authentication/apiKeysendpoint to generate a new API key - Set Expiration: Choose from 30, 60, 90, or 180 days (default: 90 days)
- Optional mTLS: Enable mutual TLS for enhanced security
- Name Your Key: Provide a descriptive name for easy identification
Using Your API Key
Include your API key in the X-Api-Key header for every request:
X-Api-Key: YOUR_24_CHARACTER_API_KEYAPI Key Management
- Maximum Keys: Up to 3 active API keys per company
- Rotation: Delete old keys before creating new ones when at the limit
- Security: Keys are hashed and cannot be retrieved after creation
Enhanced Security (mTLS)
For production environments, enable mutual TLS authentication:
- Set
enforceMtls: truewhen creating the API key - Contact support to obtain your client certificates
- Use the mTLS endpoint:
https://mtls-api.snappy.com/public-api
Headers
Source of the request
api_native, api_zapier, api_salesforce, api_ftp, api_make "api_native"
Query Parameters
Company ID
^[A-Za-z0-9]{8,}$"12345678"
The first name of the recipient.
1["John"]The last name of the recipient.
1["Doe"]The external id of the recipient.
1["123", "124"]Recipient email addresses (must be valid email format).
1^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$["sad@asd.com"]Alternative email addresses to use for sending gifts, overriding the recipient's primary email.
1^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$["sad@sad.com"]The account id of the recipient.
1["a12bcd34", "a56bcd78"]The source of the recipient.
1The source of the recipient.
apiIntegration, hrisIntegration, manual, ftpIntegration, fileSync ["apiIntegration", "ftpIntegration"]Fields to include in the response. Use 'full' to include all fields.
1Fields to include in the response. Use 'full' to include all fields.
id, createdAt, updatedAt, firstName, lastName, email, emailOverride, mobilePhone, country, externalId, accounts, updatedBy, source, owner, type, recipientCustomFields, birthday, full ["id", "firstName"]Number of records to skip for pagination (use with limit for paging through results)
x >= 00
Maximum number of records to return per page
1 <= x <= 200200