Example Response

{
    "code": 1200,
    "message": "Template cannot be saved."
    "detail": "Type mismatch: scope is undefined"
}

Error codes

Learn more about how to manage errors in the following sections:

Example Response

{"code":3200,"message":"Resource Not Found","details":"http:\/\/myfsp.com\/docs\/errorcodes\/404"}

Error Codes

Displaying custom errors from your FSP API

You can return custom errors from your application that will be displayed in the file manager.

To do that we reserved codes from 3900 to 3999. An error sent with an error code number in this range displays the message as the error title and the details as the error text.

Example:

1. Your file storage doesn’t support file names with the character “?”

2. The front end doesn’t stop the upload, as this character is allowed by other APIs and storages

3. When your API gets the file, returns the following error: Code: 39105 HTTP Status: 400 Message: Upload error Details: The file name is not allowed. Please make sure it does not contain one or more of these characters: \ / < > ? |

4. The file manager inside the editor displays:

The onWarning callback returns information about a soft error that doesn’t impact the normal usage of the builder. You can use this callback to track these errors, display a message or change any behavior in your application. The callback manages JSON as the output data format.

Configuration

To handle these warnings, add the onWarning callback to :

Response

Example

Warning codes

onError callback

The onError callback returns information about the application errors. You can use this callback to track these errors, display a message or change any behavior in your application. The callback manages JSON as the output data format.

Configuration

Response

Example

OnInfo Callback

Response

Example Response on prompt generation

Here’s an example of the data you can expect when the user asks to generate content:

Example Response on prompt apply

Here’s an example of the data you can expect when the user applies AI-generated content:

Example Response

Error Codes

Authentication errors

Preliminary JSON parsing errors

1: In case of a Bump error, the JSON parser forwards to the user the error code it receives from the Bump.

JSON Pre-processing errors

HTML Creation errors

1: Additional details are provided, depending on the error that the content worker is reporting.

2: Additional details are provided, depending on the form field that missed validation.

Post-processing errors