How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ForgeRock Configuration API

Read and update IDM configuration

ForgeRock Configuration API is one of 38 APIs that ForgeRock publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Configuration. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and a changelog.

This API exposes 4 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 7.3.0.

Requests are made against a single base URL, https://{deployment}/am.

4 operations 2 paths 1 schemas 1 DELETE2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
7.3.0
Base URL
https://{tenant}.forgeblocks.com
Authentication
API Key, HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 2

ForgeRock Configuration API declares 2 security schemes for authenticating requests. An API key is passed in the header as iPlanetDirectoryPro (ssoToken). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • ssoToken — AM SSO token obtained from authentication
  • bearerAuth — OAuth 2.0 access token

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Configuration 4

Read and update IDM configuration

GET
/config
ForgeRock List configuration objects
listConfigurations → 200
GET
/config/{configId}
ForgeRock Get a configuration object
getConfiguration 1 param → 200404
PUT
/config/{configId}
ForgeRock Update a configuration object
updateConfiguration 1 param body → 200
DELETE
/config/{configId}
ForgeRock Delete a configuration object
deleteConfiguration 1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ErrorResponse (3 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Standard CREST error response
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

forgerock-configuration-api-openapi.yml Raw ↑

Other APIs ForgeRock publishes across the network.

ForgeRock Access Requests API
ForgeRock Access Reviews API
ForgeRock Analytics API
ForgeRock Applications API
ForgeRock Audit API
ForgeRock Authentication API
ForgeRock Certifications API
ForgeRock Company View API
ForgeRock Entitlements API
ForgeRock Entries API
ForgeRock Groups API
ForgeRock Health API
Where this information came from

This is an independent, third-party profile of ForgeRock Configuration API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.