Federal Accounting Standards Advisory Board Authentication

Authentication

Federal Accounting Standards Advisory Board secures its APIs with none and basic across 2 declared security schemes, as derived from its OpenAPI definitions.

AccountingFederal GovernmentStandardsFinancial ReportingGovernmentRegulationsContentPublications
Methods: none, basic Schemes: 2 OAuth flows: API key in:

Security Schemes

anonymous none
application-passwords http
scheme: basic

Source

Authentication Profile

Raw ↑
generated: '2026-09-09'
method: probed
source: https://fasab.gov/wp-json/
docs: null
note: >-
  FASAB publishes no authentication documentation. This profile records what the site's own WordPress
  REST discovery document declares and what unauthenticated requests actually observed on 2026-09-09.
  The public read surface requires NO credential at all — every one of the 28 operations in
  openapi/federal-accounting-standards-advisory-board-wp-content-openapi.yml returned HTTP 200 anonymously.
summary:
  types:
  - none
  - basic
  api_key_in: []
  oauth2_flows: []
  public_read: true
schemes:
- name: anonymous
  type: none
  description: >-
    The public read surface. No Authorization header, API key, cookie or nonce is required; the
    `security: [{}]` block in the derived OpenAPI reflects the observed behaviour. Verified against
    /wp/v2/posts, /wp/v2/pages, /wp/v2/media, /wp/v2/search, /wp/v2/types, /wp/v2/taxonomies and the
    route index on 2026-09-09.
  sources:
  - openapi/federal-accounting-standards-advisory-board-wp-content-openapi.yml
  evidence:
  - url: https://fasab.gov/wp-json/wp/v2/pages?per_page=1
    http_status: 200
    anonymous: true
- name: application-passwords
  type: http
  scheme: basic
  description: >-
    WordPress Application Passwords, declared by fasab.gov itself in the `authentication` object of its
    REST discovery document. Credentials are HTTP Basic (WordPress username + a generated application
    password) and are issued interactively from wp-admin. This governs the AUTHENTICATED surface only —
    the administrative and plugin namespaces that answer 401 rest_forbidden anonymously — and is
    available to FASAB site operators, not to the public. There is no self-service registration.
  authorization_endpoint: https://fasab.gov/wp-admin/authorize-application.php
  sources:
  - https://fasab.gov/wp-json/
  evidence:
  - url: https://fasab.gov/wp-json/
    http_status: 200
    field: authentication['application-passwords'].endpoints.authorization
gated_surface:
  note: Routes confirmed to require authentication (HTTP 401 rest_forbidden anonymously, 2026-09-09).
  probes:
  - {url: 'https://fasab.gov/wp-json/wp/v2/settings', http_status: 401}
  - {url: 'https://fasab.gov/wp-json/wp/v2/plugins', http_status: 401}
  - {url: 'https://fasab.gov/wp-json/wp/v2/themes', http_status: 401}
  - {url: 'https://fasab.gov/wp-json/wp/v2/block-types', http_status: 401}
  - {url: 'https://fasab.gov/wp-json/wp/v2/users/me', http_status: 401}
  - {url: 'https://fasab.gov/wp-json/wp/v2/posts/12417/revisions', http_status: 401}
  - {url: 'https://fasab.gov/wp-json/wp-abilities/v1/abilities', http_status: 401}

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/federal-accounting-standards-advisory-board-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.