Grafana Cloud k6
Connect your client's Grafana Cloud k6 with a key they paste, and call its API through Operate As.
- Website
- k6.io
- Connects by
- Pasting a API token
- Category
- Developer tools
- Services
- 1
- Tools
- Pass-through only
| Service | Key | Base URL |
|---|---|---|
| Grafana Cloud k6 | grafana-k6 | https://api.k6.io/cloud/v6 |
Your client also types their stack id (Shown in Grafana Cloud k6's settings, API token page).
Connecting
Your client makes a API token in their Grafana Cloud k6 settings and pastes it on their link. Operate As tries it with Grafana Cloud k6 before saving it, and stores it encrypted. See Services connected with an API key.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "grafana-k6" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| Use the Grafana Cloud k6 key you paste, with only the access you gave that key | Chosen on the provider's screen |
Pass-through
Grafana Cloud k6 has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.
Add the client
In Clients, add your client and select Grafana Cloud k6. Then send them their link.
Your client connects
They paste a API token from their Grafana Cloud k6 settings.
Find the endpoint
Pick the call from Grafana Cloud k6's own API docs. Your path is everything after https://api.k6.io/cloud/v6.
Send it through Operate As
Use the client's ID, the service key grafana-k6 and that path. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../grafana-k6/projects" \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
A key works until your client deletes it in Grafana Cloud k6. They can paste a new one on the same link at any time, and your workflows carry on without changes.
See Keeping access alive and Removing access.
{ "status": 401, "data": { "…": "the service's own error" }, "encoding": "json"}