---
title: "Connect your app to KLIPY"
description: "<p><a href=\"https://klipy.com/\">KLIPY</a> is a media API that lets your RShift Sites app search and embed GIFs, stickers, and short clips, and generate AI emojis on demand."
---

> Documentation Index
> Fetch the complete documentation index at: https://rshift.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to KLIPY

<p><a href="https://klipy.com/">KLIPY</a> is a media API that lets your RShift Sites app search and embed GIFs, stickers, and short clips, and generate AI emojis on demand. It's a drop-in media layer for chat, social, and commenting features.</p>
<p>KLIPY is available as an <a href="/sites/integrations/app-connectors/">app + chat connector</a>: one shared connection that works in the project chat while you build and in your published apps.</p>
<p>With KLIPY, your app can:</p>
<ul>
<li>Search and embed GIFs, stickers, and short clips</li>
<li>Generate AI emojis on demand</li>
<li>Add a trending media picker to chat and social features</li>
</ul>
<blockquote>
<p><strong>Tip</strong></p>
<p>Reach for the KLIPY connector when your app needs a media picker, reaction stickers, or generated emojis. For a handful of static images you ship yourself, keep them in your app's assets instead.</p>
</blockquote>
<h2>Common use cases and example apps</h2>
<table>
<thead>
<tr>
<th style="text-align: left">Example app</th>
<th style="text-align: left">Example prompt</th>
<th style="text-align: left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left"><strong>Chat with GIF picker</strong></td>
<td style="text-align: left"><em>Use KLIPY and add a GIF picker to my chat app so users can search and send GIFs inline.</em></td>
<td style="text-align: left"><strong>Let users react and reply with GIFs.</strong><br />The app adds a searchable GIF picker to the message composer and embeds the selected GIF in the conversation.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Sticker reactions</strong></td>
<td style="text-align: left"><em>Use KLIPY and let users react to posts with stickers from a searchable picker.</em></td>
<td style="text-align: left"><strong>Add expressive sticker reactions.</strong><br />The app surfaces a sticker search and attaches the chosen sticker as a reaction.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Meme / clip feed</strong></td>
<td style="text-align: left"><em>Use KLIPY and build a trending feed of GIFs and clips users can browse and share.</em></td>
<td style="text-align: left"><strong>Surface trending media in a feed.</strong><br />The app pulls trending GIFs and clips and renders a browsable, shareable feed.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Custom emojis tool</strong></td>
<td style="text-align: left"><em>Use KLIPY and build a tool that generates custom AI emojis from a text prompt.</em></td>
<td style="text-align: left"><strong>Generate custom emojis on demand.</strong><br />The app sends a prompt to KLIPY and renders the generated AI emojis for the user to download or send.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Social composer</strong></td>
<td style="text-align: left"><em>Use KLIPY and add GIFs, stickers, and emojis to my social post composer.</em></td>
<td style="text-align: left"><strong>Enrich a post composer with media.</strong><br />The app lets users search GIFs, stickers, and emojis so they can drop media into posts.</td>
</tr>
</tbody>
</table>
<h2>How to connect KLIPY</h2>
<p>Who can create KLIPY connections depends on your plan and workspace settings. See <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a>. When adding a connection, you can choose between:</p>
<ul>
<li><strong>Managed by RShift Sites</strong> (no KLIPY account or API key required)</li>
<li><strong>Use your own credentials</strong> (connect with your own KLIPY API key)</li>
</ul>
<p>When the connection is created, you can <a href="/sites/integrations/app-connectors/#link-a-connection-to-a-project">link it to the projects</a> where you want to use it. Anyone building in a project can ask RShift Sites in the project chat to link their project to it.</p>
<p>Follow the setup steps below based on how you want to connect KLIPY.</p>
<p><strong>Managed by RShift Sites</strong></p>
<p>Choose this option if you want the fastest setup. You don't need to create a KLIPY account or API key. RShift Sites provides and manages the credentials for you.</p>
<blockquote>
<p><strong>Note</strong></p>
<p>You can create only one managed KLIPY connection per workspace.</p>
</blockquote>
<p><strong>Open KLIPY in Connectors</strong></p>
<p>Go to <strong>Connectors</strong> and select <strong>KLIPY</strong>.</p>
<p><strong>Add a connection</strong></p>
<p>Click <strong>Add connection</strong>.</p>
<p><strong>Name the connection</strong></p>
<p>In <strong>Display name</strong>, name the connection (for example, <code>KLIPY Prod</code>).</p>
<p><strong>Choose Managed by RShift Sites</strong></p>
<p>Under <strong>Authentication</strong>, select <strong>Managed by RShift Sites</strong>.</p>
<p><strong>Choose who can use this connection</strong></p>
<p>Managed connections are shared with the entire workspace by default. To limit who can use the connection, click <strong>Restrict to specific people</strong> under <strong>Sharing</strong>.</p>
<pre><code>    See [Who can use connections and clients](/sites/integrations/admin-controls/#who-can-use-connections-and-clients) for more information.
</code></pre>
<p><strong>Connect</strong></p>
<p>Click <strong>Connect</strong>.</p>
<p><strong>Use your own credentials</strong></p>
<p>Use your own credentials if you want to manage your KLIPY account, content, usage limits, and account settings directly in the KLIPY partner dashboard.</p>
<blockquote>
<p><strong>Note</strong></p>
<p>All media requests made through this connector count toward your KLIPY account's limits. Billing and quotas are handled directly by KLIPY, not RShift Sites.</p>
</blockquote>
<pre><code>You can create multiple KLIPY connections using different API keys, which is useful for separating environments (for example, development and production) or managing rate limits.
</code></pre>
<h3>Prerequisites</h3>
<pre><code>Before connecting KLIPY, make sure you have:

* A KLIPY account and API key
* Permission to **create connections** in your RShift Sites workspace (see [Who can create connections and clients](/sites/integrations/admin-controls/#who-can-create-connections-and-clients))
</code></pre>
<h3>Step 1: Get your KLIPY API key</h3>
<p><strong>Open the KLIPY partner dashboard</strong></p>
<p>Sign in to the <a href="https://partner.klipy.com">KLIPY partner dashboard</a>.</p>
<p><strong>Create or copy your API key</strong></p>
<p>Generate an API key for your app, or copy an existing one. With your own key you manage your KLIPY account, content, and usage limits directly.</p>
<blockquote>
<p><strong>Note</strong></p>
<p>Your KLIPY API key functions like a password. Keep it secure and never share it publicly. You'll need it in the next step.</p>
</blockquote>
<h3>Step 2: Connect KLIPY to RShift Sites</h3>
<p><strong>Open KLIPY in Connectors</strong></p>
<p>Go to <strong>Connectors</strong> and select <strong>KLIPY</strong>.</p>
<p><strong>Add a connection</strong></p>
<p>Click <strong>Add connection</strong>.</p>
<p><strong>Name the connection</strong></p>
<p>In <strong>Display name</strong>, name the connection (for example, <code>KLIPY Prod</code>).</p>
<p><strong>Choose your own credentials</strong></p>
<p>Under <strong>Authentication</strong>, select <strong>Use your own credentials</strong>.</p>
<p><strong>Enter your API key</strong></p>
<p>In <strong>API key</strong>, paste your KLIPY API key. Use <strong>Open KLIPY</strong> below the field to jump to the partner dashboard if you need to generate one.</p>
<p><strong>Choose who can use this connection</strong></p>
<p>Under <strong>Sharing</strong>, the connection is private to you by default and shows a <strong>Private</strong> label. To share it, click <strong>Share with others</strong>. Then add workspace members by email, or click <strong>Invite entire workspace</strong> to make the connection available to everyone in your RShift Sites workspace.</p>
<pre><code>    See [Who can use connections and clients](/sites/integrations/admin-controls/#who-can-use-connections-and-clients) for more information.
</code></pre>
<p><strong>Connect</strong></p>
<p>Click <strong>Connect</strong>. RShift Sites verifies the key against KLIPY before saving the connection.</p>
<p>When connected, anyone building in a project can ask RShift Sites in the project chat to link their project to KLIPY (based on configured connection-level access). Your RShift Sites apps can then search and embed media and generate AI emojis through the connector.</p>
<h2>Limitations</h2>
<p>The KLIPY connector cannot:</p>
<ul>
<li>Refresh or rotate API keys automatically. For connections that use your own credentials, generate a new key in the KLIPY partner dashboard and update the RShift Sites connection to rotate</li>
<li>Support per-end-user KLIPY login. Each connection represents a single KLIPY key shared across all projects linked to it</li>
<li>Manage your KLIPY account, content settings, or usage limits for connections that use your own credentials. Configure those in the KLIPY partner dashboard</li>
</ul>
<h2>Manage your {connector_0} connection</h2>
<p>Connections are managed from <a href="https://lovable.dev/dashboard?connectors"><strong>Connectors</strong></a>: select <strong>{connector_0}</strong>, then open the connection.</p>
<ul>
<li><strong>Unlink projects</strong> to remove {connector_0} access from specific projects while keeping the connection available for others. See <a href="/sites/integrations/app-connectors/#unlink-projects-from-a-connection">Unlink projects from a connection</a> for the steps.</li>
<li><strong>Delete the connection</strong> to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use {connector_0} stop working until a new connection is added. See <a href="/sites/integrations/app-connectors/#delete-a-connection">Delete a connection</a> for the steps and who can delete.</li>
</ul>
<h2>Related topics</h2>
<ul>
<li><a href="/sites/integrations/workday/">Connect your app to Workday</a></li>
<li><a href="/sites/integrations/notion/">Connect your app to Notion</a></li>
<li><a href="/sites/integrations/granola/">Connect your app to Granola</a></li>
<li><a href="/sites/integrations/slack/">Connect your app to Slack</a></li>
<li><a href="/sites/integrations/inngest/">Connect your app to Inngest</a></li>
</ul>

Source: https://rshift.helpcent.re/sites/integrations/klipy/index.mdx
