Skip to main content
Neon Postgres Docs

Search documentation

Type to search this documentation.

List available shared preload libraries

GET/projects/{project_id}/available_preload_librariesList available shared preload libraries

Returns the shared preload libraries available for the specified project's Postgres version. Shared preload libraries are Postgres extensions that require the shared_preload_libraries setting and a compute restart to activate. Use this list to determine which libraries can be enabled in the project's settings.preload_libraries configuration.

Parameters

project_idstringpathrequired

pattern ^[a-z0-9-]{1,60}$

Responses

200Successfully returned available shared preload librariesapplication/json
objectAvailablePreloadLibraries
librariesarray of object

Preload libraries available for the project's Postgres version. Each entry includes `library_name`, `description`, `is_default`, `is_experimental`, and `version`.

Show child attributes
Show array items
descriptionstringrequired

Human-readable explanation of the library's purpose and behavior.

is_defaultbooleanrequired

Whether this library is loaded by default in the `shared_preload_libraries` configuration for new compute endpoints.

is_experimentalbooleanrequired

Marks the library as experimental. Experimental libraries may be unstable, subject to breaking changes, or not recommended for production use.

library_namestringrequired

Name of the Postgres shared preload library as it appears in the `shared_preload_libraries` parameter (for example, `pg_stat_statements`).

versionstringrequired

Version of the preload library.

Example response
{
  "libraries": [
    {
      "description": "string",
      "is_default": true,
      "is_experimental": true,
      "library_name": "string",
      "version": "string"
    }
  ]
}
defaultGeneral Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress. application/json
objectGeneralError
codestringrequired

default ""

messagestringrequired

Error message

request_idstring

Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.

Example response
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
Documentation menu