API Reference

Create application

Overview

Create application registers a system under test in your organization: name, application type (web, API, desktop), team ownership, and environment URLs used when dispatching validation. This is the programmatic equivalent of Platform → Applications → Create.

Use this endpoint when onboarding services from a CMDB, Terraform pipeline, or internal developer portal so engineers inherit correct team scope and staging URLs before creating reliability projects.

Who should read this

  • Platform engineers integrating CI/CD, internal tooling, or data pipelines with Zof.

Prerequisites

  • Valid organization API key with permission for this resource
  • Resource ID when path includes {id}, copy from Console or list endpoint
  • Staging environment for first integration test

When to use this workflow

  • Provisioning a new microservice before first Zof project
  • Syncing application registry from internal service catalog nightly
  • Terraform or Backstage scaffolder creating Zof resources alongside repo creation

Step-by-step procedure

Authenticate

Set Authorization: Bearer header with organization API key.

Confirm key role includes required permission (403 indicates insufficient scope).

Execute request

POST https://api.zof.ai/v1/applications

Include Content-Type: application/json for bodies with POST/PATCH.

Handle response

200/201: parse JSON body and persist resource ID for follow-up calls.

4xx: inspect error.code and error.param; fix request before retry.

429: honor Retry-After; implement exponential backoff in automation.

Key concepts

Permission
Requires applications:create (typically QA Lead or custom automation role).
name
Display name shown in Console and reports; unique per organization recommended.
type
web | api | desktop; drives default agent categories and execution plane hints.
team_id
Team that owns the application for RBAC and reporting scope.
urls
Map of environment keys (staging, production) to HTTPS base URLs agents will target.

Best practices

  • Use idempotency keys for POST operations in automation
  • Handle 429 responses with exponential backoff and jitter
  • Log X-Request-Id from response headers for support escalation
  • Test against staging project IDs before production automation

Common issues

422 validation_error
Missing team_id or invalid URL scheme; URLs must be https:// in production paths.
409 duplicate_name
Application name already exists; use PATCH update or unique naming convention.
403 Forbidden
API key lacks applications:create; assign role in Admin Center.

Create application (curl)

curl -X POST https://api.zof.ai/v1/applications \
  -H "Authorization: Bearer $ZOF_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: app-checkout-$(date +%Y%m%d)" \
  -d '{
    "name": "Checkout Web",
    "type": "web",
    "team_id": "team_01HXXXX",
    "urls": {
      "staging": "https://staging.example.com",
      "production": "https://checkout.example.com"
    }
  }'

API operations

POST
/applications
Register a new application with name, type, team, and environment URLs.

Was this page helpful?

01The operational surface

One surface for posture, operations, and what needs attention next.

The Zof home is not a marketing dashboard. It is the operational surface engineering, QA, and SRE teams use every day, quality posture, in-flight runs, coverage by module, and the actions a leader should look at next.

OPERATIONAL KPIs

  • Runs
  • Coverage
  • Risk

Live across every environment you ship to.

WORK SPINE

  • Specs
  • Tests
  • Schedules

From specification to scheduled regression.

GUARDRAILS

  • RBAC
  • SSO
  • audit

Every action attributable to a named human.

STAGING · LIVE/home
Zof AI home command center showing 12 runs at 94% pass, 3 open critical issues, 84% coverage, four module traceability bars, the specification pipeline, upcoming schedules, and recommended next actions with an active-runs sidebar.
Home view · Checkout Service · Staging · captured live from the product.
  • 01 · RUNS · 24H

    94% pass

    12 runs across staging

  • 02 · COVERAGE

    84%

    Across four modules

  • 03 · ACTIVE RUNS

    3 running

    Live on this branch

  • 04 · NEXT ACTIONS

    Recommended

    Triage gaps, new spec

Create application | Zof AI Documentation