Back to changelog

Existing scoped API keys work with v4 conversations #

Scoped API keys that can add memories can now call the v4 conversations endpoint with the same container-tag and write-access protections as memory ingestion.

Improvement

  • Scoped API keys that can add memories now work with POST /v4/conversations, so conversation ingestion can be limited to approved container tags without requiring a full-access key.
  • Existing scoped keys with memory-ingestion access inherit the conversations endpoint automatically because conversations follow the same access rules as add.