Forms

Forms

Programmatic access to Dailybot forms — list, filter, sort, search, submit responses with automation or anonymous modes, attach guest identities, transition through workflow states, and manage approval flows.

See the full endpoint reference — with parameters, request/response schemas, error codes, and code samples — at the interactive page: /developers/api/forms.

Every endpoint in this group accepts either an API key (X-API-KEY) or a CLI Bearer token (Authorization: Bearer …) unless explicitly marked otherwise, per the auth method matrix at /developers/authentication#parity-matrix.

Identifier

The Form and Form Response resources use a dedicated uuid field (RFC 4122 v4) as the canonical identifier in every request and response. Path parameters like /v1/forms/{uuid}/responses/{response_uuid}/ also use the uuid value.

Pagination

All list endpoints return the standard pagination envelope:

{
  "count": 42,
  "next": "https://api.dailybot.com/v1/forms/?offset=25&limit=25",
  "previous": null,
  "results": [...]
}

See /developers/conventions#pagination for the full spec.

Listing forms

GET /v1/forms/ returns every form in the caller’s organization (archived excluded by default). Capabilities — editing, response visibility, state changes — are governed by the form’s permissions; owner and org admins always have full access.

Supports filtering by scope, owner, searching by name, sorting, and date ranges.

Scope filters (?filter=):

Owner filter (?owner_user_ids=): Comma-separated user UUIDs (max 50). Returns only forms owned by those users. ANDs with every other parameter (search, filter, pagination, ordering). Cross-org UUIDs never match (returns 0 rows, not an error). Replaces the deprecated filter=me.

Sorting (?order=):

Use ?is_ascend=true to reverse the sort direction.

# Workflow forms, sorted alphabetically ascending
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/?filter=workflow&order=alphabetical&is_ascend=true"

# Search by name
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/?search=Access%20Request"

# Forms sorted by most responses
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/?order=total"

Including questions — pass ?include=questions to embed each form’s questions inline:

{
  "uuid": "...",
  "name": "Sprint Review",
  "questions": [
    {
      "uuid": "q-uuid-1",
      "label": "What did you accomplish?",
      "type": "text",
      "required": true,
      "options": null
    }
  ]
}

Discovering form owners

GET /v1/forms/form-owners/ returns a paginated, searchable list of org members who own at least one non-archived form. Only active, approved members appear. Ordered by full_name ascending.

Designed for UI pickers: a 1000-member org returns only its (typically few) form owners, not the whole member directory.

Each result contains uuid, full_name, image, and role (org role slug: ADMIN_ORG, MANAGER, ADMIN, MEMBER, GUEST).

Email visibility: the email field appears only when the caller has email visibility — org admins, managers, and team admins. Member-scoped callers receive rows without the email key (omitted entirely, never null). API keys inherit the key owner’s role. The search parameter still matches on email server-side for every caller, but the value is never echoed back to callers without visibility. Integrators must not assume email is present on picker rows.

# Search form owners by name
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/form-owners/?search=serg&limit=20"

# Filter forms list by owner
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/?owner_user_ids=<uuid-1>,<uuid-2>"

Deprecated fields:

• available_on_list_view — still accepted on POST /v1/forms/create/ and PATCH /v1/forms/{uuid}/config/ but is a server-side no-op. List visibility is now org-wide. To hide a form, archive it.
• filter=me — still works for backward compatibility but is deprecated. Use owner_user_ids with your own user UUID instead. When both are sent, they intersect. The me scoping on form responses endpoints is unrelated and not deprecated.

Both deprecated fields remain accepted indefinitely; removal (and the eventual column drop) will be announced as a separate changelog entry with its own migration window. Integrators should migrate now but nothing breaks on deploy day.

Migration note for integrators: replace filter=me with owner_user_ids=<your-uuid>. Clients that relied on available_on_list_view to hide forms must now filter client-side or archive the form.

Listing form responses

GET /v1/forms/{uuid}/responses/ returns the caller’s own responses by default. Pass ?all=true or any advanced filter to see all responses (requires VIEW_REPORTS permission on the form).

Permission model:

Submission source filter (?submission_sources=):

Every response belongs to exactly one of these four mutually exclusive categories:

Comma-separated values use OR semantics: ?submission_sources=automation,public returns automation OR public responses.

Approval flow filter (?flow_status=): One of pending, approved, denied. Silently ignored if the form has no approval flow.

Workflow state filter (?state=): Filter by workflow state key (e.g. draft, in_review, done). Returns 400 invalid_workflow_state if the form has no workflow.

Sorting (?order=): One of recent (default, newest first) or oldest.

Filter composition — all filters compose with AND across groups and OR within each group:

Results = (submission_sources OR)
  AND (submitter_user_ids OR)
  AND flow_status
  AND state
  AND search
  AND date_range

Search behavior — the search parameter searches across response content, member name/email, and guest name/email. Anonymous member identities are never searchable (privacy protection).

FORM_UUID="96bd8829-1d2a-40fe-8acf-7edb08f742dd"

# All responses
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/$FORM_UUID/responses/?all=true"

# Only automation submissions
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/$FORM_UUID/responses/?all=true&submission_sources=automation"

# Pending approval + member source + search
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/$FORM_UUID/responses/?all=true&submission_sources=member&flow_status=pending&search=bug"

# Oldest first with date range
curl -H "X-API-KEY: $DAILYBOT_API_KEY" \
  "https://api.dailybot.com/v1/forms/$FORM_UUID/responses/?all=true&order=oldest&start_date=2026-07-01&end_date=2026-07-10"

Submitting a form response

POST /v1/forms/{uuid}/responses/ creates a new response. The content field maps each question UUID to its answer value (strings, booleans, numbers, or arrays of scalars for multiple-choice).

Submission modes:

Guest identity — use guest_user to attach an external person’s identity (name and email) to automation submissions. Only accepted when automation: true; silently ignored otherwise. Required when the form has email_and_name_mandatory enabled. guest_user.full_name max 255 chars; guest_user.email valid email, max 254 chars.

Submission source — use submission_source (max 512 chars) to tag which automation or integration produced the response. Stored in response metadata and returned in list/detail views. Suggested values: "github-actions:deploy-pipeline", "zapier:feedback-sync", "cli:ci-release-bot", "make:onboarding-flow".

Validation rules:

• content is required and must contain answers matching the form’s questions
• guest_user requires automation: true — ignored otherwise
• If the form has email_and_name_mandatory=true and automation=true, both guest_user.full_name and guest_user.email must be provided
• Payload size limit: 64 KB maximum
• Answer values cannot be nested objects — lists must contain only scalars

# Automation mode with guest identity and source
curl -s -X POST \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  "https://api.dailybot.com/v1/forms/{uuid}/responses/" \
  -d '{
    "content": {"<question-uuid>": "Approved"},
    "automation": true,
    "guest_user": {"full_name": "Ops Bot", "email": "ops@company.com"},
    "submission_source": "workflow:on-call-handoff"
  }'

# Anonymous submission
curl -s -X POST \
  -H "X-API-KEY: $DAILYBOT_API_KEY" \
  -H "Content-Type: application/json" \
  "https://api.dailybot.com/v1/forms/{uuid}/responses/" \
  -d '{
    "content": {"<question-uuid>": "Honest feedback about the process"},
    "anonymous": true
  }'

Web app URLs for integrators