Configuration
Use a dedicated index and a server-only API key restricted to that index. Never expose the key to React or public configuration. Use HTTPS when connecting across machines; HTTP is intended for a trusted local connection.Initial indexing
Next after value printed by the preceding run, not an assumed batch number. Each call reads at most120 indexed database entries. It does not scan storage, fetch originals or analyze media. It reports a Meilisearch task identifier: accepted tasks are not necessarily completed tasks. Inspect task success in Meilisearch before relying on the index. A failed batch may be safely submitted again.
Resumable synchronization
Install the optional synchronization tables only when you use this integration:media-studio:search-index --configure. Then schedule:
API
nextCursor; cursors expire after15minutes, bind the query/user/workspace/index and stop at1000 candidate results. Ranking can change while the index changes, so this initial pagination is not a stable snapshot.
Returned names come from the authoritative database, not untrusted search payloads. Source access, trash state, entry revision and current version are checked again for each page. Index counts and unverified snippets are not returned. A page may therefore contain fewer results or none while still having a next cursor. The index is not an authorization system.
When Meilisearch is unavailable, this endpoint returns503 with a generic message. Ordinary SQL browsing remains available; Studio never falls back to unrestricted results. Responses are private/no-store. Source access may change after a response, so file delivery independently checks access again.