Cruz Foam · Authentication Profile

Cruz Foam Authentication

Authentication

Cruz Foam publishes no developer program and issues no API credentials. The WordPress REST content API behind cruzfoam.com is anonymously readable — no key, token, signature or account is required to read posts, pages, the customer showcase, media, taxonomies, search or the discovery metadata. The server declares exactly one authentication method in its own root document, WordPress application passwords, and that method gates only the write and privileged-read operations that are not part of the public surface.

Cruz Foam declares 0 security scheme(s) across its OpenAPI definitions.

CompanyMaterials ScienceSustainable PackagingCompostable MaterialsBiomaterialsCircular EconomyManufacturingConsumer Packaged GoodsCold ChainSustainabilityContent
Methods: Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

Raw ↑
generated: '2026-08-11'
method: probed
source: https://cruzfoam.com/wp-json/
docs: https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/
description: >-
  Cruz Foam publishes no developer program and issues no API credentials. The WordPress REST
  content API behind cruzfoam.com is anonymously readable — no key, token, signature or account is
  required to read posts, pages, the customer showcase, media, taxonomies, search or the discovery
  metadata. The server declares exactly one authentication method in its own root document,
  WordPress application passwords, and that method gates only the write and privileged-read
  operations that are not part of the public surface.
summary:
  types: []
  anonymous_read: true
  credentialed_write: true
  api_key_in: []
  oauth2_flows: []
  note: >-
    No securityScheme appears in any of the nine derived OpenAPI documents because the public
    surface genuinely has none. This is a recorded absence, not a gap in harvesting.
schemes: []
declared_by_server:
  - name: application-passwords
    type: http
    scheme: basic
    description: >-
      WordPress application passwords (RFC 7617 Basic over TLS, username + generated
      application password). Declared in the `authentication` block of the API root document.
      Required for every write method and for privileged reads such as GET /wp/v2/settings.
      Credentials are issued per WordPress user from the site admin — there is no public
      registration path, so this is a staff-only credential, not a developer credential.
    authorization_endpoint: https://cruzfoam.com/wp-admin/authorize-application.php
    source: https://cruzfoam.com/wp-json/
evidence:
  - url: https://cruzfoam.com/wp-json/
    http_status: 200
    finding: 'authentication: {"application-passwords": {"endpoints": {"authorization": "https://cruzfoam.com/wp-admin/authorize-application.php"}}}'
  - url: https://cruzfoam.com/wp-json/wp/v2/posts?per_page=1
    http_status: 200
    finding: 'Anonymous read succeeds; response carries `Allow: GET`, confirming read-only anonymous access.'
  - url: https://cruzfoam.com/wp-json/wp/v2/customers?per_page=1
    http_status: 200
    finding: Anonymous read of the site-specific customers post type succeeds, X-WP-Total 20.
  - url: https://cruzfoam.com/wp-json/wp/v2/settings
    http_status: 401
    finding: '{"code":"rest_forbidden","message":"Sorry, you are not allowed to do that.","data":{"status":401}}'
x-evidence:
  fetched: '2026-08-11'
  probes: 4