Check API Availability
- Milly Bentzon
- Jul 8, 2022
- 2 min read
If you want to check whether a customer has a balance, you should use the check api. The API provides a list of accounts' balances, as well as the history of their checks. The id parameter specifies the check's id. If the id parameter is not specified, all checks on the account will be returned. If the id parameter is specified, you can get the history of all your customers' checks.
There are two modes for checking. Asynchronous and synchronous checks. Synchronous checks return results immediately, while asynchronous checks take a while to complete. Asynchronous checks return a PENDING or RUNNING response code. The Get results of a specific check will return results of a check run with an API or smart policy. When you run a synchronous check, the response will have a success code and a failure code.
The /checks/check API endpoint provides HTTP PATCH access for updating a check definition. You can specify the 'check-definition-url' attribute to specify a URL to the check definition and get the results. When a check is completed, you will receive a 201 Created response. If the check is not completed, it will return a PENDING response. You can execute more checks using the check api.
The check API works with the GitHub REST API. You can build integrations with it using GraphQL. The UI of GitHub is a bit limited. You can't customize the events it sends. But you can handle the Re-run all checks or Re-run failed checks. You can also post a comment directly in a PR file when your check runs successfully. To make this work, you must provide more details. You can also use zuul_return to return file comments.
SITES WE SUPPORT
SOCIAL LINKS
Opmerkingen