PATCH
/
organizations
/
{organizationId}
/
technologies
/
{catalogTechnologyId}

Headers

Authorization
string
required

Path Parameters

organizationId
string
required
catalogTechnologyId
string
required

Body

application/json
category
string
color
enum<string>

Technology color used in diagrams

Available options:
blue,
green,
yellow,
orange,
red,
beaver,
dark-blue,
purple,
pink,
white,
grey,
black
deprecatedAt
string
description
string

Technical description for the technology, avoid marketing language

docsUrl
string

Documentation or readme url

iconUrlDark
string | null

Icon that only works on dark backgrounds

iconUrlLight
string | null

Icon that only works on light backgrounds

name
string

Long verbose name

nameShort
string

Short one or two word name to show in places with limited space

provider
enum<string> | null

Service provider that provides this technology

Available options:
aws,
azure,
gcp,
microsoft,
salesforce,
atlassian,
apache,
supabase
rejectionMessage
string

If rejected, detail description of why

rejectionReason
enum<string>

If rejected, the reason why

Available options:
duplicate,
incomplete,
invalid,
other
restrictions
enum<string>[] | null

Restriction on which model object or connections this technology can be added to

Available options:
actor,
app,
component,
connection,
group,
store,
system
status
enum<string>

Current status of the technology, including pending review, approved, and rejected. Approved technologies are visible to all users.

Available options:
approved,
pending-review,
rejected
type
enum<string> | null

Type or category of technology

Available options:
data-storage,
deployment,
framework-library,
gateway,
other,
language,
message-broker,
network,
protocol,
runtime,
service-tool
updatesUrl
string

Release notes or changelog url

websiteUrl
string

Landing page website url

Response

200 - application/json
catalogTechnology
object
required