> For the complete documentation index, see [llms.txt](https://docs.getscandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getscandium.com/api-testing/scheduling-and-monitoring.md).
# Scheduling and Monitoring
Scheduled API tests are tests that run at predefined times and intervals. For instance, you want to know at every hour if your APIs still work as expected.
To schedule API runs with Scandium, you need to [create an API suite](/api-testing/api-suites.md#create-a-new-test-suite). An API suite is a collection of multiple API tests. When you run this single suite, all test cases contained within the suite will run.
{% hint style="info" %}
To get the best out of your API tests, you should add [assertions](/api-testing.md#adding-assertions-to-api-requests) to each test case.
{% endhint %}
### How to schedule an API suite
To schedule an API suite, open the test suite you want to schedule by click on its name from the list of API suites you have created.
Click on the 'Schedule' button
From the ensuing modal, provide a name and description for the schedule, then set the frequency for which you want the suite to be run.
You can choose from the options hourly, daily, or specific days of the week.
Then click on the 'Save' button.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.getscandium.com/api-testing/scheduling-and-monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.