Partitions

How a customer is named: an object in bodies, key=value in query strings.

One key

curl -G "https://app.concatflow.com/api/v1/assistants/$CONCATFLOW_ASSISTANT_ID/conversations" \
  -H "Authorization: Bearer $CONCATFLOW_API_KEY" \
  --data-urlencode "partition=customer_id=4712"

A partition names one customer. Its keys are the partition keys of the assistant’s isolation, such as customer_id. Its values come from your own session.

In a request body

POST /api/v1/embed/sessions takes an object:

{ "customer_id": "4712", "region": "eu" }

Values are strings. The keys must be exactly those of the isolation: a missing or an extra key fails with 403 partition_keys_mismatch.

In a query string

GET and DELETE on conversations take partition=key=value, several pairs joined with ,. URL-encode the whole value:

?partition=customer_id%3D4712
?partition=customer_id%3D4712%2Cregion%3Deu

Keys and values must not contain , or =. An unreadable value fails with 422 bad_partition.

Limits

What	Limit
Key	63 characters
Value	200 characters, not empty
partition query string	500 characters