@myapihq/sdk 2.31.2 → 2.31.4

package/dist/client.d.ts

@@ -11,6 +11,15 @@ export declare class MyApiError extends Error {
      * nothing support could trace. It is the only useful thing about a 500.
      */
     requestId?: string;
+    /**
+     * The HTTP method of the failed request, when the SDK knows it.
+     *
+     * Present so callers can tell a failed READ from a failed WRITE. The CLI's
+     * 5xx message used to tell everyone "whether the change went through is not
+     * knowable from here" — true and important after a POST, and simply false
+     * after `pixel audience`, which changes nothing.
+     */
+    method?: string;
     constructor(code: string, status: number, detail?: string | undefined, body?: Record<string, unknown> | undefined);
 }
 /**
@@ -42,7 +51,7 @@ export interface RequestOptions {
      */
     onReplay?: () => void;
 }
-export declare function toError(err: any, status: number, requestId?: string): MyApiError;
+export declare function toError(err: any, status: number, requestId?: string, method?: string): MyApiError;
 export declare function request<T>(method: string, url: string, apiKey?: string, body?: unknown, extraHeaders?: Record<string, string>, opts?: RequestOptions): Promise<T>;
 export interface Page<T> {
     data: T[];

package/dist/client.js

@@ -23,6 +23,15 @@ class MyApiError extends Error {
      * nothing support could trace. It is the only useful thing about a 500.
      */
     requestId;
+    /**
+     * The HTTP method of the failed request, when the SDK knows it.
+     *
+     * Present so callers can tell a failed READ from a failed WRITE. The CLI's
+     * 5xx message used to tell everyone "whether the change went through is not
+     * knowable from here" — true and important after a POST, and simply false
+     * after `pixel audience`, which changes nothing.
+     */
+    method;
     constructor(code, status, detail, body) {
         // Surface the detail in the message so console.error / err.message
         // shows useful info without callers having to look at err.detail.
@@ -256,7 +265,7 @@ async function parseResponse(method, url, response) {
         throw new MyApiError('invalid_json_response', response.status, `${method} ${url} returned non-JSON (status ${response.status}): ${snippet}\n${diagnoseNonJson(response.status, raw)}`);
     }
     if (!response.ok) {
-        throw toError(result?.error, response.status, pickRequestId(result));
+        throw toError(result?.error, response.status, pickRequestId(result), method);
     }
     // A few routes answer 2xx with a BARE object — no {success, data, error,
     // meta} envelope. `pixel identity` and `pixel events` are the two we have
@@ -273,7 +282,7 @@ async function parseResponse(method, url, response) {
     }
     const apiResponse = result;
     if (!apiResponse.success) {
-        throw toError(apiResponse.error, response.status);
+        throw toError(apiResponse.error, response.status, undefined, method);
     }
     return apiResponse;
 }
@@ -301,7 +310,7 @@ function pickRequestId(result) {
     const meta = result?.meta;
     return typeof meta?.request_id === 'string' && meta.request_id ? meta.request_id : undefined;
 }
-function toError(err, status, requestId) {
+function toError(err, status, requestId, method) {
     const obj = typeof err === 'object' && err !== null ? err : undefined;
     const code = obj ? (obj.code || 'unknown_error') : (err || 'unknown_error');
     const pick = (v) => (typeof v === 'string' && v.trim() !== '' ? v : undefined);
@@ -309,6 +318,8 @@ function toError(err, status, requestId) {
     const e = new MyApiError(code, status, detail, obj);
     if (requestId)
         e.requestId = requestId;
+    if (method)
+        e.method = method;
     return e;
 }
 // Returns the unwrapped `data` payload — the common case.

package/dist/config.js

@@ -28,7 +28,14 @@ exports.WORKFLOW_BASE = process.env.MYAPI_WORKFLOW_URL ?? 'https://api.myworkflo
 exports.EMAIL_BASE = process.env.MYAPI_EMAIL_URL ?? 'https://api.myemailapi.com';
 exports.STORAGE_BASE = process.env.MYAPI_STORAGE_URL ?? 'https://api.mystorageapi.com';
 exports.URL_BASE = process.env.MYAPI_URL_URL ?? 'https://api.myurlto.com';
-exports.PIXEL_BASE = process.env.MYAPI_PIXEL_URL ?? 'https://api.mypixelapi.com';
+// api.mypixelapi.com resolves and answers, which is why this looked wired. It
+// answers `401 {"error":"Unauthorized"}` to a valid platform key on EVERY pixel
+// route — note the bare body, not our envelope: it is a different service that
+// does not share our key space. So every `myapi pixel …` command has failed
+// with "Invalid API key. Run: myapi account setup" since the initial release,
+// and setup cannot fix it. The gateway serves the whole pixel surface with the
+// same key (visits, events, interactions, identity, identify all verified).
+exports.PIXEL_BASE = process.env.MYAPI_PIXEL_URL ?? GATEWAY;
 // Per-service hosts below either don't resolve in DNS or 404 the routes;
 // served via the gateway until backend wires the brand routing. Flip back
 // to per-service hosts when DNS is sound and routes verified there.

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const SDK_VERSION = "2.31.2";
+export declare const SDK_VERSION = "2.31.4";

package/dist/version.js

@@ -8,4 +8,4 @@ exports.SDK_VERSION = void 0;
 // Why a constant and not a package.json read: the SDK runs inside edge
 // functions (Cloudflare Workers), so it must not import node:fs. A literal
 // is the only version source that works in every runtime we ship to.
-exports.SDK_VERSION = '2.31.2';
+exports.SDK_VERSION = '2.31.4';

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/sdk",
   "license": "Apache-2.0",
-  "version": "2.31.2",
+  "version": "2.31.4",
   "description": "TypeScript SDK for the MyAPI ecosystem",
   "repository": {
     "type": "git",