Integrate SurveyJS Libraries with Backend

SurveyJS are client-side libraries that work in a web browser. You can think of them as building blocks that you can insert anywhere in your application to create a frontend for your survey management system. Developers can integrate SurveyJS with any server-side framework and database to build a backend for this system. This help topic describes the main aspects that should be taken into account when you integrate SurveyJS with your backend.

Client–Server Interaction

To communicate with the server, SurveyJS libraries use JSON objects. The following diagram illustrates the communication process:

SurveyJS Interaction with Backend

SurveyJS libraries send and receive two types of JSON objects:

  • Survey schema
    Contains a survey model that describes the survey structure. The survey model can contain pages, panels, and questions.

  • Survey result
    Contains a respondent's answers to survey questions.

Your backend development team should implement server-side code that stores these JSON objects in a database and delivers them to and from the client side.

Server-Side Implementation

Backend implementation is a custom development task that lies beyond the application scope of SurveyJS libraries. However, we can highlight implementation aspects that guarantee successful SurveyJS integration.


Design a REST API endpoint that accepts JSON data in requests and sends JSON data in responses.

User Authentication and Authorization

To authenticate a user that sends a request, determine their identity. To authorize the user, determine the resources that they can access. Prevent users from accessing API operations outside their predefined roles.

Data Validation and Sanitization

Validate API calls and sanitize user input to prevent cross-site request forgery (CSRF), cross-site scripting (XSS), and SQL injection (SQLi) attacks.

Survey Data Storage

A survey management application should include a database to store survey schemas and results. Depending on your business needs, you can build an on-premises data storage or host data in a cloud service.

In the simplest case, the database can include two tables: one for survey schemas and one for survey results. The tables should have a one-to-many relationship (one schema to many survey results) and can have the fields described below.


  • id - A unique identifier of a survey schema.
  • content - A JSON object or text string that contains the survey schema.


  • id - A unique identifier of a survey result.
  • survey_schema_id - A required field that refers to
  • content - A JSON object or text string that contains the survey result.

Each database can also have additional fields as required. For example, if you need to track who and when created or changed a survey schema, you can add the createdAt, createdBy, changedAt, and changedBy fields to the SurveySchemas table.

The following table illustrates permissions that each SurveyJS component needs for correct operation:

SurveyJS Component SurveySchemas SurveyResults
Form Library Read Create
Survey Creator Create / Read / Update -
Dashboard Read Read
PDF Generator Read Read

Note that SurveyJS Dashboard needs to read one record from SurveySchemas and all records with the same survey_schema_id from SurveyResults. SurveyJS PDF Generator needs to read one record from SurveySchemas and, optionally, one record with a desired result from SurveyResults.


Although SurveyJS does not offer production-ready backend solutions, you can refer to the following page for free examples that can be used as a starting point to implement a full-cycle survey management system on your premises: Backend Integration Examples.

Copyright © 2022 Devsoft Baltic OÜ. All rights reserved.

Why we use cookies.

This site uses cookies to make your browsing experience more convenient and personal. Cookies store useful information on your computer to help us improve the efficiency and relevance of our site for you. In some cases, they are essential to making the site work properly. By accessing this site, you consent to the use of cookies.

For more information, refer to DevSoft Baltic’ privacy policy and cookie policy.