Save Responses
Use when: Your form needs to collect and store submitted answers.
Learn how to connect SurveyJS components to a PHP backend using Laravel. These working examples accompany the PHP integration guide and show the code behind each request. SurveyJS does not include a backend, so use these examples as a starting point for your application.
SurveyJS Form Library displays forms in the browser. Start with a PHP endpoint that saves submitted answers, then add the workflows your application needs.
Use when: Your form needs to collect and store submitted answers.
Use when: Your form needs user-specific data or previously saved answers.
Use when: Respondents need to complete a form across multiple sessions.
Use when: Your form allows respondents to upload files.
Use when: Choice lists come from data such as products, users, or offices.
Use when: Calculations or validation rules depend on data from your server.
Use when: You need to query answers with SQL or join them with other application data.
Use when: Several people need to fill out the same record together.
SurveyJS Dashboard lets users analyze responses with interactive charts in the browser. Your PHP backend supplies the saved responses.
Use when: Users need to explore and analyze collected responses.
Survey Creator lets users build and edit forms in the browser. Your PHP backend loads and saves form JSON schemas and checks that users have permission to make changes.
Use when: Users need to create or update forms in your application.
Use when: Form authors need to add logos, images, or other files.
Use when: Authors need to translate forms into multiple languages quickly.
Use when: Authors need to test form logic with sample variable values in the Preview tab.
Use when: Multiple authors need to edit the same form in real time.
Use a Node.js service alongside your PHP application to run SurveyJS workflows: validate responses, check form schemas, generate PDFs, and extract answers from documents.
Use when: Submitted answers must be checked on the server before they are saved.
Use when: You need to catch broken references and logic errors in form schemas.
Use when: Your backend needs PDFs for archiving, email attachments, or other workflows.
Use when: Completed forms arrive as paper scans, photos, or filled PDFs.