Append an immutable collection schema version
Append an immutable collection schema version - Rensei REST API operation reference.
AuthorizationBearer <rsk_live_*>Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.
collectionId*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidprojectId*string1 <= length <= 128application/json- body
expectedVersion*integer1 <= value <= 9007199254740991schema*indexEmbed?array<>items <= 32Success
application/json- response
indexEmbed*array<string>|nullid*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidorgId*stringprojectId*stringname*stringkeyField*stringretentionClass*stringagentWrite*string"none""append""write"schemaVersion*integer-9007199254740991 <= value <= 9007199254740991createdAt*string^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$date-timeschema?curl -X POST 'https://app.rensei.ai/api/collections/497f6eca-6276-4993-bfeb-53cbbbba6f08/schema?projectId=string' \ -H 'Content-Type: application/json' \ -d '{ "expectedVersion": 1, "schema": { "property1": "string", "property2": "string" }}'{ "indexEmbed": [ "string" ], "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "orgId": "string", "projectId": "string", "name": "string", "keyField": "string", "retentionClass": "string", "agentWrite": "none", "schemaVersion": -9007199254740991, "createdAt": "2019-08-24T14:15:22Z", "schema": { "property1": "string", "property2": "string" }}Read immutable record history, newest first
Read immutable record history, newest first - Rensei REST API operation reference.
Trigger credential rotation fan-out
Called by the operator (CLI or admin UI) after rotating an upstream credential (Vault, 1Password, encrypted DB row, …). Re-resolves the `(orgId, kind)` tuple via the credential provider registry and fans the fresh value out to every live `rotate-stream` SSE subscriber for that org. Zero live subscribers is not an error. Auth: `Bearer rsk_*` via `getCliOrSessionAuth`. The `orgId` in the body must match the authenticated org. For `session` / `user_token` auth the caller must have `admin` or `owner` role; for `api_key` auth the cross-tenant guard is sufficient. The audit write is deferred (`after()`) and failures are non-fatal - the fan-out already fired.