> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ohmyho.st/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For account actions, read https://ohmyho.st/skills/ohmyhost-get-started/SKILL.md and use the authenticated ohmyho.st CLI or local product MCP. Mintlify search only reads documentation. Preserve the customer’s selected project, environment and authentication provider.

# Stream normalized deployment diagnostics



## OpenAPI

````yaml /openapi.json get /v1/projects/{project_id}/deployments/{deployment_id}/logs/events
openapi: 3.1.2
info:
  title: ohmyho.st API
  version: 0.0.0
  description: >-
    Public REST API for ohmyho.st hosting, projects, domains, email, credits and
    exports.
servers:
  - url: https://app.ohmyho.st
    description: Production control API
  - url: https://dev.app.ohmyho.st
    description: Development control API
security:
  - BearerAuth: []
paths:
  /v1/projects/{project_id}/deployments/{deployment_id}/logs/events:
    get:
      summary: Stream normalized deployment diagnostics
      operationId: streamDeploymentLogs
      parameters:
        - $ref: '#/components/parameters/RequestId'
        - $ref: '#/components/parameters/ProjectId'
        - $ref: '#/components/parameters/DeploymentId'
      responses:
        '200':
          description: A bounded normalized diagnostic event stream.
          content:
            text/event-stream:
              schema:
                $ref: '#/components/schemas/DeploymentDiagnostic'
        '401':
          $ref: '#/components/responses/Problem'
        '403':
          $ref: '#/components/responses/Problem'
        '404':
          $ref: '#/components/responses/ResourceNotFound'
        '503':
          $ref: '#/components/responses/Problem'
