Documentation

Build with your coding assistant

One reference for the right package, the right imports and your first working GIF picker.

Give your assistant the integration reference

Use this prompt when adding GIF search to an existing project. The reference covers React, Next.js, Angular, JavaScript, SwiftUI and Jetpack Compose, plus HTTP for other languages.

Copy into your coding assistant
Add GifSnap GIF search to this project.
Read https://gifsnap.com/docs/integration.md and use the SDK for our existing stack.
Check https://gifsnap.com/sdk-manifest.json for the exact install command.
Render animated media using gif.url, handle selection in our composer,
and include loading, empty and recoverable error states.
Preserve our app's theme and verify that the integration builds.

Documentation that tools can read

Markdown integration reference ↗Documentation index · llms.txt ↗SDK versions and install commands ↗OpenAPI specification ↗

These public files work with tools that can read a URL. If your editor supports a custom documentation source, add https://gifsnap.com/docs. You can also attach the Markdown reference directly. Documentation indexing and retrieval depend on the tool you use.

Choose your application’s stack

Keep the first integration reliable

Use the exact published distribution in the SDK manifest. React, JavaScript and Angular packages are available on npm. Native integrations use Swift Package Manager and GifSnap’s hosted Maven repository.

Render gif.url for animation; previews may be still images. Preserve returned URLs, avoid duplicate results when appending pages, and handle a failed request separately from an empty result. Your application controls sending the selected GIF.

The public API currently needs no API key. See the API reference for response fields, pagination and service behavior.

Inspect the implementation

Source and tests are public for the web SDKs, Swift package and Android libraries.