Empowerly · Authentication Profile
Empowerly Authentication
Authentication
Empowerly declares 0 security scheme(s) across its OpenAPI definitions.
CompanyEducationEdTechCollege AdmissionsCounselingStudentsCareer ServicesConsumer ServicesStatus Page
Methods:
Schemes: 0
OAuth flows:
API key in:
Security Schemes
Source
Authentication Profile
generated: '2026-08-12'
method: derived
source: >-
openapi/empowerly-status-api-openapi.yml (no securitySchemes; global `security: []`), plus live
unauthenticated probes of status.empowerly.com, api.empowerly.com and app.empowerly.com 2026-08-12
summary: >-
Empowerly documents no authentication for developers because it exposes no developer API. The one
callable public surface is entirely unauthenticated. A separate production API host exists behind
the web portal and is presumed session/token authenticated, but nothing about its scheme is
published and none was inferred.
apis:
- api: Empowerly Status API
baseURL: https://status.empowerly.com/api/v2
schemes: []
anonymous: true
note: >-
No securityScheme is declared and none is required. All eight probed endpoints returned 200 to
an anonymous GET with no credential of any kind. Access-Control-Allow-Origin is `*`, so the API
is callable directly from a browser. This is the Atlassian Statuspage default posture, not an
Empowerly design decision.
evidence:
- url: https://status.empowerly.com/api/v2/summary.json
http_status: 200
credential_sent: none
undocumented:
- host: https://api.empowerly.com
scheme: unknown
note: >-
Live production API host for the student/counselor portal. No auth scheme is published, no
/.well-known/oauth-authorization-server (403), no /.well-known/openid-configuration, and no
documented token, API key or OAuth flow anywhere on empowerly.com. Only the unauthenticated
/health endpoint (200) responds; every other probed path 404s. Recorded as unknown — NOT guessed.
- host: https://app.empowerly.com
scheme: unknown
note: >-
Student and counselor web portal (CloudFront-served SPA). Sign-in is a human web login; no
programmatic auth is documented and no OIDC discovery document is served.
oauth:
supported: false
discovery_probed:
- url: https://empowerly.com/.well-known/oauth-authorization-server
http_status: 404
- url: https://empowerly.com/.well-known/openid-configuration
http_status: 404
- url: https://api.empowerly.com/.well-known/oauth-authorization-server
http_status: 403
scopes:
published: false
note: >-
derive-oauth-scopes.py found zero oauth2 securitySchemes across the repo, and no scopes or
permissions reference exists on empowerly.com. No scopes/ artifact was written.
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.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/empowerly-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.