@dsptch-work/api-client 0.8.0 → 0.9.0

package/dist/gen/sdk.gen.js

@@ -2234,6 +2234,61 @@ export class Forms {
             ...options
         });
     }
+    /**
+     * List form submission versions
+     *
+     * Change feed for form submissions, following the API-wide change-feed
+     * contract (see "Change feeds" in the API overview): poll with
+     * `filter[created_at][gte]` set to your watermark, deduplicate on
+     * `(id, event, timestamp)`, and advance the watermark only to
+     * `meta.complete_through`. The feed carries `destroy` events only, returned
+     * oldest event first: archiving hard-deletes the row, so the live index
+     * offers no deletion signal, while creates and updates surface there through
+     * `created_at` / `updated_at` — and un-archiving does not exist in the
+     * product, so a `destroy` here is final.
+     *
+     * Events are guaranteed for at least the last 30 days. Older events are
+     * served for as long as they remain stored, and may be removed without
+     * notice. Past the retention window, or after a lost watermark, resync by
+     * re-listing the live index and diffing your replica.
+     *
+     * One request covers at most 32 days of event time, and
+     * `filter[created_at][gte]` and `[lte]` place that interval anywhere in the
+     * feed's history. Sending only `[gte]` covers the 32 days after it, only
+     * `[lte]` the 32 days before it, and neither the 32 days beginning 30 days
+     * ago. A wider interval is refused with a `422` of type `interval_too_wide`
+     * rather than narrowed to fit — split it into consecutive windows and read
+     * them in order, and their pages join without gaps. Both bounds are
+     * inclusive, so an event stamped exactly on a shared bound appears in both
+     * pages — deduplicate as usual. An interval whose `[lte]` precedes its
+     * `[gte]` is refused too, as a `422` of type `invalid_filter_value`, rather
+     * than answered with the empty page it names.
+     *
+     * `meta.complete_through` is never later than the end of the interval you
+     * asked for, so a request ending in the past reports its own `[lte]`.
+     * Advancing your watermark to it walks a consumer that has fallen behind
+     * forward one window per poll, rather than past events no response carried.
+     *
+     * Visibility is re-derived from the definition and submitter retained on the
+     * event; the live index also grants access through a job assignment, which
+     * archival clears, so a user-scoped key sees a subset of its index-visible
+     * events, never a superset. A company-scoped key reads the whole tenant and
+     * is unaffected. `timestamp` (and the `filter[created_at]` range) is the
+     * time the event occurred, not the submission's own timestamps.
+     *
+     *
+     * **Required scope:**
+     *
+     * `form_submissions.deltas:read`
+     *
+     */
+    static listFormSubmissionDeltas(options) {
+        return (options?.client ?? client).get({
+            security: [{ name: 'X-Api-Key', type: 'apiKey' }],
+            url: '/api/v1/form_submissions/deltas',
+            ...options
+        });
+    }
     /**
      * List form submissions
      *
@@ -4203,12 +4258,37 @@ export class TimeEntries {
      * overview): poll with `filter[created_at][gte]` set to your
      * watermark, deduplicate on `(id, event, timestamp)`, and
      * advance the watermark only to `meta.complete_through`.
-     * The feed carries `create`, `update`, and `destroy` events
-     * for the last 30 days, returned oldest event first. A
-     * watermark older than that window is refused with a `422`
-     * rather than answered with a page that cannot be complete —
-     * resync by re-crawling `/api/v1/time_entries` and diffing
-     * against your replica.
+     * The feed carries `create`, `update`, and `destroy` events,
+     * returned oldest event first.
+     *
+     * Events are guaranteed for at least the last 30 days. Older
+     * events are served for as long as they remain stored, and
+     * may be removed without notice.
+     *
+     * One request covers at most 32 days of event time, and
+     * `filter[created_at][gte]` and `[lte]` place that interval
+     * anywhere in the feed's history. Sending only `[gte]`
+     * covers the 32 days after it, only `[lte]` the 32 days
+     * before it, and neither the 32 days beginning 30 days ago.
+     * A wider interval is refused with a `422` of type
+     * `interval_too_wide` rather than narrowed to fit — split it
+     * into consecutive windows and read them in order, and their
+     * pages join without gaps. Both bounds are inclusive, so an
+     * event stamped exactly on a shared bound appears in both
+     * pages — deduplicate as usual. An interval whose `[lte]`
+     * precedes its `[gte]` is refused too, as a `422` of type
+     * `invalid_filter_value`, rather than answered with the empty
+     * page it names.
+     *
+     * `meta.complete_through` is never later than the end of the
+     * interval you asked for, so a request ending in the past
+     * reports its own `[lte]`. Advancing your watermark to it
+     * walks a consumer that has fallen behind forward one window
+     * per poll, rather than past events no response carried.
+     *
+     * `filter[event]` narrows the payload, not the work: the
+     * feed is indexed on event time, so a filtered request costs
+     * what an unfiltered one over the same interval costs.
      *
      *
      * **Required scope:**
@@ -4308,8 +4388,8 @@ export class TimeEntries {
      * optional and only supplied fields change. Authorization is re-checked after
      * attributes are assigned, so moving the entry to a time card in another
      * company is forbidden (403). If the change would push categorized allocation
-     * minutes past the time card's worked minutes, the request returns 422 unless
-     * confirm_allocation_conflict is sent true. The feature-allocation cap is
+     * minutes past the time card's overtime eligible minutes, the request returns
+     * 422 unless confirm_allocation_conflict is sent true. The feature-allocation cap is
      * enforced, and because a persisted feature_ids= writes its join rows
      * immediately, a rejected save rolls them back within the enclosing
      * transaction.
@@ -4673,7 +4753,7 @@ export class AttestationConfigs {
     static listAttestationConfigs(options) {
         return (options.client ?? client).get({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/attestation_configs',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/attestation_configs',
             ...options
         });
     }
@@ -4688,7 +4768,7 @@ export class AttestationConfigs {
     static createAttestationConfig(options) {
         return (options.client ?? client).post({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/attestation_configs',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/attestation_configs',
             ...options,
             headers: {
                 'Content-Type': 'application/json',
@@ -4707,7 +4787,7 @@ export class AttestationConfigs {
     static deleteAttestationConfig(options) {
         return (options.client ?? client).delete({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/attestation_configs/{id}',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/attestation_configs/{id}',
             ...options
         });
     }
@@ -4722,7 +4802,7 @@ export class AttestationConfigs {
     static getAttestationConfig(options) {
         return (options.client ?? client).get({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/attestation_configs/{id}',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/attestation_configs/{id}',
             ...options
         });
     }
@@ -4750,7 +4830,7 @@ export class PaySchedules {
     static listPayPeriodConfigHistory(options) {
         return (options.client ?? client).get({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/history',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/history',
             ...options
         });
     }
@@ -4780,7 +4860,7 @@ export class PaySchedules {
     static getPayPeriodConfig(options) {
         return (options.client ?? client).get({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{uid}',
+            url: '/api/v1/timekeeping/pay_period_configs/{id}',
             ...options
         });
     }
@@ -4797,7 +4877,7 @@ export class Holidays {
     static listHolidays(options) {
         return (options.client ?? client).get({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/holidays',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/holidays',
             ...options
         });
     }
@@ -4812,7 +4892,7 @@ export class Holidays {
     static createHoliday(options) {
         return (options.client ?? client).post({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/holidays',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/holidays',
             ...options,
             headers: {
                 'Content-Type': 'application/json',
@@ -4831,7 +4911,7 @@ export class Holidays {
     static deleteHoliday(options) {
         return (options.client ?? client).delete({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/holidays/{id}',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/holidays/{id}',
             ...options
         });
     }
@@ -4846,7 +4926,7 @@ export class Holidays {
     static updateHoliday(options) {
         return (options.client ?? client).patch({
             security: [{ name: 'X-Api-Key', type: 'apiKey' }],
-            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_uid}/holidays/{id}',
+            url: '/api/v1/timekeeping/pay_period_configs/{pay_period_config_id}/holidays/{id}',
             ...options,
             headers: {
                 'Content-Type': 'application/json',