Get an account
Retrieve an account with its plan and current-period usage. Use it to watch screenshot consumption against the plan before it runs over.
Retrieve an account with its plan and current-period usage. Use it to watch screenshot consumption against the plan before it runs over.
Authenticate as a user with a personal access token.
Send it as a bearer token in the Authorization header:
Authorization: Bearer <personal-access-token>Personal access tokens act on behalf of the user that created them and are required by endpoints that perform user actions, such as reviewing builds and posting comments.
In: header
Path Parameters
Slug of the account to retrieve.
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/accounts/string"{ "id": "string", "slug": "string", "name": "string", "type": "user", "plan": { "name": "string", "includedScreenshots": -9007199254740991 }, "periodStartDate": "2019-08-24T14:15:22Z", "periodEndDate": "2019-08-24T14:15:22Z", "currentPeriodScreenshots": -9007199254740991, "includedScreenshots": -9007199254740991, "consumptionRatio": 0, "additionalScreenshotsCost": 0, "defaultUserLevel": "member"}List a test's changes GET
List the distinct changes a test produced over a period, the ones that came back most often first. Each change is one exact visual difference, with how many times it reappeared, whether it is ignored, and the diff of its latest occurrence — so you can look at what moved. A change that keeps reappearing while nothing in the UI changed is a flaky one: fix what makes it unstable, or silence it with `ignoreChange`. Use it to see what keeps changing in a flaky test.
Get the current user GET
Retrieve the user associated with the personal access token used to authenticate the request, along with their accessible accounts and GitHub linkage. Use it first in a conversation to learn which accounts, and so which owner slugs, this connection can reach.