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

EFFECT Photonics Effect/v1 API

EFFECT Photonics' own custom REST namespace — a careers synchronisation trigger (POST /effect/v1/careers/sync, observed HTTP 401 anonymously) and a GLB 3D-model position endpoint used by the product visualiser (GET/POST /effect/v1/glb-positions/{id}).

EFFECT Photonics Effect/v1 API is one of 6 APIs that EFFECT Photonics publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include effect/v1. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 3 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://effectphotonics.com.

4 operations 3 paths 1 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://effectphotonics.com/wp-json/
Authentication
OAuth 2.0, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

EFFECT Photonics Effect/v1 API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (mcpOAuth2) using the authorizationCode flow, exposing 1 scope. An API key is passed in the header as X-WP-Nonce (wpNonce). It accepts HTTP basic authentication (applicationPassword).

  • mcpOAuth2 — OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC 8414 metadata at https://effectphotonics.com/.well-known/oauth-authorization-se…
  • wpNonce — WordPress cookie-authentication nonce. Advertised by the live server in its Access-Control-Allow-Headers response header (Authorization, X-WP-Nonce, Content-Di…
  • applicationPassword — WordPress Application Passwords — HTTP Basic with a user-issued application password. The live discovery document at https://effectphotonics.com/wp-json/ names…

Paths & Operations 4

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

effect/v1 4

EFFECT Photonics' own custom REST namespace — a careers synchronisation trigger and a GLB (3D model) position endpoint used by the product visualiser.

GET
/wp-json/effect/v1
GET /effect/v1
getEffectV1 2 params → 200401404
POST
/wp-json/effect/v1/careers/sync
POST /effect/v1/careers/sync
postEffectV1CareersSync → 200401404
GET
/wp-json/effect/v1/glb-positions/{id}
GET /effect/v1/glb-positions/{id}
getEffectV1GlbPositionsId 1 param → 200401404
POST
/wp-json/effect/v1/glb-positions/{id}
POST /effect/v1/glb-positions/{id}
postEffectV1GlbPositionsId 1 param → 200401404

Schemas 1

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

WPError
object
The WordPress REST API error envelope, observed verbatim on live 401/404 responses from this host. Not RFC 9457 problem+json.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

effect-photonics-effect-v1-api-openapi.yml Raw ↑

Other APIs EFFECT Photonics publishes across the network.

EFFECT Photonics Wp/v2 API
EFFECT Photonics MCP API
EFFECT Photonics Wp Abilities/v1 API
EFFECT Photonics Oembed/1.0 API
EFFECT Photonics Root API
Where this information came from

This is an independent, third-party profile of EFFECT Photonics Effect/v1 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.