FMLDevelopers

Errors

An error shows first in its HTTP status: 400 for an incomplete request, 401 for a refused key or token, 404 when something isn't found, 500 when something broke on our side. The body takes one of these two forms.

Refused key or token

When the key, the login or the token is refused, the request stops before the endpoint. The message starts with the error code:

HTTP
HTTP/1.1 401 Unauthorized

{"error": "102 - Invalid API key."}

Endpoint errors

Other errors use the usual response shape: the message is in data, without its code. Rely on the HTTP status, and show the message as is if needed.

HTTP
HTTP/1.1 404 Not Found

{"data": ["Article not found."], "meta": {}}

Codes and messages

CodeMessage
1No article provided.
2Article not found.
3No article content provided.
4Article content must be between 20 and 300 characters long.
5No comment content provided.
6Comment not found.
7No comment content provided.
8Comment content must be between 20 and 300 characters long.
9Missing parameter
10This user not found.
11This username is already associated with an account.
12This email is already associated with an account.
13This email is not valid.
14About me content can not exceed more 300 characters long.
15The file is too large. Allowed maximum size is 1 MB.
16Field confirm_password is missing.
17The password fields must match.
18You have already liked this user.
21You need to provide an email address
23Article already voted
25Invalid subject provided
26Invalid message provided
27Image not found.
28Badge not found.
29Provided vote type is invalid
30Missing datas for twitter connect
31User already liked this post
32User account is banned
33User does not own comment
34You need to validate your account, check your emails.
35Missing datas for facebook connect
99Unknown error
100You must be authenticated in order to access this function.
102Invalid API key.
103Invalid login credentials.
104Invalid or expired API token.