# Package Management APIs

For a complete list of package management API endpoints, see [OpenAPI Specification](/developer-api/openapi-specification.md)

### List Team Packages

Use the GET `/api/organizations/:organizationId/bricks/` endpoint to list all packages visible to your team.

### List Package Version History

Use the GET `/api/bricks/:id/versions/` endpoint to list versions of a package (mod, brick, integration definition, etc.).

Notes:

* `:id` refers to the surrogate UUID for the package, not the registry id. You can locate the UUID via the endpoint to [#list-team-packages](#list-team-packages "mention")
* The response does NOT include the package config, use [#get-package-config](#get-package-config "mention") to fetch that

### Get Package Config

Use the GET `/api/registry/bricks/:registryId/` endpoint to get a package and its config. 

The endpoint will return the latest version of the package. To get a specific version, use the `version=<x.y.z>` query param. Use [#list-package-version-history](#list-package-version-history "mention") to see all versions of a given package.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pixiebrix.com/developer-api/package-management-apis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.