Create gifts
Use this endpoint to create one or more gifts within a Campaign and initiate the Triggered Gifting flow. Snappy will notify recipients based on the Campaign’s Notification Policy.
Required fields:
campaignId- the Campaign ID to send underrecipients- array of recipients, each requiring at minimum afirstnameand an identifier to send to (email or phone). Include a uniquekeyper recipient for duplicate detection.
Optional fields:
customization- Gift Customization overrides (giftProperties,notificationPolicy,recipientExperience). Overrides apply only to gifts created in this call.metadata- optional key-value pairs (max 50 pairs, keys up to 40 chars, values up to 500 chars)companyIdquery 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)
Behavior Notes:
- Supports batch creation - multiple recipients in a single request. Each recipient generates its own Gift with its own
linkandkey. - A successful request returns the Gift objects with an initial status of
unopenedand a unique claimlinkfor each recipient. - Webhook events fired through the lifecycle:
gift-status-changed(unopened→unwrapped→opened→claimed/expired), andgift-notification-initial-sent. - The top-level
sendingMethodfield is deprecated - usecustomization.notificationPolicy.sendingChannelsinstead.
Permissions
- Requires:
gifts:create
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"
Body
The gift object.
Campaign ID
^[A-Za-z0-9]{8,}$"12345678"
The recipients of the gift.
Deprecated. Use "customization.notificationPolicy.sendingChannels" instead.
mail, sms, mailAndSms, link "mail"
Customization configuration of the gift.
Optional metadata object with key-value pairs. Keys must be alphanumeric (including underscores) and up to 40 characters. Values must be alphanumeric and up to 500 characters. Maximum 50 key-value pairs allowed.
{ "key1": "value1", "key2": "value2" }Response
Ok
The response of the gift creation
The message of the response
Optional metadata object with key-value pairs. Keys must be alphanumeric (including underscores) and up to 40 characters. Values must be alphanumeric and up to 500 characters. Maximum 50 key-value pairs allowed.
{ "key1": "value1", "key2": "value2" }