Events_ReadActivityDetails_Workspace
const url = 'https://dev-api.qualiastudios.dev/v1/accounts/example/workspaces/example/events/example:activityDetails';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://dev-api.qualiastudios.dev/v1/accounts/example/workspaces/example/events/example:activityDetails \ --header 'X-API-Key: <X-API-Key>'Reads bounded recorded targets after checking their current QDS access. (— api-linter: core::0131::synonyms=disabled aip.dev/not-precedent: a paged target projection, not a resource Get. —)
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The workspace id.
The event id.
Query Parameters
Section titled “Query Parameters ”Default 50, maximum 100 targets.
Independent target cursor, bound to the event and Activity policy version.
Responses
Section titled “ Responses ”OK
Recorded evidence, with current target metadata separately identified.
object
Recorded targets in immutable order, never a search of today’s selection.
One recorded episode reference. Content is returned only after GetEpisode authorizes the exact reference as the caller. An unavailable target retains only its recorded identifier; no reason, state or revision content escapes.
object
Immutable recorded reference.
Current readable episode number, not a historical label.
Current upload returned by QDS, not an inferred event-time source.
Missing or inaccessible, without claiming deletion.
Recorded ruling reason, at most 4096 characters.
Recorded previous review state, or empty when unknown.
Exact recorded edit revision. Absent when not recorded.
Exact recorded previous revision. Absent is unknown, not revision zero.
What a review decided on, captured in its transaction. Absent on reviews recorded before it was captured: never inferred from today’s episode.
object
The episode’s edit revision at the decision; 0 is the original recording. Absent when it was not recorded.
The upload the episode came from at the decision.
The content snapshot’s id at the decision (hex). An immutable reference, not a dataset version.
Canonical action identity.
Scope recorded by the producer.
Current authorized dataset name; empty when unavailable.
Current authorized dataset slug; empty when unavailable.
Empty when the recorded target list ends.
True when dataset access could not be established. Does not imply deletion.
Historical action membership was not recorded for these individual events.
Safe recorded field changes: dataset fields, or an episode task link that moved without a new revision. Never ingest configuration JSON.
An allowlisted scalar dataset field, with missing evidence kept distinct.
An episode’s linked_task uses task resource names, where empty means no task.
object
Known field path.
Recorded previous value; absent means unknown.
Recorded resulting value; absent means unknown.
True for a durable request manifest, even when its exact count is unknown.
Requested checks, without child run or findings counts.
Typed admitted re-ingest operation UUID, when recorded.
Example generated
{ "targets": [ { "episode": "example", "currentLabel": "example", "currentUpload": "example", "unavailable": true, "reason": "example", "previousState": "example", "revision": 1, "previousRevision": 1, "reviewContext": { "revision": 1, "upload": "example", "contentReference": "example" } } ], "event": "example", "dataset": "example", "currentDatasetLabel": "example", "currentDatasetSlug": "example", "nextPageToken": "example", "unavailable": true, "originalBatchUnknown": true, "changes": [ { "field": "example", "previous": "example", "current": "example" } ], "requestRecorded": true, "checks": [ "example" ], "admissionOperation": "example"}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}