{ "opencollection": "1.0.0", "info": { "name": "Braintrust Acls Logs API", "version": "1.0.0" }, "request": { "auth": { "type": "bearer", "token": "{{bearerToken}}" } }, "items": [ { "info": { "name": "Logs", "type": "folder" }, "items": [ { "info": { "name": "Insert project logs events", "type": "http" }, "http": { "method": "POST", "url": "https://api.braintrust.dev/v1/project_logs/:project_id/insert", "params": [ { "name": "project_id", "value": "", "type": "path", "description": "Project id" } ], "body": { "type": "json", "data": "{}" }, "auth": { "type": "bearer", "token": "{{bearerToken}}" } }, "docs": "Insert a set of events into the project logs" }, { "info": { "name": "Fetch project logs (GET form)", "type": "http" }, "http": { "method": "GET", "url": "https://api.braintrust.dev/v1/project_logs/:project_id/fetch", "params": [ { "name": "project_id", "value": "", "type": "path", "description": "Project id" }, { "name": "limit", "value": "", "type": "query", "description": "limit the number of traces fetched\n\nFetch queries may be paginated if the total result size is expected to be large (e.g. project_logs which accumulate over a long time). Note that fetch queries only support pagination in descending time order (from latest to earliest `_xact_id`. Furthermore, later pages may return rows which showed up in earlier pages, except with an earlier `_xact_id`. This happens because pagination occurs over the whole version history of the event log. You will most likely want to exclude any such duplicate, outdated rows (by `id`) from your combined result set.\n\nThe `limit` parameter controls the number of full traces to return. So you may end up with more individual rows than the specified limit if you are fetching events containing traces." }, { "name": "max_xact_id", "value": "", "type": "query", "description": "DEPRECATION NOTICE: The manually-constructed pagination cursor is deprecated in favor of the explicit 'cursor' returned by object fetch requests. Please prefer the 'cursor' argument going forwards.\n\nTogether, `max_xact_id` and `max_root_span_id` form a pagination cursor\n\nSince a paginated fetch query returns results in order from latest to earliest, the cursor for the next page can be found as the row with the minimum (earliest) value of the tuple `(_xact_id, root_span_id)`. See the documentation of `limit` for an overview of paginating fetch queries." }, { "name": "max_root_span_id", "value": "", "type": "query", "description": "DEPRECATION NOTICE: The manually-constructed pagination cursor is deprecated in favor of the explicit 'cursor' returned by object fetch requests. Please prefer the 'cursor' argument going forwards.\n\nTogether, `max_xact_id` and `max_root_span_id` form a pagination cursor\n\nSince a paginated fetch query returns results in order from latest to earliest, the cursor for the next page can be found as the row with the minimum (earliest) value of the tuple `(_xact_id, root_span_id)`. See the documentation of `limit` for an overview of paginating fetch queries." }, { "name": "version", "value": "", "type": "query", "description": "Retrieve a snapshot of events from a past time\n\nThe version id is essentially a filter on the latest event transaction id. You can use the `max_xact_id` returned by a past fetch as the version to reproduce that exact fetch." } ], "auth": { "type": "bearer", "token": "{{bearerToken}}" } }, "docs": "Fetch the events in a project logs. Equivalent to the POST form of the same path, but with the parameters in the URL query rather than in the request body. For more complex queries, use the `POST /btql` endpoint." }, { "info": { "name": "Fetch project logs (POST form)", "type": "http" }, "http": { "method": "POST", "url": "https://api.braintrust.dev/v1/project_logs/:project_id/fetch", "params": [ { "name": "project_id", "value": "", "type": "path", "description": "Project id" } ], "body": { "type": "json", "data": "{}" }, "auth": { "type": "bearer", "token": "{{bearerToken}}" } }, "docs": "Fetch the events in a project logs. Equivalent to the GET form of the same path, but with the parameters in the request body rather than in the URL query. For more complex queries, use the `POST /btql` endpoint." }, { "info": { "name": "Feedback for project logs events", "type": "http" }, "http": { "method": "POST", "url": "https://api.braintrust.dev/v1/project_logs/:project_id/feedback", "params": [ { "name": "project_id", "value": "", "type": "path", "description": "Project id" } ], "body": { "type": "json", "data": "{}" }, "auth": { "type": "bearer", "token": "{{bearerToken}}" } }, "docs": "Log feedback for a set of project logs events" } ] } ], "bundled": true }