Docs

Start here

Ask for a report's proof-of-work challenge

POST/v1/community/reports/challengeon https://api.auray.ai/v1

The puzzle an anonymous report pays.

The puzzle an anonymous report pays. Find a nonce such that sha256("<salt>.<nonce>") begins with bits zero bits, then send the challenge string back unchanged with your nonce in the body of POST /v1/community/reports. One challenge is one report, and it expires after expires_in seconds. The Community hands these out itself, so reporting never waits on support being open; it is the same puzzle as POST /v1/support/challenge, at the difficulty our team sets for both. A report sent with a key solves none. A POST rather than a GET because a cached challenge is one salt handed to everybody.

#Authentication

No key needed, and none is read: it is the puzzle an anonymous report pays. Paced per address, and answered while support is closed.

#Example request

curl -X POST https://api.auray.ai/v1/community/reports/challenge

#Responses

#200 OK

OK

FieldTypeRequiredDefaultDescription
objectstringyes—One of "challenge".
challengestringyes—Signed. Send it back byte for byte; any change is refused by one comparison.
saltstringyes—A convenience copy of the field inside challenge; the server reads the signed one.
bitsintegeryes—Leading zero bits required. Raised during an incident, so read it rather than assuming.
expires_inintegeryes—Seconds.
algorithmstringyes—One of "sha256-leading-zero-bits".
request_idstringno—Mirrored in the X-Request-Id header.

Headers:

HeaderDescription
RateLimit-LimitBurst capacity for the bucket that answered.
RateLimit-Remaining
RateLimit-ResetSeconds until refill.
X-Request-Id

#429 Too Many Requests

#503 Service Unavailable

#Status codes

StatusMeaning
200OK
429Too Many Requests
503Service Unavailable

Every refusal names its code, and every code is explained at Errors.

Start typing to search every page of the documentation.

Up arrow Down arrow to moveEnter to openEscape to close