@delopay/sdk 0.123.0 → 0.125.0

package/dist/internal.cjs

@@ -809,6 +809,32 @@ var Connectors = class {
       { body: params }
     );
   }
+  /**
+   * What the processor says about this connector account: whether it will
+   * accept charges, which capabilities are live, and anything it is still
+   * waiting on.
+   *
+   * This is **not** {@link Connectors.verify}. That one asks whether the stored
+   * credentials work, by running a test-card authorization; a processor can
+   * revoke an account's ability to take payments while the credentials stay
+   * perfectly valid, and then a credential check reports healthy while every
+   * checkout silently stalls. This asks the account's own status instead, and
+   * is a plain read — it costs the merchant nothing and is safe to call twice.
+   *
+   * Connectors with no probe answer `state: 'unknown'` with
+   * `unknown_reason: 'connector_not_supported'`, rather than an error — every
+   * `'unknown'` carries a reason code you render your own words for. A router
+   * without this endpoint answers 404 — render that as "this build cannot
+   * report health", never as "healthy".
+   *
+   * `GET /account/{accountId}/connectors/{connectorId}/health`
+   */
+  async health(accountId, connectorId) {
+    return this.request(
+      "GET",
+      `/account/${encodeURIComponent(accountId)}/connectors/${encodeURIComponent(connectorId)}/health`
+    );
+  }
   /** Verify connector credentials. `POST /account/connectors/verify` */
   async verify(params) {
     return this.request("POST", "/account/connectors/verify", { body: params });
@@ -2527,6 +2553,23 @@ var Routing = class {
   async connectorCaps(profileId) {
     return this.request("GET", `/routing/connector-caps/${encodeURIComponent(profileId)}`);
   }
+  /**
+   * The live `routing_volume` counters behind a shop's active advanced
+   * program: one per distinct budget the program reads, each with the window
+   * it covers, the figure in the pinned threshold currency, and the rules that
+   * read it. Lets a merchant see whether a `routing_volume < 50000` rule is at
+   * 120 or at 499 today, and support answer why a payment went to the overflow
+   * connector.
+   *
+   * What routing will use right now, not what the shop turned over: the
+   * counters are held in Redis only and a lost Redis restarts the window at
+   * zero. Read-only; needs the same permission as reading the rules.
+   *
+   * `GET /routing/volume-counters/{profileId}`
+   */
+  async volumeCounters(profileId) {
+    return this.request("GET", `/routing/volume-counters/${encodeURIComponent(profileId)}`);
+  }
   /**
    * Replace a shop's per-connector payment caps.
    *