> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to KLIPY

> Connect your app to KLIPY to search and embed GIFs, stickers, and clips, and generate AI emojis.

export const connector_0 = "KLIPY"

[KLIPY](https://klipy.com/) is a media API that lets your Lovable 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.

With KLIPY, your app can:

* Search and embed GIFs, stickers, and short clips
* Generate AI emojis on demand
* Add a trending media picker to chat and social features

<Tip>
  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.
</Tip>

## Common use cases and example apps

| Example app              | Example prompt                                                                            | Description                                                                                                                                                 |
| :----------------------- | :---------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Chat with GIF picker** | *Use KLIPY and add a GIF picker to my chat app so users can search and send GIFs inline.* | **Let users react and reply with GIFs.**<br />The app adds a searchable GIF picker to the message composer and embeds the selected GIF in the conversation. |
| **Sticker reactions**    | *Use KLIPY and let users react to posts with stickers from a searchable picker.*          | **Add expressive sticker reactions.**<br />The app surfaces a sticker search and attaches the chosen sticker as a reaction.                                 |
| **Meme / clip feed**     | *Use KLIPY and build a trending feed of GIFs and clips users can browse and share.*       | **Surface trending media in a feed.**<br />The app pulls trending GIFs and clips and renders a browsable, shareable feed.                                   |
| **Custom emojis tool**   | *Use KLIPY and build a tool that generates custom AI emojis from a text prompt.*          | **Generate custom emojis on demand.**<br />The app sends a prompt to KLIPY and renders the generated AI emojis for the user to download or send.            |
| **Social composer**      | *Use KLIPY and add GIFs, stickers, and emojis to my social post composer.*                | **Enrich a post composer with media.**<br />The app lets users search GIFs, stickers, and emojis so they can drop media into posts.                         |

## How to connect KLIPY

Workspace **admins** and **owners** can connect KLIPY.

KLIPY uses a Bring Your Own Key model: you connect your own KLIPY API key, and your app's media requests are proxied through the Lovable gateway so the key stays on the server and is never exposed in your published app. You keep full control over your KLIPY account, content, usage limits, and account settings in the KLIPY partner dashboard.

When the connection is created, KLIPY becomes available across all projects in the workspace. Anyone building in a project can ask Lovable in chat to link their project to it.

### Prerequisites

Before connecting KLIPY, make sure you have:

* A KLIPY account
* Your KLIPY API key from the [KLIPY partner dashboard](https://partner.klipy.com)
* Lovable workspace **owner** or **admin** role

<Note>
  All media requests made through this connector count toward your KLIPY account's limits. Billing and quotas are handled directly by KLIPY, not Lovable.
</Note>

### Step 1: Get your KLIPY API key

<Steps>
  <Step title="Open the KLIPY partner dashboard">
    Sign in to the [KLIPY partner dashboard](https://partner.klipy.com).
  </Step>

  <Step title="Create or copy your API key">
    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.
  </Step>
</Steps>

<Warning>
  Your KLIPY API key functions like a password. Keep it secure and never share it publicly. You'll need it in the next step.
</Warning>

### Step 2: Connect KLIPY to Lovable

<Steps>
  <Step title="Open KLIPY in Connectors">
    Go to **Connectors → App connectors** and select **KLIPY**.
  </Step>

  <Step title="Add a connection">
    Click **Add connection**.
  </Step>

  <Step title="Configure the connection">
    Paste your KLIPY API key into the **API key** field. Use **Open KLIPY** below the field to jump to the partner dashboard if you need to generate one.
  </Step>

  <Step title="Choose who can access this connection">
    Under **Who can access this connection**, decide who in your workspace can use the connection:

    * **Only you** (default): only the person creating the connection can use it and its associated data.
    * **Invite specific people**: only you and explicitly added workspace members can use the connection and its associated data.
    * **Invite entire workspace**: click **Invite entire workspace** to make the connection available to everyone in your Lovable workspace.

    See [Who can manage connections](/integrations/introduction#who-can-manage-connections) for more information.
  </Step>

  <Step title="Connect">
    Click **Connect**. Lovable verifies the key against KLIPY before saving the connection.
  </Step>
</Steps>

When connected, anyone building in a project can ask Lovable in chat to link their project to KLIPY (based on configured connection-level access). Your Lovable apps can then search and embed media and generate AI emojis through the connector.

## Limitations

The KLIPY connector cannot:

* Refresh or rotate API keys automatically. To rotate, generate a new key in the KLIPY partner dashboard and update the Lovable connection
* Support per-end-user KLIPY authentication (each connection uses a single shared API key, scoped to the workspace)
* Manage your KLIPY account, content settings, or usage limits. Configure those in the KLIPY partner dashboard

## How to unlink projects from a {connector_0} connection

Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects.

To unlink projects:

<Steps>
  <Step title="Open Connectors">
    Open **Connectors**, then go to **App connectors**, and select **{connector_0}**.
  </Step>

  <Step title="Open the connection">
    Open the connection you want to manage.
  </Step>

  <Step title="Select projects">
    Under **Linked projects**, check the projects you want to unlink.
  </Step>

  <Step title="Confirm">
    Click **Unlink projects** and confirm.
  </Step>
</Steps>

When unlinked, those projects will no longer have access to {connector_0} through this connection. If a project needs {connector_0} again, you can link it to any available connection.

## How to delete a {connector_0} connection

Workspace admins and owners can delete {connector_0} connections. Other members can delete a connection if they created it, or if they have been explicitly granted access to it.

<Warning>
  Deleting a connection is permanent and cannot be undone. It will remove the credentials from all linked projects, and any apps using this connection will stop working until a new connection is added.
</Warning>

Before deleting, review the **Linked projects** section to see which projects are currently using the connection.

To delete a connection:

<Steps>
  <Step title="Open Connectors">
    Open **Connectors**, then go to **App connectors**, and select **{connector_0}**.
  </Step>

  <Step title="Open the connection">
    Open the connection you want to remove.
  </Step>

  <Step title="Review linked projects">
    Review the **Linked projects** section.
  </Step>

  <Step title="Delete">
    Under **Delete this connection**, click **Delete** and confirm.
  </Step>
</Steps>
