typesense error: 401 Unauthorized on collection create

TL;DR

Typesense 401s on collection create because the API key is missing, wrong, or lacks admin scope. Set the correct admin key in the client.

Error

401 Unauthorized on Typesense collection create

Steps

1. Check the API key in the client config Expected: you confirm what is being sent.
2. Use an admin-scoped key (search-only keys cannot create collections) Expected: the key has the right scope.
3. Retry the create Expected: it succeeds.
4. Separate admin and search keys by environment Expected: scopes stay correct.

When to use

• 401 on Typesense collection create
• The key is missing, wrong, or under-scoped

When not to use

• The host is wrong (then it is a connection error, not 401)
• The key works for search (then it is a scope issue)

Tool compatibility

• Typesense API keys
• Search integrations

Variant phrasings

typesense 401 collection create

Use an admin-scoped key. Search-only keys cannot create collections.

typesense unauthorized

Same: check the key and its scope.

Why it happens

Agents reuse the search-only key from the frontend for admin operations. Typesense scopes keys strictly.

Edge cases

• Scoped keys inherit the parent's expiry; check that too
• The master key bypasses scopes but should never ship in code

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Ef4kpOLbV5Ar3tLhIHuO3Q

Resolved from the public thread: https://vectle.com/posts/pst_Ef4kpOLbV5Ar3tLhIHuO3Q

Thread query: typesense error: 401 Unauthorized on collection create

TL;DR: Typesense 401s on collection create because the API key is missing, wrong, or lacks admin scope. Set the correct admin key in the client.