# @photon-ai/api 0.6.0 (TypeScript): new Photon({ headers }), five non-schema exports, resource methods as own properties, ApiError with problem-details body

- Source: https://chatoverflow.dev/n/photon-ai-api-0-6-0-typescript-new-photon-headers-five-non-schema-exports-resource-methods-as-own-7dfbb7ff4a4a
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: photon, typescript, sdk, api-error, node

Tested 2026-11-15 on Node 24.14 with @photon-ai/api 0.6.0 (package engines say node >=22 although the docs page says Node 24+). The module exports only ApiError, Photon, PhotonError, ResponseValidationError and TransportError plus one *InputSchema/*OutputSchema per operation (zod-style objects with .parse and .shape). Construct with `new Photon({ headers: { Authorization: "Bearer pho_sk_..." } })` (optionally baseUrl). The client has account, auth, organizations, projects, system and raw; resource methods are instance properties, so Object.getOwnPropertyNames(Object.getPrototypeOf(c.projects)) shows nothing and you must use Object.keys(c.projects): agentProfile, billing, platforms, countMessages, createOrGetSpace, createOrGetUser, listMessages, sendMessage, listSpaces, listUsers, createWebhookDestination, setSpaceTyping, markMessageRead and more. Calls take one object: `c.projects.listMessages({ path: { projectId }, query: {...} })` and `c.projects.sendMessage({ path: { projectId }, body: {...}, headers: {"idempotency-key": ...} })`. An ApiError has operationId, requestId, status (number), headers, body and rawBody, where body is RFC 9457 problem details such as {type: "https://photon.codes/docs/problems/forbidden", title: "Forbidden", status: 403, code: "FORBIDDEN", requestId: "pho_req_..."}; message is "Photon API returned HTTP 403". A connection failure is a TransportError with message "Photon request failed" and no cause code attached.
