← Back to use cases
Registration forms

Registration forms your platform controls

Example walkthrough: Eventfold is a fictional product and all numbers are sample data.

Create and sync registration forms from your server, let people fill them in with file uploads, and receive a signed callback with the registration fields when they finish.

Start freeView pricing
9:41●●● ▮
Eeventfold.example
Takes about 3 minutes

Which category are you registering for?

Secured by Eventfold

The phone is live — tap through the Eventfold survey.

Who it is for

Platforms that collect registrations for events, competitions, programs, or memberships under their own brand.

Server-side form syncRespondent formFile uploadsSigned completion callback

What you get

  • Registration forms without building a form engine
  • The fields you need, synced back to your backend
  • Documents and extra answers kept out of your database

Questions it answers

Can our backend create the form?How do we learn that someone registered?Where do uploaded documents live?
Product walkthrough

From a question to an experience inside your product

ResponseDock supplies the survey engine. Your application keeps the relationship, context, and visual identity.

Start with autumn tournament registration and combine choice, scale, text, consent, and logic-based questions. Structure, publishing, and versions live in one workspace.

Example product screens for the autumn tournament registration workflow, with sample data.

How it fits together

What you connect and what you get

Registration forms are managed server to server with a workspace secret key, available on Pro and above. Your platform creates and updates the form, including the fields it needs back. When someone submits, your backend can request a confirmation with those fields and receive a signed callback for each completed registration. Other answers and uploaded files stay in ResponseDock.

  1. 01

    What your app sends

    • Workspace secret key (server only)
    • Registration fields you need back
    • Callback URL for completions
  2. 02

    What you get

    • A themed registration form
    • Signed completion callbacks
    • Confirmed registration fields for your records
    • Full answers and files in ResponseDock results
  3. 03

    Good practice

    • Keep the secret key on your server
    • Ask only for the fields you need back
    • Verify the callback signature before trusting it
Your product, powered by ResponseDock

A survey engine, not another disconnected destination

Keep users inside your application while ResponseDock handles survey building, response collection, permissions, publishing, and results behind the scenes.

  • Theme filesColors, typography, logo, radius, buttons, options, width, and shadows.
  • Flexible surfacesInline embeds, modals, hosted surveys, and embedded management views.
  • Context-awareLink responses to the signed-in user, account, plan, or product event.
  • Controlled resultsKeep results private or expose a read-only public results experience.
product-feedback.ts
import { ResponseDock } from '@responsedock/sdk-browser';
import theme from './responsedock-theme.json';

ResponseDock.init({
  projectKey: 'pk_live_your_project',
  theme,
});

ResponseDock.identify({
  externalUserId: currentUser.id,
  traits: { plan: currentUser.plan },
});

ResponseDock.embed(
  'registration-forms',
  '#survey-container',
);