ioZen Docs

Changelog

API changes and updates.

2026-03-10

Content Blocks & Template Variables

  • Content blocks in intake bot schema — The GET /intake-bots/:id response now includes content block items alongside question fields in schema.fields. Content blocks have kind: "content" and do not accept user input; they display content between questions during the intake flow. See the Schema Items guide for how to handle both item types.
  • Template variables — Question labels, helper text, and content block bodies can contain {{field_name}} references that resolve to the respondent's previous answers at runtime. When reading a schema via the API, these placeholders appear as-is. See the Template Variables guide for the syntax and scoping rules.
  • AI-generated content blocks — Content blocks with content_type: "ai_generated" are generated at runtime during the intake session. The body field in the schema contains the author's prompt, not the generated output. Generated content is stored per-submission in the conversation history.
  • v1 API schema response updatedschema.fields now uses a union type: items are either a field object (has type) or a content block object (has kind: "content"). Existing integrations that only read field objects are unaffected — unknown kind values should be skipped.

2026-02-25

v1 API Launch

  • Initial release of the ioZen Public API v1
  • Endpoints: Intake Bots, Submissions, Webhooks
  • API key authentication with scopes
  • Rate limiting per plan tier
  • Webhook event delivery via QStash
  • Interactive API documentation at /docs

On this page