Get End-User Data
Endpoints
Get End-User Data
Read everything a Guru holds about one end user
GET
Get End-User Data
People who reach your Guru through a widget, a chat bot or the API do not have a
Gurubase account, so they cannot use the account tools to see or delete their data.
This endpoint is how the team running the Guru answers their access (GDPR Art. 15)
and erasure (Art. 17) requests. Which party is the controller for that data
depends on your deployment and your agreement with us; see the
privacy policy and your DPA rather than
treating this page as the answer.
Everything is scoped to the Guru in the path, so a key cannot reach another Guru’s
data even for the same end-user id.
Path Parameters
string
required
The Guru the end user interacted with
string
required
The identifier your integration supplied when the questions were asked
Headers
string
required
Your API key. You can obtain one from the Gurubase dashboard.
Reading their data
GET returns their questions, the questions the Guru declined to answer, their
conversations, their semantic searches, any stored profile, and any memories held
about them.
Results are paged. Each collection reports whether more remains, so keep raising
offset until every has_more is false: an access response has to be complete,
and stopping at the first page would understate what you hold. Memories come back
on the first page only.
integer
default:"100"
Records per collection, per page. Maximum 1000.
integer
default:"0"
How many records to skip.
profile is not paged. There is at most one per person per Guru, and it is the
most sensitive record here, so it is returned on every page rather than only the
first.
If the memory store cannot be read, the request fails with 500 rather than
returning a partial copy. An access response that silently omits data understates
what you hold, which is worse than an error you can retry.
To erase the same person’s data, see
Erase End-User Data.