Index or refresh the vault
Trigger a scan (or a full deep scan) so new or edited vault content becomes searchable.
Who this is for: a workspace owner or platform operator (the scan grant).
The vault index is a local mirror — see the vault index. Nothing appears in search, performance, gaps, or dormant until it's been scanned in.
Trigger a scan
curl -X POST "https://app.tease.link/api/admin/vault/scan" \
-H "Authorization: Bearer $TEASE_API_KEY"| Query param | Description |
|---|---|
do_vision | Also run the vision tagger over freshly captured covers. |
deep | See Full deep scan below — engine (gateway) accounts only. |
{ "started": true, "already_running": false }A scan already in flight is a no-op: you get {"started": false, "already_running": true}
rather than a second scan stacking on top of the first.
Poll status
curl "https://app.tease.link/api/admin/vault/scan/status" \
-H "Authorization: Bearer $TEASE_API_KEY"{
"folders": 84,
"items": 5120,
"ai_tagged": 4870,
"last_indexed_ts": 1751280000,
"running": false,
"last_error": ""
}Poll until running flips back to false.
Full deep scan
The normal scan re-reads whatever's already been captured. deep=1 additionally asks the
engine to crawl your entire vault from scratch — every folder, every item — over its own
polling cadence.
curl -X POST "https://app.tease.link/api/admin/vault/scan?deep=1" \
-H "Authorization: Bearer $TEASE_API_KEY"{
"started": true,
"already_running": false,
"deep_requested": true,
"nonce": "a1b2c3...",
"requested_at": 1751280000
}Gateway-engine accounts only
A deep scan is an engine feature. If your account runs in OFAPI mode (no engine attached),
deep=1 returns 400 — there's nothing to drive the crawl. Use deep=0 there; a regular scan
still works.
What's next
Once items are indexed, find content to send, or clear the untagged pile with AI auto-tagging.