Meilisearch
Integrate your application with the Meilisearch API
🚀 Quickstart
Connect to Meilisearch with Tenklo and see data flow in 2 minutes. Meilisearch uses an API key generated in your Meilisearch Cloud project or self-hosted instance.
In Tenklo (free signup), go to Integrations -> Configure New Integration -> Meilisearch.
Connect your Meilisearch instance
Go to Connections -> Add Test Connection. Enter your instance URL and API key, then save.
Make your first request. Replace the placeholders with your secret key, integration ID, and connection ID:
curl "https://api.tenklo.dev/proxy/indexes" \
-H "Authorization: Bearer <NANGO-SECRET-KEY>" \
-H "Provider-Config-Key: <INTEGRATION-ID>" \
-H "Connection-Id: <CONNECTION-ID>"Or fetch credentials with the Node SDK or API.
✅ You're connected! Check the Logs tab in Tenklo to inspect requests.
Follow our Auth implementation guide to integrate Tenklo in your app.
To obtain an API key, follow the setup guide linked below.
📚 Meilisearch integration guides
Tenklo maintained guides for common use cases.
- How to connect your Meilisearch instance
Find your instance URL, create an API key, and connect it to Tenklo
Official docs: Meilisearch API reference
🧩 Pre-built syncs & actions for Meilisearch
Explore Nango-provided actions in your dashboard. Extend and customize them to fit your needs.
Others
| Function name | Description | Type | Source code |
|---|---|---|---|
add-documents | Add or replace documents in a Meilisearch index (batch). Returns the enqueued task. | Action | 🔗 Github |
delete-documents | Delete documents from a Meilisearch index by ids or by filter (exactly one must be provided). Returns the enqueued task. | Action | 🔗 Github |
generate-tenant-token | Generate a Meilisearch tenant token: a scoped, signed search JWT carrying per-index ACL rules. Expires after 1 hour unless expiresAt or expiresInSeconds is set. | Action | 🔗 Github |
get-documents | Fetch documents from a Meilisearch index, optionally filtered or by ids. | Action | 🔗 Github |
get-task | Fetch the status of a Meilisearch async task by its uid. | Action | 🔗 Github |
search-documents | Search documents in a Meilisearch index. | Action | 🔗 Github |
update-documents | Add or partially update documents in a Meilisearch index (batch). Returns the enqueued task. | Action | 🔗 Github |
Common gotchas
- Documents writes are asynchronous: the API returns an enqueued task (
taskUid); pollGET /tasks/{taskUid}to confirm completion. - Use an API key, not the master key. The master key cannot sign tenant tokens and should never leave your infrastructure.
- The instance URL must include the scheme and have no trailing slash, e.g.
https://ms-xxxx.meilisearch.io.