ACLs7

Add-Ons5

AI Gateway Agents5

AI Gateway Auth Strategies5

AI Gateway CA Certificates5

AI Gateway Certificates5

AI Gateway Config Stores10

AI Gateway Consumer Groups8

AI Gateway Consumers11

AI Gateway DataPlane Certificates4

AI Gateway Identity Providers5

AI Gateway MCP Servers5

AI Gateway Model Providers5

AI Gateway Models5

AI Gateway Nodes3

AI Gateway Policies5

AI Gateway SNIs10

AI Gateway Vaults5

AI Gateways6

API6

API Attributes1

API Documentation6

API Image4

API Implementation4

API Operations2

API Package Documentation6

API Package Image4

API Package Operations4

API Package Specification4

API Packages5

API Publication8

API Specification6

API Version5

API-keys7

App Auth Strategies6

Application Registrations8

Applications8

Assets6

Auth Settings17

Authentication1

Basic-auth credentials7

CA Certificates5

Catalog Integrations1

Catalog Resource Mappings4

Catalog Resource Services1

Catalog Resources3

Catalog Service API Mappings5

Catalog Service Resources1

Catalog Services5

Certificates5

Cloud Gateways Resource Quotas3

Config Store Secrets5

Config Stores5

Consumer Groups9

Consumers9

Control Plane Groups6

Control Planes5

Criteria Templates1

Custom Domains5

Custom Plugin Schemas5

CustomPlugins5

Dashboards5

Data-Plane Group Configurations3

DCR Providers6

Degraphql_routes7

DP Certificates5

DP Nodes6

Event Gateway Backend Clusters5

Event Gateway DataPlane Certificates5

Event Gateway Listener Policies9

Event Gateway Listeners5

Event Gateway Nodes4

Event Gateway Schema Registries5

Event Gateway Static Keys4

Event Gateway TLS Trust Bundles5

Event Gateway Virtual Cluster Consume Policies9

Event Gateway Virtual Cluster Policies9

Event Gateway Virtual Cluster Produce Policies9

Event Gateway Virtual Clusters5

Event Gateways6

GraphQL Cost Decorations7

HMAC-auth credentials7

Impersonation Settings2

Integration Instance Auth Config3

Integration Instance Auth Credentials3

Integration Instances5

Invites1

JWTs7

Keys10

KeySets5

MCP Server Runtime1

MCP Servers6

Me2

Metering Events2

Meters6

MTLS-auth credentials7

Networks6

Notifications11

OpenMeter Apps2

OpenMeter Billing Settings5

OpenMeter Customers19

OpenMeter Defaults2

OpenMeter Entitlements1

OpenMeter Features6

OpenMeter LLM Cost5

OpenMeter Product Catalog19

OpenMeter Subscriptions8

OpenMeter Tax5

Pages7

Partial Links1

Partials5

Personal Access Tokens6

Plugins26

Portal Audit Logs6

Portal Auth Settings13

Portal Custom Domains4

Portal Customization3

Portal Developers5

Portal Emails19

Portal Integrations3

Portal Team Membership4

Portal Team Roles4

Portal Teams5

Portals5

Portals IP Allow List6

Private DNS5

Provider Accounts2

Resource Availability1

Resource Configurations3

Roles9

Routes10

Schemas2

Scorecards11

Services5

Skills2

Snippets5

SNIs10

System Accounts5

System Accounts - Access Tokens5

System Accounts - Roles4

System Accounts - Team Membership4

Targets6

Team Membership4

Teams5

Transit Gateways5

Upstreams5

Users4

Vaults5

Portals

List Portals

Lists developer portals defined in this region for this organization. Each developer portal is available at a unique address and has isolated configuration, customization, developers, and applications.

get/v3/portals

Query parameters

page[size]integer

Example:10

The maximum number of items to include per page. The last page of a collection may include fewer items.

page[number]integer

Example:1

Determines which page of the entities to retrieve.

sortstring

Sorts a collection of portals. Supported sort attributes are:

name
description
authentication_enabled
rbac_enabled
auto_approve_applications
auto_approve_developers
default_domain
canonical_domain
created_at
updated_at

authentication_enabledboolean

Filter by a boolean value (true/false).

rbac_enabledboolean

Filter by a boolean value (true/false).

auto_approve_developersboolean

Filter by a boolean value (true/false).

auto_approve_applicationsboolean

Filter by a boolean value (true/false).

Filter portals returned in the response.

Response

A paginated list of portals in the current region of an organization.

Example response

