If you've just created an account for your team, you'll want to invite the other users on your team as soon as possible on the users page.

A default service, escalation policy, schedule and token have been created for you already in order to make getting started a little easier. Once you've got the hang of things, you can customize those as well as create your own. As you add users to your team, you can assign them to various schedules.

Let's trigger your first alert. You can use curl(1) if you like:

curl -v -X POST https://ttyops.com/api/v1/alert \
  -H "Authorization: Bearer <api token>" \
  -H "Content-Type: application/json" \
  -d '{"alerts": [{"fingerprint": "testing", "status": "firing", "labels": {"alertname": "Welcome to TTYops!", "service": "default"}}]}'

There's now an active alert for your team. Whoever is on-call has already been contacted. If you're logged in, you'll notice that a token has already been filled in for you. Tokens can be created and deleted from the team section of the dashboard. The token above is the default token created for your team when the team was created.

Within the JSON payload, the fingerprint uniquely identifies an alert so that it can be resolved later (see alerts for more information). The service label ensures that the alert is associated with the right service for your team. Each service specifies one or more escalation policies, and, in turn, each escalation policy specifies a rotation schedule – the user currently assigned the rotation assigned to the alert and contacted when it fires.

Instead of firing alerts by hand, you can set up integrations that automate the creation of alert from various other systems or services.

The next section of the docs are about teams.