Skip to main content
Forward Mode is the managed delivery layer built on top of Build Mode. Administrators predefine the agent shape and available resources through a three-tier configuration model (enterprise / template / identity), and callers simply pass a template_id and identity_id to use an agent — without managing the underlying runtime. Forward Mode ships with built-in IM channel integration, scheduled triggers (Schedules), and end-user identity isolation (Identities), making it a good fit for SaaS providers, integrators, and teams serving many end users or a large volume of callers.

​
Base URL

All Forward endpoints use the production gateway: 
https://api.qoder.com/api/v1/forward

​
Authentication

All Forward endpoints require Qoder PAT authentication:
HeaderRequiredDescription
AuthorizationYesBearer <PAT>
Unsafe POST endpoints may accept an Idempotency-Key header.

​
Resource families

ResourceDescription
TemplatesReusable agent-shape baselines that define default agent and session configuration
IdentitiesEnd-user identities with per-identity configuration overrides and isolation
SessionsConversations or task runs started from a template + identity
SchedulesCron or one-time triggered execution
Schedule runsExecution records produced by schedules
ChannelsIntegration with external IM channels
Resources RegistryRegister shared resources into Forward

​
Error envelope

Errors use the Forward error envelope: 
{
  "type": "error",
  "request_id": "req_xxx",
  "error": {
    "type": "invalid_request_error",
    "code": "invalid_request_body",
    "message": "invalid request body"
  }
}

Create a template

Create a session