GIPHY
DESIGN · FILES & DOCS
GIF, sticker and emoji search, trending feeds, and uploads on their own key.
Connecting GIPHY in practice
Every new key is a beta key capped at 100 API calls an hour, and the only route past it is an application GIPHY reviews per key followed by a pricing conversation. On top of that, every surface using the API has to “conspicuously display ‘Powered By GIPHY’ attribution marks”, which is a product requirement an agent integration rarely plans for.
Scopes that draw scrutiny
Beta keyWhat every account starts with. Rate limited to 100 searches or API calls per hour, which is a development budget rather than a production one.Production keyRequires submitting an application from the dashboard for GIPHY to review, after which they "contact qualifying developers to discuss pricing". Limits are set as part of that conversation.
Rate limits
- Beta keys: 100 API calls per hour.
- Production key limits are not published — they are agreed during the upgrade review.
Worth knowing
- The upgrade is per key, clicked "for each key used", so a multi-surface integration needs a separate approval for each one.
- GIPHY expects the upgrade request only when an app is "QA complete and close to going live", so an integration cannot be load-tested at production limits beforehand.
- GIPHY acknowledges a backlog — "we receive a lot of applications for upgraded Production keys" — so the 100-an-hour ceiling is the operating limit for an unknown stretch of time.
- Attribution uses GIPHY’s approved official logo marks; substituting a text label is not what the terms describe.
Checked against GIPHY API documentation (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put GIPHY behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.