@peektravel/app-utilities 0.9.4 → 1.0.0

package/docs/webhooks.md

@@ -369,6 +369,12 @@ It throws if `install.platform` is `null` or unrecognised — an install with an
 unknown platform has no service to route to, and silently defaulting would point
 it at the wrong gateway.
 
+`createAccessServiceForInstall` sets Peek's **required** `mode: "v2"` for you (a
+registry install is always the v2 connection). If you construct `PeekAccessService`
+by hand instead, `mode` is mandatory — pass `mode: "v2"` together with the
+`apiUrl`. (`mode: "v1"` is the deprecated legacy gateway and needs `gatewayKey`;
+see the README's *Connection mode* section.)
+
 Prefer this (or the config's `apiUrl` field) over `baseUrl`/`appId`, which are
 deprecated: they reconstruct the URL with a hardcoded gateway default that cannot
 be correct for every install. **The hardcoded base-URL fallbacks will be removed

package/llms.txt

@@ -22,13 +22,25 @@ const peek = new PeekAccessService({
   installId,   // JWT subject
   jwtSecret,   // HMAC secret signing the JWT
   issuer,      // app name (JWT issuer)
+  mode: "v2",  // REQUIRED connection generation: "v2" (registry, use going forward) | "v1" (legacy, deprecated)
   apiUrl,      // the install webhook's apiUrl — the base API URL; each service appends its own backoffice slug
-  // optional: gatewayKey, tokenTtlSeconds, tokenRefreshLeewaySeconds,
+  // optional: gatewayKey (v1 only), tokenTtlSeconds, tokenRefreshLeewaySeconds,
   // retryDelaysMs, logger, fetch, itemOptionsPageSize,
   // accessOptions: { fullCustomerAccess: false }  // default — see "Access options / PII"
 });
 ```
 
+`mode` is **required** — choose the connection explicitly. `"v2"` is the
+app-registry connection and **requires** the install webhook's `apiUrl` (persisted
+per install); the constructor throws without it. If you don't have a webhook
+`apiUrl` yet, build one by appending your **app slug** to the registry prefix and
+pass that: `https://apps.peek.com/installations-api/<app-slug>` (same shape as the
+webhook's `api.url`; the trailing app-slug segment is required — the prefix alone
+is not a valid URL). Transitional bridge — prefer the webhook URL. `"v1"` is the legacy gateway
+(needs `appId` + `gatewayKey`) and is **`@deprecated`** — passing `mode: "v1"` is
+the fastest update for an install that relied on the old implicit default, but
+migrate to `"v2"`. Omitting `mode` throws from the constructor.
+
 Targeting an install by URL: pass the install webhook's `apiUrl` as the config
 `apiUrl`. It is the install's **base API URL**; each service class appends its own
 backoffice slug (e.g. `peek_backoffice_api-v1`, from a small per-platform endpoint
@@ -56,7 +68,7 @@ per call, and applies to every service that access service hands out.
 
 ```ts
 const peek = new PeekAccessService({
-  installId, jwtSecret, issuer, appId, gatewayKey,
+  installId, jwtSecret, issuer, mode: "v2", apiUrl,
   accessOptions: { fullCustomerAccess: true },  // opt in to PII + payment ops
 });
 ```
@@ -166,6 +178,12 @@ final authority and may still reject the request.
   `getAllReviewSummaries()` → `ProductReviewSummary[]` (one per activity:
   `avgRating` — decimal, `null` when no ratings — plus `countTotal` and per-star
   `countOneStar`…`countFiveStar`). No PII; unaffected by `fullCustomerAccess`.
+- `getCustomQuestionService()` — `getAll()` returns every custom question defined
+  on the account (across all activities) as the same `CustomQuestion[]` shape as
+  `getProductService().getCustomQuestions(productId)`. The account-wide catalog
+  carries no per-activity config, so `order` is `0` and `isRequired` is `false` on
+  every entry. Question definitions, not answers — no PII; unaffected by
+  `fullCustomerAccess`.
 
 ## Sibling accessors (CNG, ACME — REST, not GraphQL)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@peektravel/app-utilities",
-  "version": "0.9.4",
+  "version": "1.0.0",
   "description": "GraphQL JS mapping utilities extracted from the Peek Pro Autopilot connector.",
   "license": "MIT",
   "repository": {