Skip to content

Commit d600ed0

Browse files
committed
Update possible Risk Intelligence /retrieve error codes
1 parent eb880ba commit d600ed0

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

docs/risk-intelligence/getting-started/retrieve.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,13 @@ Below is a list of possible values for `error_code`. **If you are seeing status
7070
| `auth_required` | 401 | You forgot to set the `X-API-Key` header. |
7171
| `auth_invalid` | 401 | The API key you provided was invalid. |
7272
| `sitekey_invalid` | 400 | The sitekey in your request is invalid. |
73-
| `token_missing` | 400 | You forgot to add the token parameter. |
74-
| `token_expired` | 400 | The response has expired. |
73+
| `token_missing` | 400 | The token parameter is missing or empty. |
7574
| `bad_request` | 400 | Something else is wrong with your request; e.g. your token is invalid. |
75+
| `token_invalid` | 200 | The token is invalid (e.g., associated with a different account). |
76+
| `token_expired` | 200 | The token is expired. |
77+
78+
:::warning Note
79+
80+
Status code **200** does not necessarily mean that the token was successfully used to retrieve Risk Intelligence data; it just means that the API was able to handle it. Check the `success` field.
81+
82+
:::

0 commit comments

Comments
 (0)