Verifications
Verify entities in bulk
Changed onAnswers many entity-and-period pairs in one call. Each entry is answered on its own merits: an entity the caller may not verify is returned under errors while the rest are still recorded, because eligibility depends on who owns each entity. Read errors on every response -- a 200 does not mean every entry was recorded.
put/api/v1/verifications
Request
- Base URLhttps://api.getcortexapp.com
- URLhttps://api.getcortexapp.com/api/v1/verifications
- AuthHTTP bearer
Request body
Example request
{
"verifications": [
{
"entity": "payments-api",
"periodCid": "vp0a1b2c3d4e5f6789",
"reason": "Ownership moved to the payments team",
"status": "VERIFIED_CORRECT"
}
]
}Response
The entries that were recorded, and the entries that were not
Example response
{
"errors": [
{
"code": "NOT_AN_OWNER",
"message": "You do not own this entity"
}
],
"verifications": [
{
"status": "VERIFIED_CORRECT",
"verifiedByApiKey": {
"name": "ci-bot"
}
}
]
}Changes
- info
endpoint added
- info