Pratik
623e33f2db
Adds the profile surface to both SDKs and documents it. Python (MemoryClient + AsyncMemoryClient) and TypeScript gain: get/generate profile, get/update settings, sample, regenerate. A profile's keys come from the customer's own JSON Schema, so the TS client keeps `profile` opaque and passes `schema` through untouched in both directions. Camel-casing them would return field names that do not match the schema the customer wrote. Reads use the v2 envelope, where a known entity with no profile yet is a 200 carrying a status rather than a 404, so an empty state is distinguishable from an error. Verified against a live environment running this API: settings round-trip, a partial update leaves the schema intact, generation produces a profile under the configured schema, and sample, regenerate, cooldown and the 400/404 paths all answer as documented.
6 lines
203 B
Plaintext
6 lines
203 B
Plaintext
---
|
|
title: 'Generate Profile'
|
|
description: "Generate or refresh the profile for a single user or agent immediately, instead of waiting for the message threshold."
|
|
openapi: post /v2/profiles/trigger/
|
|
---
|