Overview
Tenor V2-compatible API
Compatibility API
The Compatibility API provides a drop-in replacement for many applications with existing Tenor integrations. Response schemas match the Tenor V2 format, including the results array structure, pagination cursors, and media format objects.
Base URL
https://compat.gifbox.me/v2
Endpoint Availability
| Endpoint | Description | |
|---|---|---|
| ✅ | /search |
Search for posts by keyword |
| ✅ | /featured |
Retrieve featured posts |
| ✅ | /categories |
Get a list of post categories for browsing |
| 🟨 | /search_suggestions |
Get different possible queries for a query1 |
| 🟨 | /autocomplete |
Get autocomplete suggestions for a query1 |
| 🟨 | /trending_terms |
Get currently trending search terms1 |
| ✅ | /registershare |
Register share event for a post |
| ✅ | /posts |
Retrieve posts by ID |
Response Format
All endpoints return JSON responses following the Tenor V2 schema.
Gifbox Extensions
Some endpoints can return additional Gifbox-specific fields that are not part of the Tenor V2 schema. To keep responses drop-in compatible by default, these fields are omitted unless you opt in by adding the gifbox_extensions query parameter to the request.
| Endpoint | Extra fields | Description |
|---|---|---|
/categories |
special, gradient |
Marks a featured category and provides a CSS gradient for styling its tag. |
The parameter is a flag; its value is ignored, so ?gifbox_extensions or ?gifbox_extensions=1 both enable the extra fields.
Migration from Tenor
Migration requires two changes:
- Update the base URL from
https://tenor.googleapis.com/v2tohttps://compat.gifbox.me/v2 - Replace your Tenor API key with a Gifbox API key. Retrieve your Gifbox API key from your API dashboard.
No other code changes should be necessary. The response format is identical, and all standard Tenor V2 client libraries should work without modification.
If you encounter compatibility issues with specific endpoints or response fields, please report them so we can address gaps in the implementation.