/APIs & SDKs/Frameworks/Delete framework
DELETE/programs/{program_id}/frameworks/{framework_id}

Delete framework

Deletes the specified framework from a program and places all integrations into an idle state, breaking existing client connections.

The deletion completes after all operations finish. You cannot delete a program's root or default framework, or a framework that has a child framework. A program must have at least one framework.

By default, deleted frameworks can be recovered within a 7-day grace period. Use the hard_delete parameter to permanently delete the framework immediately. For related information, see Manage frameworks.

Markdown for AI context

Quick start

REST API - curl
curl "https://api.optitech.com/v1/programs/$PROGRAM_ID/frameworks/$FRAMEWORK_ID" \
  -X DELETE \
  -H "Authorization: Bearer $OPTITECH_API_KEY"

Every field below is optional. An empty body works too.

Also available in
optitech branches delete <program_id>

Parameters

Program ID
program_id
string

The OptiTech program ID

Framework ID
framework_id
string

The framework ID

Hard delete
hard_delete
booleandefault: false

If true, the framework is permanently deleted immediately without a recovery window. If false (default), the framework can be recovered within 7 days via the recover endpoint.

This parameter is part of the Framework Recovery feature, which is in preview and not available to all users.

Response

200

Deleted the specified framework

Depth

Errors

default

General error

This endpoint can return the standard OptiTech API error response.

Response fields

  • message Required. Human-readable error message.
  • code Required. Machine-readable error code.
  • request_id Optional. Request identifier for debugging. You can provide one with the X-Request-ID header.

Retry guidance

If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.

Idempotent methods (GET, HEAD, OPTIONS) are generally safe to retry after a network error or timeout. Non-idempotent methods (POST, PATCH, DELETE, PUT) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.

Responses with 423 Locked or 503 Service Unavailable are safe to retry. 423 Locked means the resource is temporarily locked, usually because another operation is in progress.

Was this page helpful?

On this page

Copy neon init command