1
Choose the integration job
Decide whether the integration needs form access, submission access, or both.
Scoped integrations
Connect form workflows with narrow API surfaces
KinoForms gives developers scoped API-key surfaces for embedded and programmatic form workflows while keeping form access and submission access distinct.
Problem
Integrations should not need broad product access
External systems often need a narrow job: read a form, write a form, read submissions, or submit data programmatically.
API scopes that match form and submission work
KinoForms separates API key surfaces so integrations can map to the task instead of sharing one broad account credential.
- forms:read for retrieving form configuration
- forms:write for form-management integrations
- submissions:read for response review integrations
- submissions:write for programmatic submission flows
Use cases
Where this page fits
These examples keep the page focused on narrow form-workflow intent instead of broad form-builder copy.
Embed a published form in another interface
Sync submitted records to an internal system
Create submission flows from a known workspace
Separate form management from response review
Workflow steps
How the workflow moves
Use scoped form and submission API surfaces when integrations need a narrow, review-aware connection.
2
Assign the narrow scope
Use the form and submission read/write scopes that match the job.
3
Keep review context intact
Connect systems without removing the submission from its owning form and workspace.
Concrete examples
What this looks like in a form
Submission export integration
An integration can read submitted responses without changing form-builder configuration.
Embedded form workflow
A programmatic surface can read form configuration and submit responses for a known workspace.
Write-only intake handoff
A partner workflow can create submissions through a write scope while internal reviewers keep read and edit access inside KinoForms.
Related pages
Follow the connected form workflow
role-aware form access
Understand how API scopes fit alongside team and workspace roles.
controlled form submissions
Follow submitted records after an integration creates or reads them.
vendor onboarding form template
Use scoped integrations for vendor data workflows.
form submission validation
Keep API-created records aligned with field and workflow validation.
FAQ
Common questions
What API scopes does KinoForms describe?
The public pages describe separate scopes for forms:read, forms:write, submissions:read, and submissions:write.
Why use scoped API keys for form integrations?
Scoped keys let integrations map to a narrower form or submission job instead of using broad product access.
Next step
Connect systems without flattening the workflow
Use scoped form and submission API surfaces when integrations need a narrow, review-aware connection.