Department of Better Technology Response Assignments API

Assign users or teams to an individual response.

Operations 5

GET /responses/{response_id}/assignments List a response's assignees #
POST /responses/{response_id}/assignments Add assignees to a response #
PUT /responses/{response_id}/assignments Replace a response's assignees #
DELETE /responses/{response_id}/assignments Remove all assignees from a response #
DELETE /responses/{response_id}/assignments/{assignment_parameter} Remove an assignee from a response #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/department-of-better-technology-response-assignments-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

department-of-better-technology-response-assignments-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Screendoor Files Response Assignments API
  description: The Screendoor API from the Department of Better Technology (CityBase Screendoor) lets you programmatically manage online forms, submissions ("responses"), evaluation workflows, statuses, labels, and assignments. Screendoor is used by government agencies and organizations to build paperless forms and manage intake, review, and approval processes. All endpoints are relative to the base URL and authenticated with an API key passed as the `api_key` URL parameter.
  version: '1'
  contact:
    name: Department of Better Technology (CityBase)
    url: https://help.dobt.co/
  x-api-version-header: 'Api-Version: 1'
  x-provenance:
    generated: '2026-07-18'
    method: generated
    source: https://dobtco.github.io/screendoor-api-docs/
servers:
- url: https://screendoor.dobt.co/api
  description: Screendoor production API
security:
- apiKeyAuth: []
tags:
- name: Response Assignments
  description: Assign users or teams to an individual response.
paths:
  /responses/{response_id}/assignments:
    parameters:
    - $ref: '#/components/parameters/ResponseId'
    get:
      operationId: listResponseAssignments
      summary: List a response's assignees
      tags:
      - Response Assignments
      responses:
        '200':
          description: The users/teams assigned to the response.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Assignee'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
    post:
      operationId: addResponseAssignments
      summary: Add assignees to a response
      description: Adds assignees. Each entry has the form "Type,id" (e.g. "User,10").
      tags:
      - Response Assignments
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AssigneeNames'
      responses:
        '200':
          description: The updated set of assignees.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Assignee'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '422':
          $ref: '#/components/responses/UnprocessableEntity'
    put:
      operationId: replaceResponseAssignments
      summary: Replace a response's assignees
      tags:
      - Response Assignments
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AssigneeNames'
      responses:
        '200':
          description: The replaced set of assignees.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Assignee'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '422':
          $ref: '#/components/responses/UnprocessableEntity'
    delete:
      operationId: removeAllResponseAssignments
      summary: Remove all assignees from a response
      tags:
      - Response Assignments
      responses:
        '204':
          description: All assignees were removed.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
  /responses/{response_id}/assignments/{assignment_parameter}:
    parameters:
    - $ref: '#/components/parameters/ResponseId'
    - name: assignment_parameter
      in: path
      required: true
      description: The assignee identifier in "Type,id" form.
      schema:
        type: string
    delete:
      operationId: removeResponseAssignment
      summary: Remove an assignee from a response
      tags:
      - Response Assignments
      responses:
        '204':
          description: The assignee was removed.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  schemas:
    Assignee:
      type: object
      properties:
        type:
          type: string
          enum:
          - User
          - Team
        id:
          type: integer
        name:
          type: string
    ValidationError:
      type: object
      properties:
        error:
          type: string
        errors:
          type: object
          description: Map of field name to an array of validation messages.
          additionalProperties:
            type: array
            items:
              type: string
    AssigneeNames:
      type: object
      required:
      - assignees
      properties:
        assignees:
          type: array
          description: Each entry has the form "Type,id" (e.g. "User,10").
          items:
            type: string
    Error:
      type: object
      properties:
        error:
          type: string
          description: A human-readable error message.
  parameters:
    ResponseId:
      name: response_id
      in: path
      required: true
      description: The id of the response.
      schema:
        type: integer
  responses:
    UnprocessableEntity:
      description: The request was well-formed but failed validation.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ValidationError'
    Unauthorized:
      description: The API key is missing or invalid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: The requested resource was not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: query
      name: api_key
      description: Your Screendoor API key, obtained in Screendoor under Settings -> API Keys, passed as the `api_key` URL parameter on every request.