Skip to content
POST/api/v1/catalog/deprecate

Deprecate a catalog entry

Marks a catalog asset deprecated in the in-process asset catalog: sets status='deprecated' and stores a deprecation policy { sunsetDate, urgency, reason, migrationTarget?, migrationGuide? } with deprecatedAt. assetId, sunsetDate and reason are required; urgency defaults to 'scheduled' (immediate|scheduled|advisory). The engine validates the policy before writing — an unparseable sunsetDate or a migrationTarget that is the asset itself or an already-sunset asset returns 400 INVALID_DEPRECATION_POLICY. Caller must be a member of the asset's owning org; an asset with no orgId is refused 403 ASSET_UNOWNED. This is a RECORD only — nothing prevents a deprecated entry from being selected by new evals; the flag surfaces in /catalog/summary pendingSunsets. Requires compliance:create; audited.

Authentication

Send Authorization: Bearer YOUR_API_KEY on every request. Generate API keys at /dashboard/settings/api-keys.

Request body required

Example

{
  "entry_id": "string",
  "deprecation_message": "string"
}
Schema
{
  "application/json": {
    "schema": {
      "type": "object",
      "required": [
        "entry_id"
      ],
      "properties": {
        "entry_id": {
          "type": "string"
        },
        "deprecation_message": {
          "type": "string"
        }
      }
    }
  }
}

Response

200 example

{
  "success": true
}

All status codes

200Deprecated.
400(no description)
401(no description)
403Forbidden — insufficient role for this operation.
404Not Found — ASSET_NOT_FOUND.
429(no description)
500Internal Server Error.

Code samples

cURL

curl -X POST \
  https://evalguard.ai/api/v1/catalog/deprecate \
  -H "Authorization: Bearer $EVALGUARD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "entry_id": "string", "deprecation_message": "string" }'

TypeScript

// The TypeScript SDK (@evalguard/sdk) exposes TYPED methods — runEval,
// getEval, runSecurityScan, checkFirewall, … — not a generic request().
// For an arbitrary endpoint, call it directly:

const res = await fetch("https://evalguard.ai/api/v1/catalog/deprecate", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.EVALGUARD_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "entry_id": "string",
    "deprecation_message": "string"
  }),
});
console.log(res.status, await res.json());

Python

# The Python SDK (pip install evalguardai) exposes TYPED methods on
# EvalGuardClient — run_eval, get_eval, … — not a generic request().
# For an arbitrary endpoint, call it directly:

import os
import requests

headers = {"Authorization": f"Bearer {os.environ['EVALGUARD_API_KEY']}"}
headers["Content-Type"] = "application/json"

response = requests.request(
    "POST",
    "https://evalguard.ai/api/v1/catalog/deprecate",
    headers=headers,
    json={
    "entry_id": "string",
    "deprecation_message": "string"
},
)
print(response.status_code, response.json())

Go

package main

import (
	"context"
	"fmt"
	"net/http"
	"os"
	"strings"
)

func main() {
	body := strings.NewReader(`{"entry_id":"string","deprecation_message":"string"}`)
	req, _ := http.NewRequestWithContext(context.Background(), "POST", "https://evalguard.ai/api/v1/catalog/deprecate", body)
	req.Header.Set("Authorization", "Bearer "+os.Getenv("EVALGUARD_API_KEY"))
	req.Header.Set("Content-Type", "application/json")
	resp, err := http.DefaultClient.Do(req)
	if err != nil { panic(err) }
	defer resp.Body.Close()
	fmt.Println(resp.Status)
}

Errors

400401403404429500

Other Integrations endpoints