Build first. Keep usage clear.
The developer workspace gives you project keys, a credit balance, and request counts. Existing integrations using the public API keep working.
Planning a production integration
GifSnap API access is best effort: there is no published uptime SLA or reserved throughput, and content or media URLs can become unavailable. Test the API against your needs and provide a fallback for failed requests and unavailable media. Contact support to discuss your requirements before depending on it for a critical workflow.
The keyless public API and the authenticated credit API are different access paths. A fixed quota has not been published for the keyless API; capacity and abuse protections can still apply. For the authenticated API, the account-level limit is currently 120 requests per minute, shared across its projects; other service capacity limits also apply. Handle HTTP 429 and follow Retry-After when supplied.
The authenticated API starts with free credits. Card top-ups are not available yet; the planned one-time pack and billing details are described below. Credits pay for API requests, not rights to the GIFs: preserve source information and obtain any permissions your use requires. See the API terms and refund policy.
Start with free credits
Your first project activates 10,000 free credits. The grant is once per verified account, shared by its projects. No card is required. Extra projects do not create extra starter grants.
What uses a credit?
One successful request to the authenticated search, trending or GIF lookup API uses one credit. A search or trending response can contain up to 50 GIFs for that credit. Invalid requests and provider failures use no credits. Loading the returned GIF URLs does not debit this API balance.
Credits on this API do not purchase rights to third-party content. Preserve source attribution and follow the applicable content permissions. Video importing, generation, For You recommendations and human integration services are separate from this credit API.
Keep your key on your server
Create a project in the dashboard, then save its key as GIFSNAP_API_KEY in your server environment. The complete key is shown only once. You can revoke and replace keys in the dashboard.
curl "https://gifsnap.com/api/developer/v1/gifs/search?q=happy&limit=6" \
-H "Authorization: Bearer $GIFSNAP_API_KEY" \
-H "Idempotency-Key: $(uuidgen)"For web or mobile apps, call this endpoint through your own backend. Never embed the secret key in browser JavaScript, a mobile binary or a public repository. The existing unauthenticated SDK path remains available for public clients.
Requests and retries
Supported GET paths are gifs/search, gifs/trending, gifs/{id}, stickers/search and stickers/trending, below /api/developer/v1/. Responses preserve API v1 fields and original media URLs. Use q for searches, page and limit for pagination.
Generate an idempotency key of 16–80 letters, digits, hyphens or underscores for each logical request. Reuse it with the same API key, path and parameters when retrying that request. A successful retry does not debit another credit, but its results may be refreshed. Changing parameters under the same key returns HTTP 409. Generate a new key for a new search or page.
X-Credits-Remaining reports the available balance; X-Credits-Charged reports 0 or 1 for this attempt. HTTP 402 means credits are exhausted or a payment adjustment requires attention. HTTP 429 means slow down; respect Retry-After. Requests currently share a 120-per-minute account limit. An in-flight duplicate returns HTTP 409; retry it after a short delay.
Simple, one-time pricing
10,000 free credits to start. Then $10 USD for 10,000 more credits. That is $1 per 1,000 successful API requests. Applicable taxes are added at checkout. Purchased credits have no scheduled expiry. There is no subscription or automatic recharge.
Card top-ups are not open yet. Free developer accounts are available now. The dashboard will offer the credit pack after payment setup and testing are complete. You will see the exact total before confirming payment; no background charge is made when a balance runs out.
A payment success screen does not itself grant credits. The balance updates after the payment provider confirms completion. Refunds and disputes adjust the corresponding purchased balance. If an adjustment exceeds the unused purchased balance, authenticated requests pause until it is resolved. Free and purchased balances are tracked separately.
Data in the workspace
We store your account identifier, a protected hash of your verified email for starter-credit abuse prevention, project details you enter, hashed API keys, daily request/error counts, a credit ledger and payment references. We do not store raw search queries in the billing ledger, card numbers, chat messages or recipient details. Billing request fingerprints are keyed hashes used for retry protection. A project URL is a developer-provided claim, not proof of ownership or an endorsement.
API terms · Refund policy · Privacy policy · Contact support · Open your workspace →