Migrate organization settings to v5

​

Migration details

​

Endpoint mapping

​

Read organization settings

GET /organization

{
  "organizationalContext": "Acme builds security tools for enterprises",
  "namespaceCount": 42
}

​

Update organization context

PATCH /v3/settings
{"filterPrompt":"Acme builds security tools for enterprises"}

PATCH /organization
{"organizationalContext":"Acme builds security tools for enterprises"}

​

With the SDK

const settings = await client.settings.get()
await client.settings.update({ filterPrompt: "Acme builds security tools for enterprises" })

const { organizationalContext, namespaceCount } = await supermemory.organization.get()

await supermemory.organization.update({
  organizationalContext: "Acme builds security tools for enterprises",
})

​

Removed public operations

• Organization profile-bucket mutation is not exposed through organization settings.
• Bucket suggestion is not part of v5.
• Organization data reset is not part of v5.
• Namespace-owned profile buckets are managed through /ns/{namespace}/profile/buckets.

​

Verification

• Compare the v5 context with the legacy filterPrompt before cutover.
• Set, replace, and clear organizational context.
• Confirm namespaceCount agrees with pagination.totalItems from GET /namespaces for the same credentials.
• Verify non-admin callers receive 403 on PATCH.
• Confirm removed fields are not required by downstream configuration code.