OpenPages · Authentication Profile

Openpages Authentication

Authentication

OpenPages secures its APIs with oauth2 and http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyB2BGovernanceRiskComplianceGRCRegulatory ComplianceRisk ManagementEnterprise SoftwareWatsonxAudit
Methods: oauth2, http Schemes: 1 OAuth flows: API key in:

Security Schemes

iam-bearer http
scheme: bearer

Source

Authentication Profile

openpages-authentication.yml Raw ↑
generated: '2026-07-20'
method: searched
source: https://cloud.ibm.com/docs/openpages?topic=openpages-iam-openpages
docs: https://cloud.ibm.com/docs/openpages?topic=openpages-iam-openpages
summary:
  types: [oauth2, http]
  model: IBM Cloud Identity and Access Management (IAM)
  token_type: IAM bearer access token
  api_key_in: []
  oauth2_flows: []
notes: >-
  Access to OpenPages service instances is controlled by IBM Cloud Identity and
  Access Management (IAM); further, finer-grained access is managed within the
  OpenPages application itself. Calls to the OpenPages REST API require the
  caller to hold the OpenPages "User" service access role (crn service role
  GRCUser) and to present an IAM bearer access token. IAM API keys are exchanged
  for bearer tokens at the IBM Cloud IAM token endpoint. Users and groups are
  synchronized from IBM Cloud IAM into OpenPages; identities can be federated.
schemes:
- name: iam-bearer
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: >-
    IBM Cloud IAM access token presented as Authorization: Bearer <token>.
    Tokens are obtained by exchanging an IBM Cloud IAM API key at the IAM token
    service.
  token_endpoint: https://iam.cloud.ibm.com/identity/token
  sources: ['https://cloud.ibm.com/docs/openpages?topic=openpages-iam-openpages']
roles:
- name: OpenPages User
  crn: crn:v1:bluemix:public:openpages::::serviceRole:GRCUser
  grants: Log in to OpenPages and make calls to the OpenPages REST API.
- name: Viewer
  crn: crn:v1:bluemix:public:openpages::::serviceRole:Viewer
- name: Operator
  crn: crn:v1:bluemix:public:openpages::::serviceRole:Operator
- name: Editor
  crn: crn:v1:bluemix:public:openpages::::serviceRole:Editor
- name: Administrator
  crn: crn:v1:bluemix:public:openpages::::serviceRole:Administrator
network_controls:
  ip_allowlisting: >-
    Optional per-instance IP allowlisting (IPv4/IPv6 addresses or CIDR ranges)
    restricts which clients can log in and access the API. By default all IP
    addresses are allowed.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/openpages-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.