Documentation

Move a Tenor integration to GifSnap

A practical migration guide for GIF search, pagination, and selected media. Adapt your existing UI or replace it with the React picker.

Google’s published schedule ended external Tenor API integrations on June 30, 2026, after closing new API key sign-ups on January 13. Tenor’s website and Google-owned integrations are separate from that shutdown. See Google’s Tenor API discontinuation notice.

Choose your integration path

If your app uses React, the GifSnap picker provides a search interface and an onSelect callback. To keep your existing interface, replace its search and response mapping with the GifSnap REST API.

GifSnap uses its own API contract. Plan to update request parameters, response handling, and pagination; existing Tenor IDs and parameters are not automatically interchangeable.

Map the pieces that change

IntegrationTenor APIGifSnap API
Search/v2/search/api/v1/gifs/search?q=hello
Authenticationkey and client_keyCurrent public endpoints accept requests without an API key.
Paginationpos / next cursorpage / limit, then pagination.next_page.
Selected mediaresults[].media_formatsdata[].url for the animation, optional animated_preview for smaller renditions, and preview_url for a poster that may be still.

The Tenor columns describe its historical endpoint documentation and response objects.

Replace the search request

Start at page 1 for each new query. Request the next page only when the response says one is available, and keep the query and limit consistent.

Search with GifSnap
const url = new URL('https://gifsnap.com/api/v1/gifs/search');
url.searchParams.set('q', 'hello');
url.searchParams.set('page', '1');
url.searchParams.set('limit', '12');

const response = await fetch(url);
if (!response.ok) {
  throw new Error('GIF search failed: ' + response.status);
}
const result = await response.json();
const gifs = result.data;
const nextPage = result.pagination.next_page;

Normalize media for your UI

Translate the response into your application’s own attachment shape. Keep the returned URL unchanged and retain source metadata. Avoid constructing a media URL from an ID or assuming every image ends in .gif. This simple attachment preview uses the original animation; posterUrl is only an optional placeholder and may be still.

Application attachment
function toAttachment(gif) {
  return {
    id: gif.id,
    url: gif.url,
    previewUrl: gif.url, // Display the selected animation.
    posterUrl: gif.preview_url, // Optional, possibly still placeholder.
    alt: gif.title || 'Animated image',
    width: gif.width,
    height: gif.height,
    source: gif.source,
  };
}

For a results grid, use a validated animated_preview when its MIME type is supported by your renderer, with url as the fallback when it is absent, unsupported, or fails to load. GIF and WebP work in an image element; MP4 and WebM need a video element. Follow the media response reference and keep the original url for sending.

Review behavior before switching

The public GifSnap API is currently best-effort, without a published SLA. Evaluate it against your app’s requirements, including media terms, moderation, and reliability.

Continue with the endpoint reference or try the live React picker.

Let’s get GIFs working in your app.

Choosing an SDK, moving an existing picker, or stuck on your first request? Tell us about your app and stack so we can help with your integration.

Get integration help

Ask a question or discuss a $299 implementation pilot. No payment is taken on this website.