From an internal customer request.

Note: Perhaps we can clean up https://github.com/grafana/synthetic-monitoring-api-go-client/blob/main/docs/API.md and make the steps to create the keys/tokens more clear to help users in future

We need to clean up documentation to make it clear which API instance needs to be used.

No executable is included in repository and running make command not producing any executable.

There is a need for use case example to demonstrate where and when this client can be used.
Can this client be used as a stand alone client, or it is writtent to be used part of Grafana Cloud only ?

Now that there's a command to interact with the API, sm-client, it would be nice for it to take JSON as input in order to create and update checks.

This was mentioned in #31

I wonder if using this library and the documented REST API is the right approach for automating the creation of checks as a Grafana Cloud user.

Specifically, I try to understand the implications of calling /api/v1/register/install. Is this required if I have a program that wants to interact with the endpoints under /api/v1/check? And should a new token be required for every subsequent run, or is calling /install a one-time process? Also, what is the reason to not use the Grafana API token directly for the authentication of the other endpoints?

In case this library and the API are for internal use only, feel free to close this issue. Since this API is referenced in the official docs, I thought this would be a good starting point to automate the creation of checks.

• /api/v1/register/install
• /api/v1/check/add
• /api/v1/check/update
• /api/v1/check/delete/:id:
• /api/v1/check/list
• /api/v1/probe/add
• /api/v1/probe/update
• /api/v1/probe/list
• /api/v1/probe/delete/:id:
• /api/v1/tenant/update
• /api/v1/tenant/delete/:id:

Deprecated, removed:

• /api/v1/register/init
• /api/v1/register/save
• /api/v1/register/viewer-token
• /api/v1/register/describe