components:
  parameters:
    RequestId:
      name: X-Request-Id
      in: header
      description: Optional caller-provided correlation identifier.
      required: false
      schema:
        type: string
        minLength: 1
        maxLength: 128
    ProjectId:
      name: project_id
      in: path
      description: Project identifier.
      required: true
      schema:
        $ref: '#/components/schemas/Ulid'
    DeploymentId:
      name: deployment_id
      in: path
      description: Deployment identifier.
      required: true
      schema:
        $ref: '#/components/schemas/Ulid'
  schemas:
    DeploymentDiagnostic:
      type: object
      additionalProperties: false
      required:
        - id
        - source
        - code
        - message
        - occurred_at
      properties:
        id:
          $ref: '#/components/schemas/Ulid'
        source:
          type: string
          enum:
            - build
            - control
            - runtime
            - function
        code:
          type: string
          pattern: ^[A-Z][A-Z0-9_]{1,63}$
        message:
          type: string
          pattern: ^[A-Z][A-Z0-9_]{1,127}$
        exception_class:
          type: string
          maxLength: 128
        file:
          type: string
          maxLength: 512
        line:
          type: integer
          minimum: 1
        column:
          type: integer
          minimum: 0
        route:
          type: string
          maxLength: 512
        request_id:
          type: string
          maxLength: 128
        trace_id:
          type: string
          maxLength: 128
        duration_ms:
          type: integer
          minimum: 0
          maximum: 900000
        excerpt:
          type: string
          minLength: 1
          maxLength: 16384
          description: >-
            The customer's own output with control characters removed before
            storage: on BUILD_FAILED the tail of the install/build output
            (newest lines last), on HEALTH_CHECK_FAILED the head of the body the
            health check was answered with (at most 4096 characters, never a
            header). A running application holds its environment's secrets and
            this answer is not scanned for them, so, like a query of the
            project's database, a HEALTH_CHECK_FAILED excerpt is returned only
            to an owner of the project; never answer a health check with a
            secret.
        excerpt_truncated:
          type: boolean
          description: >-
            Whether output was omitted from excerpt (earlier build output, or
            the rest of the health answer). Present exactly when excerpt is
            present.
        status_code:
          type: integer
          minimum: 100
          maximum: 599
          description: >-
            The HTTP status the health check was answered with; present only on
            HEALTH_CHECK_FAILED. The probe is a cookieless GET of route that
            follows no redirect, so a 3xx is unhealthy too.
        occurred_at:
          type: string
          format: date-time
    Ulid:
      type: string
      pattern: ^[0-9A-HJKMNP-TV-Z]{26}$
    ProblemDetails:
      type: object
      description: RFC 9457 Problem Details extended with stable ohmyhost recovery fields.
      additionalProperties: false
      required:
        - type
        - title
        - status
        - code
        - request_id
        - retryable
        - suggested_action
      properties:
        type:
          type: string
          format: uri-reference
        title:
          type: string
          minLength: 1
        status:
          type: integer
          minimum: 400
          maximum: 599
        detail:
          type: string
        instance:
          type: string
          format: uri-reference
        code:
          type: string
          enum:
            - invalid_request
            - unauthenticated
            - forbidden
            - organization_required
            - resource_not_found
            - idempotency_key_reused
            - project_handle_unavailable
            - project_identity_unavailable
            - deployment_plan_expired
            - deployment_plan_incompatible
            - confirmation_expired
            - confirmation_invalid
            - etag_mismatch
            - promotion_source_stale
            - promotion_target_stale
            - promotion_invalid_target
            - mail_domain_conflict
            - mail_domain_required
            - mail_capacity_unavailable
            - storage_jurisdiction_conflict
            - shared_data_requires_promotion
            - production_deployment_required
            - framework_conversion_required
            - repository_configuration_missing
            - migration_filename_noncanonical
            - environment_secret_mutation_blocked
            - workers_runtime_incompatible
            - project_handle_invalid
            - project_handle_taken
            - project_handle_unchanged
            - project_rename_blocked
            - payload_too_large
            - rate_limited
            - insufficient_organization_credits
            - paid_plan_required
            - project_budget_exceeded
            - compute_performance_paid_required
            - compute_performance_unavailable
            - database_write_pending
            - database_access_limit
            - compute_change_pending
            - compute_change_conflict
            - billing_purchase_conflict
            - billing_recharge_conflict
            - github_connection_required
            - github_connection_revoked
            - repository_not_installed
            - cloudflare_zone_not_bound
            - cloudflare_authorization_closed
            - project_notes_conflict
            - project_export_not_ready
            - powered_by_flag_required
            - interactive_login_required
            - api_key_creation_uncertain
            - api_key_permissions_unavailable
            - reconciliation_exhausted
            - service_unavailable
            - source_commit_not_found
            - domain_hostname_taken
            - domain_dns_conflict
            - data_change_blocked
            - data_change_in_progress
            - data_change_not_applicable
            - rollback_target_data_changed
            - project_domain_delete_required
        request_id:
          type: string
          minLength: 1
          maxLength: 128
        retryable:
          type: boolean
        retry_after_seconds:
          type: integer
          minimum: 1
          maximum: 86400
          description: >-
            Optional machine-readable retry delay for a rate limit, matching
            Retry-After.
        suggested_action:
          type: string
          minLength: 1
  responses:
    Problem:
      description: The request failed.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/XRequestId'
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/ProblemDetails'
    ResourceNotFound:
      description: >-
        The resource does not exist or is not visible to the authenticated
        principal.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/XRequestId'
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/ProblemDetails'
          examples:
            resourceNotFound:
              value:
                type: https://docs.ohmyho.st/errors/resource-not-found
                title: Resource not found
                status: 404
                code: resource_not_found
                request_id: req_01J00000000000000000000000
                retryable: false
                suggested_action: Check the resource identifier and your access scope.
  headers:
    XRequestId:
      description: Correlates the request with operations, events, logs, and audit records.
      required: true
      schema:
        type: string
        minLength: 1
        maxLength: 128
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        WorkOS access JWT or a user-owned WorkOS API key. User keys are bound to
        one organization and restricted to their enabled product permissions.
        Session-only onboarding and session revocation require an interactive
        access JWT. No cookie session is assumed.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.