stac-fastapi-catalogs-extension 0.4.0

STAC FastAPI extension for multi-tenant catalogs

Jump to: | Table of Contents |

stac-fastapi multi-tenant virtual catalogs extension

STAC FastAPI extension for multi-tenant, recursive catalog hierarchies.

This package adds a dedicated /catalogs registry and scoped catalog routes so a single STAC API deployment can serve multiple logical catalog trees. It is designed for use cases where one API needs tenant-style isolation, curated views, provider-specific trees, or thematic navigation across shared datasets.

The extension supports poly-hierarchy (multi-parenting), where a collection or catalog can be linked under multiple catalog paths without duplicating data. It also supports contextual navigation for scoped routes, preserving UI breadcrumb behavior while still exposing alternative parents through related links.

Implementation status

Project	Status	Notes
stac-fastapi-elasticsearch-opensearch (SFEOS)	Implemented	Active integration target for this extension
stac-fastapi-pgstac	Not implemented yet	In Progress: https://github.com/stac-utils/stac-fastapi-pgstac/pull/366
stac-fastapi-mongo	Not implemented yet	Planned

Last verified: 2026-03-22

Table of contents

• Implementation status
• Specification reference
• Conformance class guidance
• What this package provides
• Supported projects
• Install
• Integrate in a STAC FastAPI deployment
• Backend client requirements
• Notes for common deployment repos
• Endpoints added by this extension

Specification reference

This implementation is aligned with the Multi-Tenant Catalogs extension work in StacLabs:

• https://github.com/StacLabs/multi-tenant-catalogs

Notable concepts adopted here include:

• Recursive /catalogs endpoint structure
• Optional transaction management plane
• Safety-first unlink semantics (organizational operations are non-destructive)
• Runtime link generation for parent/child/related relationships

Conformance class guidance

When enabling this extension in your deployment, advertise conformance classes according to your enabled capabilities:

• Required:
  • https://api.stacspec.org/v1.0.0/core
  • https://api.stacspec.org/v1.0.0-rc.1/multi-tenant-catalogs
• Recommended:
  • https://api.stacspec.org/v1.0.0-rc.2/children
• Optional (only if transaction endpoints are enabled):
  • https://api.stacspec.org/v1.0.0-rc.1/multi-tenant-catalogs/transaction

Operational guidance:

• Read-only/public APIs should not expose POST/PUT/DELETE catalog endpoints and should not advertise the transaction conformance class.
• If transactions are enabled, expose and document the management endpoints and include the transaction conformance class in conformance responses.
• Important: To preserve the poly-hierarchy DAG structure, updates to collections SHOULD be performed through scoped routes (/catalogs/{catalogId}/collections/{collectionId}) rather than the core STAC route (/collections/{collectionId}). The core route is flat and does not maintain parent-child relationships, so updates through that route may not properly preserve the hierarchical context.

Multi-Tenant Security

For multi-tenant deployments where you want to prevent information leakage about other tenants, use the hide_alternate_parents flag:

CatalogsExtension(
    client=catalogs_client,
    hide_alternate_parents=True,  # Disables rel="related" links to alternative parents
)

When hide_alternate_parents=True, the API will only advertise the single contextual parent through rel="parent" and will not expose alternative parents via rel="related" links. This prevents clients from discovering the names and structure of other tenants in the system.

Supported projects

This extension is designed for STAC FastAPI deployment applications and is currently supported in:

• SFEOS: https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch

Planned (not yet implemented):

• stac-fastapi-pgstac: https://github.com/stac-utils/stac-fastapi-pgstac
• stac-fastapi-mongo: https://github.com/stac-utils/stac-fastapi-mongo

It can also be integrated into custom STAC FastAPI deployments that implement the AsyncBaseCatalogsClient contract.

What this package provides

• Two STAC FastAPI extension classes:
  • CatalogsExtension: Read-only discovery endpoints for catalogs
  • CatalogsTransactionExtension: Write operations (POST, PUT, DELETE) for catalog management
• Request/response models for catalogs and children APIs
• An abstract client contract: AsyncBaseCatalogsClient

This package wires routes and validation into your API. Your deployment app is responsible for providing a concrete client implementation backed by your database/search stack.

Install

pip install stac-fastapi-catalogs-extension

Integrate in a STAC FastAPI deployment