{
  "data": [
    {
      "id": "5f9fd312-a987-4628-b4c5-bb4f4fddd5f7",
      "created_at": "2022-11-04T20:10:06.927Z",
      "updated_at": "2022-11-04T20:10:06.927Z",
      "sipr_enabled": true,
      "labels": {
        "env": "test"
      }
    }
  ],
  "meta": {
    "page": {
      "number": 1,
      "size": 10,
      "total": 100
    }
  }
}

Changes

Changed in 7 of the 75 revisions of this API.361025

Jun 23, 2026bb5e056b7c6d1See the full diff
- ○
  added the optional property data/items/notifications_developer_pii_visibility_enabled to the response with the 200 status
  response-optional-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Apr 7, 2026f8b12cdd4a061See the full diff
- ○
  added the required property data/items/sipr_enabled to the response with the 200 status
  response-required-property-added
Oct 23, 20258ab3ec3ed3011See the full diff
- ●
  added the new type enum value to the allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterStandard]/rule response property for the response status 400
  response-property-enum-value-added
Aug 22, 20253c0154b2053a114See the full diff
- ▲
  the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterChoiceItem]/source became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterDependentItem]/source became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterMaximumLength]/source became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterMinimumLength]/source became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property allOf[subschema #2]/invalid_parameters/items/oneOf[InvalidParameterStandard]/source became nullable for the status 400
  response-property-became-nullable
- ▲
  the response property data/items/display_name became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property data/items/name became nullable for the status 200
  response-property-became-nullable
- ▲
  the response property detail became nullable for the status 401
  response-property-became-nullable
- ▲
  the response property instance became nullable for the status 401
  response-property-became-nullable
- ▲
  the response property status became nullable for the status 401
  response-property-became-nullable
- ▲
  the response property title became nullable for the status 401
  response-property-became-nullable
- ○
  the authentication_enabled response's property default value true was added for the status 200
  response-property-default-value-added
- ○
  the auto_approve_applications response's property default value false was added for the status 200
  response-property-default-value-added
- ○
  the auto_approve_developers response's property default value false was added for the status 200
  response-property-default-value-added
- ○
  the rbac_enabled response's property default value false was added for the status 200
  response-property-default-value-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 14, 20256333a0d3b095917See the full diff
- ▲
  for the query request parameter filter, the type/format of property canonical_domain was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property default_api_visibility was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property default_application_auth_strategy_id was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property default_domain was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property default_page_visibility was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property description was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property id was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  for the query request parameter filter, the type/format of property name was specialized from / to object/
  request-parameter-property-type-specialized
- ▲
  the data/items/ response's property type/format changed from / to object/ for status 200
  response-property-type-changed
- ○
  added the optional property data/items/labels to the response with the 200 status
  response-optional-property-added
- ○
  removed Portal subschema #2 from the data/items/ response property allOf list for the response status 200
  response-property-all-of-removed
- ○
  added the required property data/items/authentication_enabled to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/auto_approve_applications to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/auto_approve_developers to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/canonical_domain to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/created_at to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/default_api_visibility to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/default_application_auth_strategy_id to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/default_domain to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/default_page_visibility to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/description to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/display_name to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/id to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/name to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/rbac_enabled to the response with the 200 status
  response-required-property-added
- ○
  added the required property data/items/updated_at to the response with the 200 status
  response-required-property-added
This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 22, 202576b0fefddb0d1691See the full diff
- ▲
  the data/items/ response's property type/format changed from object/ to / for status 200
  response-property-type-changed
- ▲
  removed the required property data/items/authentication_enabled from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/auto_approve_applications from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/auto_approve_developers from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/canonical_domain from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/created_at from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/default_api_visibility from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/default_application_auth_strategy_id from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/default_domain from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/default_page_visibility from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/description from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/display_name from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/id from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/name from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/rbac_enabled from the response with the 200 status
  response-required-property-removed
- ▲
  removed the required property data/items/updated_at from the response with the 200 status
  response-required-property-removed
- ●
  for the query request parameter filter, the type/format of property canonical_domain was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property default_api_visibility was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property default_application_auth_strategy_id was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property default_domain was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property default_page_visibility was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property description was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property id was changed from object/ to /
  request-parameter-property-type-changed
- ●
  for the query request parameter filter, the type/format of property name was changed from object/ to /
  request-parameter-property-type-changed
- ●
  removed the optional property data/items/labels from the response with the 200 status
  response-optional-property-removed
- ○
  added Portal subschema #2 to the data/items/ response property allOf list for the response status 200
  response-property-all-of-added
Jul 1, 20259a3d26a000881See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 6 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history