List agent requests
curl --request GET \
--url https://api.slash.com/agent-request \
--header 'X-API-Key: <api-key>'{
"items": [
{
"id": "<string>",
"display": {
"title": "<string>",
"sections": [
{
"label": "<string>",
"value": "<string>"
}
],
"description": "<string>"
},
"createdAt": "2023-11-07T05:31:56Z",
"result": {}
}
],
"metadata": {
"nextCursor": "<string>",
"count": 123
}
}Agent Requests
List agent requests
List all agent requests created by this API key.
Agent requests are created when a read-only API key makes a write request (POST, PUT, PATCH, DELETE) to the Public API. This endpoint returns all such requests, paginated.
GET
/
agent-request
List agent requests
curl --request GET \
--url https://api.slash.com/agent-request \
--header 'X-API-Key: <api-key>'{
"items": [
{
"id": "<string>",
"display": {
"title": "<string>",
"sections": [
{
"label": "<string>",
"value": "<string>"
}
],
"description": "<string>"
},
"createdAt": "2023-11-07T05:31:56Z",
"result": {}
}
],
"metadata": {
"nextCursor": "<string>",
"count": 123
}
}Authorizations
API key authentication for public API requests.
Keys come in two flavors:
- Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashboard under a specific entity; every request acts on that entity.
- User-scoped keys are pinned to a user and span every legal
entity that user has access to. Every request made with a
user-scoped key (except
GET /legal-entity, which lists the legal entities the user can access) must include anx-legal-entityheader naming the legal entity the request is operating on. Requests without the header are rejected with400. The authenticated user must have an active permission role on the supplied legal entity, otherwise the request is rejected with403.
Query Parameters
A cursor string to fetch the next page of results
Filter by request status
Available options:
pending, approved, rejected, expired, executed, failed, running ⌘I