Headers
Body
application/json
Technology color used in diagrams
Available options:
blue, green, yellow, orange, red, beaver, dark-blue, purple, pink, white, grey, black Technical description for the technology, avoid marketing language
Documentation or readme url
Icon that only works on dark backgrounds
Example:
[
"/organizations/{organizationId}/dark/{catalogTechnologyId}.png",
"/dark/{catalogTechnologyId}.png"
]Icon that only works on light backgrounds
Example:
[
"/organizations/{organizationId}/light/{catalogTechnologyId}.png",
"/light/{catalogTechnologyId}.png"
]Long verbose name
Short one or two word name to show in places with limited space
Service provider that provides this technology
Available options:
aws, azure, gcp, microsoft, salesforce, atlassian, apache, supabase If rejected, detail description of why
If rejected, the reason why
Available options:
duplicate, incomplete, invalid, other Restriction on which model object or connections this technology can be added to
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 or category of technology
Available options:
data-storage, deployment, framework-library, gateway, other, language, message-broker, network, protocol, runtime, service-tool Release notes or changelog url
Landing page website url
Response
OK