@myapihq/cli 2.31.2 → 2.31.4

package/dist/commands/pixel.js

@@ -87,7 +87,7 @@ export async function visits(flags) {
         ts: v.ts,
     })));
     // /visits returns only {visits, total} — it does NOT echo limit/offset the
-    // way /events and /interactions do, so this used to print
+    // way /interactions does, so this used to print
     // "Showing: undefined | Offset: undefined". Report what the response
     // actually carries.
     info(`Total: ${res.total} | Showing: ${res.visits.length}`);
@@ -128,7 +128,11 @@ export async function events(flags) {
         campaign_id: e.campaign_id ?? '',
         ts: e.ts,
     })));
-    info(`Total: ${res.total} | Showing: ${res.limit} | Offset: ${res.offset}`);
+    // /events returns {events, total} — the limit/offset echo the visits comment
+    // above attributes to it is in `meta`, which the SDK does not surface, so
+    // this printed "Showing: undefined | Offset: undefined" too. Only
+    // /interactions genuinely echoes them in the body.
+    info(`Total: ${res.total} | Showing: ${res.events.length}`);
 }
 // Geographic distribution sample of the org's pixel audience.
 export async function audience(flags) {

package/dist/errors.js

@@ -144,7 +144,16 @@ export function friendlyError(err) {
         lines.push(err.requestId
             ? `  Quote this when reporting it: ${err.requestId}`
             : '  No request id came back, so quote the exact command and the time instead.');
-        lines.push('  Whether the change went through is not knowable from here — check before retrying.');
+        // Only for a request that could have changed something. A 500 can land
+        // before or after a write, so the warning is right for POST/PATCH/DELETE —
+        // but `pixel audience` is a GET, and telling someone to go and check
+        // whether their read went through sends them looking for a change that
+        // could not exist. Unknown method keeps the warning: silence about a
+        // possible half-applied write is the worse failure.
+        const read = err.method === 'GET' || err.method === 'HEAD';
+        if (!read) {
+            lines.push('  Whether the change went through is not knowable from here — check before retrying.');
+        }
         return withOrgContext(lines.join('\n'), err);
     }
     const base = ERROR_MESSAGES[err.code] || err.code;

package/dist/errors.test.js

@@ -139,3 +139,29 @@ function looksLikeBadKey(err) {
     ]);
     return err.status === 401 && (!err.code || AUTH_CODES.has(String(err.code).toLowerCase()));
 }
+// A 500 on a GET used to end with "Whether the change went through is not
+// knowable from here — check before retrying." `pixel audience` is a read; it
+// sent people to look for a change that could not exist. Found 2026-08-24 while
+// fixing PIXEL_BASE, when the command finally reached the platform at all.
+describe('5xx advice distinguishes a read from a write', () => {
+    function err(method) {
+        const e = new MyApiError('ANALYTICS_ERROR', 502, 'analytics query failed');
+        e.requestId = 'req_test';
+        if (method)
+            e.method = method;
+        return e;
+    }
+    it('says nothing about a change after a failed GET', () => {
+        const msg = friendlyError(err('GET'));
+        expect(msg).not.toContain('went through');
+        expect(msg).toContain('req_test');
+        expect(msg).toContain('our fault');
+    });
+    it('still warns after a failed write', () => {
+        expect(friendlyError(err('POST'))).toContain('went through');
+        expect(friendlyError(err('DELETE'))).toContain('went through');
+    });
+    it('keeps the warning when the method is unknown', () => {
+        expect(friendlyError(err())).toContain('went through');
+    });
+});

package/dist/flags.js

@@ -22,6 +22,9 @@ export const GLOBAL_FLAGS = {
     version: 'boolean',
     org: 'string',
 };
+// Value flags that name one target rather than a list, mapped to the noun used
+// when refusing a duplicate. Comma-separating these is not a workaround.
+const SINGLE_VALUED = new Map([['org', 'organisation']]);
 // Short aliases are consumed as `-h` / `-v` / `-V` before the `--flag` branch,
 // so they never appear as keys in `merged` and need no type — but they do land
 // in `flags` (as help/version), so the dispatcher must still tolerate them.
