> ## Documentation Index > Fetch the complete documentation index at: https://docs.starleads.co/llms.txt > Use this file to discover all available pages before exploring further. # List the tests of an agent > Lists the tests of one of your agents with their latest run status. Use `kind` to keep only simulation or classification tests, and `folderId` on each test to know where it lives. ## OpenAPI ````yaml GET /AgentTest openapi: 3.0.1 info: title: Starleads public API documentation description: > Welcome to the Starleads Public API documentation. This API provides public access to Starleads services, allowing developers and growth-hackers to interact with campaign-related data. *** ### Base endpoint ```https://api.starleads.co``` *** ### Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. In case of failure, the body of the response will be JSON in the following format: ``` { "type": "https://tools.ietf.org/html/rfc7231#section-6.5.1", "title": "Bad Request", "status": 400, "detail": "No campaign exists with campaignId : 11111111" } ``` The ```type``` property is a link to a general description of the error type. *** ### Authentification Authentication for the API is handled with an API key that must be provided as a ```X-Api-Key``` header for every request.
**API keys are supposed to be a secret that only the client and server know. Please remember to not share them with anyone.**
You can find your API keys when authenticated in your Starleads profile :
![Api key menu option](../images/api-menu-option-screenshot.png) version: v1 x-logo: url: https://api.starleads.co/images/starleads-logo.png servers: [] security: [] tags: - name: Agent description: >- Manage your AI agent's prompt. These endpoints allow you to read and update the prompt that drives your agent's behavior during calls. - name: CampaignField description: >- CampaignFields enables users to specify customizable fields within their campaigns. These fields serve as placeholders (e.g., ```{lastname}```) that can be dynamically filled with corresponding data when creating prompts, providing flexibility in tailoring campaign content based on specific variables.
**Those are the keys of the ```databag``` field of the request payload to add a new ```CampaignItem``` to a campaign.** - name: CampaignItem description: Represents prospects entries related to a campaign - name: Consumption description: >- Track your company's credit consumption. These endpoints expose your current balance, usage and billing period so you can build budget monitoring on top of the API. - name: Subscription description: >- Inspect your subscription contract: the plan you are on, your subscription status, the features currently active and your effective limits. No pricing information is exposed. - name: AgentTest description: >- Tests of your agents: simulation tests (a simulated user talks to the agent and each success criterion is judged) and classification tests (the agent must produce the expected tag for a conversation). A test belongs to one agent. - name: AgentTestExecution description: >- Executions of agent tests: launching a set of tests, following their progress and cancelling them. One execution groups the runs created together for a list of tests, each repeated up to 5 times. - name: AgentTestFolder description: >- Folders grouping the tests of an agent (flat, with a name, a color and a markdown body). - name: AgentTestRun description: >- Runs of agent tests: one run is one attempt of one test inside an execution. Results, history and cancellation. - name: SimulationChat description: >- Test an agent through a text chat, exactly as it would behave in a real conversation (prompt, fields and connected tools included). Start a chat, then exchange messages with the agent. paths: /AgentTest: get: tags: - AgentTest summary: List the tests of an agent description: >- Lists the tests of one of your agents with their latest run status. Use `kind` to keep only simulation or classification tests, and `folderId` on each test to know where it lives. operationId: ListAgentTests parameters: - name: X-Api-Key in: header description: Api key to pass as a ```X-Api-Key``` request header. required: true schema: type: string - name: agentId in: query description: ID of the agent. required: true schema: type: string - name: kind in: query description: 'Only this kind of tests: Simulation or Classification. Omit for all.' schema: $ref: '#/components/schemas/AgentTestKind' responses: '200': description: Success content: application/json: schema: type: array items: $ref: '#/components/schemas/PublicAgentTestSummary' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ProblemDetails' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/ProblemDetails' components: schemas: AgentTestKind: enum: - Simulation - Classification type: string PublicAgentTestSummary: type: object properties: id: type: string nullable: true kind: $ref: '#/components/schemas/AgentTestKind' name: type: string nullable: true folderId: type: string description: Folder containing the test, null at the root nullable: true lastRunId: type: string description: Most recent run of the test, any status nullable: true lastRunStatus: $ref: '#/components/schemas/TestRunStatus' lastRunAt: type: string format: date-time nullable: true updatedAt: type: string format: date-time additionalProperties: false description: Summary of a test as returned when listing the tests of an agent ProblemDetails: type: object properties: type: type: string nullable: true title: type: string nullable: true status: type: integer format: int32 nullable: true detail: type: string nullable: true instance: type: string nullable: true additionalProperties: {} TestRunStatus: enum: - Queued - Running - Passed - Failed - Error - Cancelled type: string ````