asset.kiwi connect

Connect Drupal to asset.kiwi, a digital asset manager. Browse, import and sync assets in the Media Library, and see where each asset is used.

Features

asset.kiwi Connect lets you use assets from your asset.kiwi account inside Drupal without re-uploading them. Assets become native Drupal media entities, and Drupal stays in sync with changes made in asset.kiwi.

• Media source plugin: asset.kiwi assets are native media entities. Metadata such as alt text, description, dimensions and variant URLs maps to your own fields.
• Visual picker: search and filter by collection, tag, asset type or semantic search. It runs inside the Media Library and the field widget. The API token never reaches the browser.
• Field widget: the "asset.kiwi Browser" widget works on any text field that stores an asset UUID, including non-media entities such as nodes and paragraphs.
• Formatters: image, video and audio formatters render asset.kiwi variant URLs.
• Webhook sync: renames, alt text and description changes are pushed to Drupal. Deleted assets unpublish their media instead of breaking existing references.
• Usage tracking: when a media entity is saved or deleted, asset.kiwi is notified, so it knows where each asset appears.
• Upload to asset.kiwi: optional upload from the Media Library, controlled by a permission and a setting.
• Drush command: assetkiwi:import-assets batch-imports assets with filters and a dry-run mode.
• Migration submodule: assetkiwi_connect_migrate moves locally stored media files to asset.kiwi.

Use this module when your editors already manage assets in asset.kiwi and want them available in Drupal. It suits teams that need consistent alt text across sites, or want to see where an asset is used before changing or deleting it.

Post-Installation

1. Enable the module.
2. Go to Configuration → Media → asset.kiwi Settings (/admin/config/media/assetkiwi). Enter the API base URL (no trailing slash) and your API token, then click Test Connection.
3. Optional: set a Webhook Secret. It must match the secret in asset.kiwi. The webhook endpoint is /assetkiwi/webhook, and requests are verified with HMAC-SHA256.
4. Choose an authentication mode:
   • Shared token (default): one token for all users.
   • Per-user OAuth: each user connects their own asset.kiwi account. This needs an OAuth client in asset.kiwi with the redirect URI /assetkiwi/oauth/callback and at least the assets:read scope.
5. Create a media type at Structure → Media types and select asset.kiwi Asset as its media source. Choose the allowed asset types, then map the metadata to fields.
6. On the media type's Form display, set the source field widget to asset.kiwi Browser. On Display, set the formatter to asset.kiwi Image (or Video or Audio).
7. Grant the permissions Administer asset.kiwi settings, Browse asset.kiwi assets and, if needed, Upload files to asset.kiwi.

Image styles are not applied to asset.kiwi variant URLs by default. To use image styles, download the file on import, or map each style to an asset.kiwi variant in the settings.

Additional Requirements

• Drupal 11.
• PHP 8.3 or later (required by Drupal 11).
• Drupal core modules Media and Media Library.
• An asset.kiwi account with an API token. Per-user OAuth also needs an OAuth client in asset.kiwi.
• Drush 13 or later, only for the assetkiwi:import-assets command.

No contrib modules are required.

Recommended modules/libraries

None are required. Drupal core's Image module works with the downloaded local file for image styles and responsive images.

Similar projects

This module connects Drupal to asset.kiwi specifically. Drupal's built-in Media and Media Library handle local files without an external service. Use this module when the source of truth for your assets is asset.kiwi.

Supporting this Module

Development is maintained by asset.kiwi. To report issues or contribute, use the links under Community Documentation.