@@ -134,10 +137,20 @@ export function parseFlags(argv, schema = {}, quiet = false) {
             // mistake when the docs say "comma-separated"; silently honouring the
             // last is the one behaviour that can't be recovered from. Refuse, and
             // say what to do instead.
+            //
+            // The comma-separated suggestion is right for a flag that names a list of
+            // things and wrong for one that names a single target: a command writes to
+            // one organisation, so `--org a,b` would just build an id that matches no
+            // org. Say which case this is rather than offering advice that cannot work.
             if (seenValueFlags.has(key)) {
-                throw new Error(`--${key} was given more than once. Only the last value would be used, ` +
-                    `which silently discards the others.\n` +
-                    `→ If you meant to pass several values, comma-separate them: --${key} a,b,c`);
+                const previous = flags[key];
+                throw new Error(SINGLE_VALUED.has(key)
+                    ? `--${key} was given more than once ("${String(previous)}", then "${raw}"). ` +
+                        `Only the last would be used, which silently discards the first.\n` +
+                        `→ A command acts on one ${SINGLE_VALUED.get(key)}. Pass --${key} once.`
+                    : `--${key} was given more than once. Only the last value would be used, ` +
+                        `which silently discards the others.\n` +
+                        `→ If you meant to pass several values, comma-separate them: --${key} a,b,c`);
             }
             seenValueFlags.add(key);
             if (type === 'number') {

package/dist/flags.test.js

@@ -206,6 +206,19 @@ describe('global flag lists cannot drift', () => {
         // other nineteen silently kept the last value. Parse with an empty schema
         // to stand in for a command that declares nothing of its own.
         expect(() => parseFlags(['--org', 'ORG_A', '--org', 'ORG_B'], {}, true)).toThrow(/--org was given more than once/);
+        // The generic advice ("comma-separate them") cannot work for org: a command
+        // writes to one organisation, and --org a,b is just an id that matches none.
+        let msg = '';
+        try {
+            parseFlags(['--org', 'ORG_A', '--org', 'ORG_B'], {}, true);
+        }
+        catch (e) {
+            msg = e.message;
+        }
+        expect(msg).not.toContain('comma-separate');
+        expect(msg).toContain('acts on one organisation');
+        expect(msg).toContain('ORG_A');
+        expect(msg).toContain('ORG_B');
     });
     it('a single --org still parses to its value under an empty schema', () => {
         const { flags } = parseFlags(['--org', 'ORG_A'], {}, true);

package/dist/skills/my-pixel-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Tracking pixel + identity resolution for MyAPI funnels and email. Capture visits and events, resolve known users to anonymous sessions, stream interaction events for analytics. Pairs with mycrmapi for auto-ingest of pixel_visit events on known contacts.
 triggers: [pixel, analytics, tracking, visit, event, identity, session, attribution, geo, open pixel]
-checksum: sha256-2c6508a5fdfa752cc5fd4231c087380e6d904f514973830a34e919b277ad31de
+checksum: sha256-4be497d5db05dbca3646b76b3385c22f84de4726d1049a7d9876c054159e4a58
 ---
 
 # MyPixelAPI
@@ -103,7 +103,7 @@ graph across the visitor's sessions.
 <!-- http:start -->
 <!-- generated by `npm run canonical-sync` — do not edit -->
 ```
-base   https://api.mypixelapi.com
+base   https://api.myapihq.com
 path   POST /pixel/orgs/{org_id}/identify
 auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
 reply  { "success": true, "data": …, "error": null, "meta": {…} }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.31.2",
+  "version": "2.31.4",
   "description": "MyAPI command-line interface",
   "repository": {
     "type": "git",
@@ -47,7 +47,7 @@
     "lint:skills:strict": "node scripts/copy-skills.js && node scripts/lint-skills.js --strict"
   },
   "dependencies": {
-    "@myapihq/sdk": "^2.31.2"
+    "@myapihq/sdk": "^2.31.4"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",