PJM Browserless Authentication API

The REST authentication front door for every browserless/API integration with PJM eTools. A client POSTs to the PJM single sign-on service with X-OpenAM-Username and X-OpenAM-Password headers and receives a JSON tokenId, which is then presented as a pjmauth cookie on subsequent tool API calls, and released via a logout call. PJM has additionally moved custom-code REST clients onto PKI, requiring a two-way TLS client certificate against the access/authenticate/pjmauthcert endpoint alongside credentials. The service is ForgeRock OpenAM — verified live with HTTP 405 on GET https://sso.pjm.com/access/authenticate/ on 2026-07-27, confirming the documented POST-only endpoint.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/pjm-browserless-authentication-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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

Get an API key

Free tier, no email required.

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

API entry from apis.yml

apis.yml Raw ↑
aid: pjm:pjm-browserless-authentication-api
name: PJM Browserless Authentication API
description: The REST authentication front door for every browserless/API integration with PJM eTools.
  A client POSTs to the PJM single sign-on service with X-OpenAM-Username and X-OpenAM-Password headers
  and receives a JSON tokenId, which is then presented as a pjmauth cookie on subsequent tool API calls,
  and released via a logout call. PJM has additionally moved custom-code REST clients onto PKI, requiring
  a two-way TLS client certificate against the access/authenticate/pjmauthcert endpoint alongside credentials.
  The service is ForgeRock OpenAM — verified live with HTTP 405 on GET https://sso.pjm.com/access/authenticate/
  on 2026-07-27, confirming the documented POST-only endpoint.
humanURL: https://www.pjm.com/markets-and-operations/etools/security.aspx
baseURL: https://sso.pjm.com/access
image: https://www.pjm.com/assets/MVC/responsive/img/pjm-logo.png
tags:
- Authentication
- Single Sign-On
- Security
- PKI
properties:
- type: Guide
  url: https://www.pjm.com/-/media/DotCom/etools/pjm-browserless-authentication-guide.pdf
- type: Documentation
  url: https://www.pjm.com/markets-and-operations/etools/security.aspx
- type: Guide
  url: https://www.pjm.com/-/media/DotCom/etools/security/pki-authentication-guide.pdf
- type: Sandbox
  url: https://ssotrain.pjm.com/
- type: Authentication
  url: authentication/pjm-authentication.yml
- type: AgentSkill
  url: skills/pjm-authenticate-browserless-etools.md