In your deployment app.py (for example in stac-fastapi-elasticsearch-opensearch), instantiate StacApi with CatalogsExtension and optionally CatalogsTransactionExtension, passing an implementation of AsyncBaseCatalogsClient.

Read-only deployment (discovery only)

from stac_fastapi.api.app import StacApi
from stac_fastapi.types.config import ApiSettings

from stac_fastapi_catalogs_extension import (
    CatalogsExtension,
    CATALOGS_CORE_CONFORMANCE,
)
from my_project.catalogs_client import CatalogsClient
from my_project.core_client import CoreClient


settings = ApiSettings()

core_client = CoreClient(...)
catalogs_client = CatalogsClient(...)

api = StacApi(
    settings=settings,
    client=core_client,
    extensions=[
        CatalogsExtension(
            client=catalogs_client,
            conformance_classes=list(CATALOGS_CORE_CONFORMANCE),
            settings=settings.model_dump(),
        )
    ],
)

app = api.app

With transaction support (read and write)

from stac_fastapi.api.app import StacApi
from stac_fastapi.types.config import ApiSettings

from stac_fastapi_catalogs_extension import (
    CatalogsExtension,
    CatalogsTransactionExtension,
)
from my_project.catalogs_client import CatalogsClient
from my_project.core_client import CoreClient


settings = ApiSettings()

core_client = CoreClient(...)
catalogs_client = CatalogsClient(...)

api = StacApi(
    settings=settings,
    client=core_client,
    extensions=[
        CatalogsExtension(
            client=catalogs_client,
            settings=settings.model_dump(),
        ),
        CatalogsTransactionExtension(
            client=catalogs_client,
            settings=settings.model_dump(),
        ),
    ],
)

app = api.app

The transaction conformance class is automatically registered when CatalogsTransactionExtension is included.

Backend client requirements

Your CatalogsClient should subclass AsyncBaseCatalogsClient and implement the required async methods, including:

• get_catalogs
• get_catalog
• create_catalog
• update_catalog
• delete_catalog
• get_catalog_collections
• create_catalog_collection
• get_catalog_collection
• update_catalog_collection
• unlink_catalog_collection
• get_catalog_collection_items
• get_catalog_collection_item
• get_sub_catalogs
• create_sub_catalog
• unlink_sub_catalog
• get_catalog_children
• get_catalog_conformance
• get_catalog_queryables

Notes for common deployment repos

stac-fastapi-elasticsearch-opensearch style deployment

• Build a catalogs client that reads/writes catalog links and hierarchy metadata from your OpenSearch/Elasticsearch index strategy.
• Reuse your existing core client for global /collections and /search routes.
• Add CatalogsExtension to the extensions list in app.py as shown above.

stac-fastapi-pgstac style deployment (planned)

• Build a catalogs client that maps these methods to SQL functions or pgstac tables/views that represent catalog hierarchy and scoped membership.
• Keep link generation contextual for scoped routes (/catalogs/{id}/collections/{collection_id}) so UI breadcrumb navigation stays correct.
• Add CatalogsExtension to the extensions list in app.py as shown above.

Endpoints added by this extension

CatalogsExtension (read-only discovery)

• GET /catalogs
• GET /catalogs/{catalog_id}
• GET /catalogs/{catalog_id}/collections
• GET /catalogs/{catalog_id}/collections/{collection_id}
• GET /catalogs/{catalog_id}/collections/{collection_id}/items
• GET /catalogs/{catalog_id}/collections/{collection_id}/items/{item_id}
• GET /catalogs/{catalog_id}/catalogs
• GET /catalogs/{catalog_id}/children
• GET /catalogs/{catalog_id}/conformance
• GET /catalogs/{catalog_id}/queryables

CatalogsTransactionExtension (write operations)

When CatalogsTransactionExtension is enabled, the following additional endpoints are available for catalog and collection management:

• POST /catalogs
• PUT /catalogs/{catalog_id}
• DELETE /catalogs/{catalog_id}
• POST /catalogs/{catalog_id}/collections
• PUT /catalogs/{catalog_id}/collections/{collection_id}
• DELETE /catalogs/{catalog_id}/collections/{collection_id}
• POST /catalogs/{catalog_id}/catalogs
• DELETE /catalogs/{catalog_id}/catalogs/{sub_catalog_id}