1. Authentication and API host

When coming from Tenor, the first change is replacing the host `https://tenor.googleapis.com` with `https://heypster-gif.com/giphy`. The second is replacing the `key` parameter with `api_key`, in line with the GIPHY-compatible layer exposed by Heypster.

# Tenor
curl "https://tenor.googleapis.com/v2/search?q=excited&key=YOUR_TENOR_KEY"

# Heypster
curl "https://heypster-gif.com/giphy/v1/gifs/search?q=excited&api_key=YOUR_HEYPSTER_API_KEY"

2. Endpoint mapping

3. Parameter changes

4. Pagination

Tenor uses `pos` and returns a `next` token. When migrating to Heypster through our GIPHY-compatible layer, you move to classic numeric pagination: `limit` sets the page size and `offset` tells how many items to skip.

// Tenor
const response1 = await fetch('https://tenor.googleapis.com/v2/search?q=cats&key=KEY');
const data1 = await response1.json();
const response2 = await fetch(`https://tenor.googleapis.com/v2/search?q=cats&key=KEY&pos=${data1.next}`);

// Heypster
const response1 = await fetch('https://heypster-gif.com/giphy/v1/gifs/search?q=cats&api_key=KEY&limit=25&offset=0');
const data1 = await response1.json();
const response2 = await fetch('https://heypster-gif.com/giphy/v1/gifs/search?q=cats&api_key=KEY&limit=25&offset=25');

5. Response parsing

A Tenor parser usually reads `results` and `next`. Here you need to read `data`, `pagination`, and `meta`. This is the main structural change after pagination.

{
  "data": [],
  "pagination": {
    "total_count": 500,
    "count": 25,
    "offset": 0
  },
  "meta": {
    "status": 200,
    "msg": "OK",
    "response_id": "heypster-response-id"
  }
}

const payload = await response.json();

const items = payload.data;
const offset = payload.pagination?.offset ?? 0;
const count = payload.pagination?.count ?? items.length;
const nextOffset = offset + count;
const status = payload.meta?.status;

6. Fields and renditions

7. Tracking

If your Tenor integration used `/v2/registershare`, plan a dedicated adaptation: the Heypster surface documented here focuses on search, discovery, and identification endpoints (`randomid`), not on a Tenor-style share-tracking endpoint.

8. Full JavaScript example

const API_HOST = 'https://heypster-gif.com/giphy';
const API_KEY = 'YOUR_HEYPSTER_API_KEY';

export async function searchTenorLike(query, page = 0, limit = 25) {
    const offset = page * limit;
    const url = new URL(`${API_HOST}/v1/gifs/search`);

    url.searchParams.set('api_key', API_KEY);
    url.searchParams.set('q', query);
    url.searchParams.set('limit', String(limit));
    url.searchParams.set('offset', String(offset));
    url.searchParams.set('rating', 'g');

    const response = await fetch(url.toString());
    const payload = await response.json();

    return {
        items: payload.data,
        pagination: payload.pagination,
        nextOffset: (payload.pagination?.offset ?? 0) + (payload.pagination?.count ?? 0),
        meta: payload.meta,
    };
}

9. Migration checklist

• Replace `https://tenor.googleapis.com` with `https://heypster-gif.com/giphy`.
• Replace `key` with `api_key` in every request.
• Map `search`, `featured`, `categories`, `autocomplete`, `search_suggestions`, `trending_terms`, `posts`, and `anonid`.
• Replace `pos` / `next` pagination with `limit` / `offset`.
• Adapt parsing from `results` to `data` and from `media_formats` to `images`.
• Explicitly verify the formats your interface actually consumes.
• Handle tracking separately if you used Tenor `registershare`.