List database extensions
Read the curated PostgreSQL extension catalog available during database creation.
Request & response examples
Request example Server-side
curl --fail-with-body --request GET \ 'https://app.helicarrier.xyz/api/hangar/extensions' \ -H "Authorization: Bearer $HELI_API_KEY"const response = await fetch( "https://app.helicarrier.xyz/api/hangar/extensions", { method: "GET", headers: { Authorization: `Bearer ${process.env.HELI_API_KEY}` } });const data = await response.json();if (!response.ok) { throw new Error(`HTTP ${response.status}: ${data.error}`);}// Inspect data; avoid logging secret responses.import osimport requests
response = requests.request( "GET", "https://app.helicarrier.xyz/api/hangar/extensions", headers={ "Authorization": f"Bearer {os.environ['HELI_API_KEY']}" }, timeout=30,)response.raise_for_status()data = response.json()# Inspect data; avoid logging secret responses. Response example 200
[ { "name": "vector", "label": "pgvector", "description": "Vector similarity search for embeddings / AI" }]Illustrative values · selected fields
Parameters
This request does not require path, query, or body parameters.
Response 200
Returns the curated PostgreSQL extension catalog as an array. An empty array means no entries were returned.
Examples show selected response fields with illustrative values. Your response can contain additional fields.
name string Human-readable resource name.
label string Human-readable label.
description string Description of the resource or capability.
Errors
401 The API key is missing, invalid, or revoked.
403 The caller or key scope does not permit this operation.
ALSO AVAILABLE VIA MCP
Connect your agent ↗ list_db_extensions
Required MCP arguments: none. Send path, query,
and body fields together as tool arguments.