Department of Better Technology
The Department of Better Technology (DOBT), founded in 2013 by former Presidential Innovation Fellows and later acquired by CityBase, builds Screendoor — a form-building and submission- management platform used by government agencies and organizations such as ProPublica, the Los Angeles Times, the Consumer Financial Protection Bureau, and the Ford Foundation to run paperless intake, evaluation, and approval workflows. The Screendoor REST API programmatically manages sites, projects, forms and form fields, workflow statuses, labels, responses (submissions), response labels, and reviewer assignments, using API-key authentication, offset pagination with RFC 5988 Link headers, and an explicit API version.
Department of Better Technology publishes 8 APIs on the APIs.io network, including Files API, Forms API, Labels API, and 5 more. Tagged areas include Company, Forms, Government, GovTech, and Civic Technology.
Department of Better Technology’s developer surface includes documentation, API reference, support, engineering blog, signup flow, authentication, and 17 more developer resources.
Kin Score
APIs 8
Individual APIs this provider publishes, each with its own machine-readable definition.
Department of Better Technology Files API
Upload files referenced by response fields.
Department of Better Technology Forms API
Manage the form fields collected for a project.
Department of Better Technology Labels API
Manage labels used to tag responses within a project.
Department of Better Technology Projects API
Manage projects (forms and their workflow) within a site.
Department of Better Technology Response Assignments API
Assign users or teams to an individual response.
Department of Better Technology Response Labels API
Attach or detach labels on an individual response.
Department of Better Technology Responses API
Create, read, update, trash, and recover form submissions.
Department of Better Technology Statuses API
Manage the status workflow stages for a project's responses.
Scroll for all 8
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
department-of-better-technology-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type