@greensecurity/javascript-sdk 0.46.0-beta.6 → 0.46.0-beta.7

package/src/models/components/vendorcredentialsummary.ts

@@ -171,6 +171,7 @@ export type VendorCredentialSummary = {
    * The date from which the vendor credential is valid, or `null` if not set.
    */
   dateValid?: string | null | undefined;
+  dateSubmittedPendingPayment?: string | null | undefined;
   /**
    * Free-form notes about the vendor credential, or `null` if there are none.
    */
@@ -191,6 +192,17 @@ export type VendorCredentialSummary = {
    * Whether the credential applies to the vendor's whole company instead of the individual vendor, or `null` if unknown.
    */
   appliesToCompany?: boolean | null | undefined;
+  /**
+   * Only populated on GET .../history; omitted everywhere else this schema is used (e.g.
+   *
+   * @remarks
+   * GET .../credentials/:id). Whether the currently logged in user is the one who first
+   * submitted this version (the vendor themselves, or the company manager who acted on
+   * their behalf) - not whether they most recently touched it. `false` also covers a
+   * version whose submitter could not be determined (it predates this field and a one-time
+   * backfill from older data found no match), not only one submitted by someone else.
+   */
+  submittedByCurrentUser?: boolean | undefined;
   /**
    * The credential this vendor credential is for, as an object or as its ID.
    */
@@ -470,11 +482,13 @@ export const VendorCredentialSummary$inboundSchema: z.ZodType<
   date_expires: z.nullable(types.string()).optional(),
   date_expedited: z.nullable(types.string()).optional(),
   date_valid: z.nullable(types.string()).optional(),
+  date_submitted_pending_payment: z.nullable(types.string()).optional(),
   notes: z.nullable(types.string()).optional(),
   json_data: z.nullable(types.string()).optional(),
   filename: z.nullable(types.string()).optional(),
   alternate_id: z.nullable(types.number()).optional(),
   applies_to_company: z.nullable(types.boolean()).optional(),
+  submitted_by_current_user: types.optional(types.boolean()),
   credential: z.nullable(smartUnion([Credential$inboundSchema, types.number()]))
     .optional(),
   vendor: z.nullable(smartUnion([Vendor$inboundSchema, types.number()]))
@@ -522,9 +536,11 @@ export const VendorCredentialSummary$inboundSchema: z.ZodType<
     "date_expires": "dateExpires",
     "date_expedited": "dateExpedited",
     "date_valid": "dateValid",
+    "date_submitted_pending_payment": "dateSubmittedPendingPayment",
     "json_data": "jsonData",
     "alternate_id": "alternateId",
     "applies_to_company": "appliesToCompany",
+    "submitted_by_current_user": "submittedByCurrentUser",
     "vendor_credential_files": "vendorCredentialFiles",
     "latest_vendor_credential_id": "latestVendorCredentialId",
     "previously_approved": "previouslyApproved",

package/src/react-query/eventsListFeed.ts

@@ -80,15 +80,16 @@ export type EventsListFeedQueryError =
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission.
  * The caller's role and their relationship to the record decide what the response includes.
  *
- * Returns `Event` items with the `event.creator` and `event.invitees` scopes already applied,
- * so the server populates `event_creator`, `event_creator_img_url` and `invitees`—the fields this
- * feed has always carried. SDK builds below `0.55.0-beta.1` receive the older `Feed` shape
- * instead, in which `facility` and `department` are name strings, not ids; the server
- * chooses by the `X-SDK-User-Agent` header the SDK sends, so an existing client keeps the
- * shape it was generated against until you regenerate it.
+ * Returns `Event` items with the `event.creator`, `event.invitees`, `event.facility` and
+ * `event.department` scopes already applied, so the server populates `event_creator`,
+ * `event_creator_img_url` and `invitees`, and `facility` and `department` are `{ id, name }`
+ * summaries—the fields this feed has always carried. SDK builds below `0.46.0-beta.1`
+ * receive the older `Feed` shape instead, in which `facility` and `department` are name
+ * strings, not ids; the server chooses by the `X-SDK-User-Agent` header the SDK sends, so an
+ * existing client keeps the shape it was generated against until you regenerate it.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
  * build against it.
  */
 export function useEventsListFeed(
@@ -115,15 +116,16 @@ export function useEventsListFeed(
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission.
  * The caller's role and their relationship to the record decide what the response includes.
  *
- * Returns `Event` items with the `event.creator` and `event.invitees` scopes already applied,
- * so the server populates `event_creator`, `event_creator_img_url` and `invitees`—the fields this
- * feed has always carried. SDK builds below `0.55.0-beta.1` receive the older `Feed` shape
- * instead, in which `facility` and `department` are name strings, not ids; the server
- * chooses by the `X-SDK-User-Agent` header the SDK sends, so an existing client keeps the
- * shape it was generated against until you regenerate it.
+ * Returns `Event` items with the `event.creator`, `event.invitees`, `event.facility` and
+ * `event.department` scopes already applied, so the server populates `event_creator`,
+ * `event_creator_img_url` and `invitees`, and `facility` and `department` are `{ id, name }`
+ * summaries—the fields this feed has always carried. SDK builds below `0.46.0-beta.1`
+ * receive the older `Feed` shape instead, in which `facility` and `department` are name
+ * strings, not ids; the server chooses by the `X-SDK-User-Agent` header the SDK sends, so an
+ * existing client keeps the shape it was generated against until you regenerate it.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
  * build against it.
  */
 export function useEventsListFeedSuspense(
@@ -153,15 +155,16 @@ export function useEventsListFeedSuspense(
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission.
  * The caller's role and their relationship to the record decide what the response includes.
  *
- * Returns `Event` items with the `event.creator` and `event.invitees` scopes already applied,
- * so the server populates `event_creator`, `event_creator_img_url` and `invitees`—the fields this
- * feed has always carried. SDK builds below `0.55.0-beta.1` receive the older `Feed` shape
- * instead, in which `facility` and `department` are name strings, not ids; the server
- * chooses by the `X-SDK-User-Agent` header the SDK sends, so an existing client keeps the
- * shape it was generated against until you regenerate it.
+ * Returns `Event` items with the `event.creator`, `event.invitees`, `event.facility` and
+ * `event.department` scopes already applied, so the server populates `event_creator`,
+ * `event_creator_img_url` and `invitees`, and `facility` and `department` are `{ id, name }`
+ * summaries—the fields this feed has always carried. SDK builds below `0.46.0-beta.1`
+ * receive the older `Feed` shape instead, in which `facility` and `department` are name
+ * strings, not ids; the server chooses by the `X-SDK-User-Agent` header the SDK sends, so an
+ * existing client keeps the shape it was generated against until you regenerate it.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
  * build against it.
  */
 export function useEventsListFeedInfinite(
@@ -202,15 +205,16 @@ export function useEventsListFeedInfinite(
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission.
  * The caller's role and their relationship to the record decide what the response includes.
  *
- * Returns `Event` items with the `event.creator` and `event.invitees` scopes already applied,
- * so the server populates `event_creator`, `event_creator_img_url` and `invitees`—the fields this
- * feed has always carried. SDK builds below `0.55.0-beta.1` receive the older `Feed` shape
- * instead, in which `facility` and `department` are name strings, not ids; the server
- * chooses by the `X-SDK-User-Agent` header the SDK sends, so an existing client keeps the
- * shape it was generated against until you regenerate it.
+ * Returns `Event` items with the `event.creator`, `event.invitees`, `event.facility` and
+ * `event.department` scopes already applied, so the server populates `event_creator`,
+ * `event_creator_img_url` and `invitees`, and `facility` and `department` are `{ id, name }`
+ * summaries—the fields this feed has always carried. SDK builds below `0.46.0-beta.1`
+ * receive the older `Feed` shape instead, in which `facility` and `department` are name
+ * strings, not ids; the server chooses by the `X-SDK-User-Agent` header the SDK sends, so an
+ * existing client keeps the shape it was generated against until you regenerate it.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
  * build against it.
  */
 export function useEventsListFeedInfiniteSuspense(

package/src/react-query/eventsListPendingInvitations.ts

@@ -80,15 +80,16 @@ export type EventsListPendingInvitationsQueryError =
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission:
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
- * Returns `Invite` items with the `invite.event` and `invite.invitee` scopes already applied,
- * so `event` is the expanded `{ id, name }` summary instead of a bare id, and `invitee` is
- * populated—the appointment and the recipient this list has always named. This endpoint
- * takes no `expand` parameter; the endpoint always applies both scopes.
- * SDK builds earlier than `0.55.0-beta.1` receive the older `PendingInvitation` shape instead, which
+ * Returns `Invite` items with the `invite.event`, `invite.invitee`, `event.location` and
+ * `event.creator` scopes already applied. So `event` is the expanded summary instead of a bare
+ * id, with the appointment's dates, flags, notes, location and organizer, and `invitee` is
+ * populated with the recipient's name and thumbnail—what this list has always published. This
+ * endpoint takes no `expand` parameter; the endpoint always applies these scopes.
+ * SDK builds earlier than `0.46.0-beta.1` receive the older `PendingInvitation` shape instead, which
  * embeds the appointment.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListPendingInvitations(
@@ -121,15 +122,16 @@ export function useEventsListPendingInvitations(
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission:
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
- * Returns `Invite` items with the `invite.event` and `invite.invitee` scopes already applied,
- * so `event` is the expanded `{ id, name }` summary instead of a bare id, and `invitee` is
- * populated—the appointment and the recipient this list has always named. This endpoint
- * takes no `expand` parameter; the endpoint always applies both scopes.
- * SDK builds earlier than `0.55.0-beta.1` receive the older `PendingInvitation` shape instead, which
+ * Returns `Invite` items with the `invite.event`, `invite.invitee`, `event.location` and
+ * `event.creator` scopes already applied. So `event` is the expanded summary instead of a bare
+ * id, with the appointment's dates, flags, notes, location and organizer, and `invitee` is
+ * populated with the recipient's name and thumbnail—what this list has always published. This
+ * endpoint takes no `expand` parameter; the endpoint always applies these scopes.
+ * SDK builds earlier than `0.46.0-beta.1` receive the older `PendingInvitation` shape instead, which
  * embeds the appointment.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListPendingInvitationsSuspense(
@@ -162,15 +164,16 @@ export function useEventsListPendingInvitationsSuspense(
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission:
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
- * Returns `Invite` items with the `invite.event` and `invite.invitee` scopes already applied,
- * so `event` is the expanded `{ id, name }` summary instead of a bare id, and `invitee` is
- * populated—the appointment and the recipient this list has always named. This endpoint
- * takes no `expand` parameter; the endpoint always applies both scopes.
- * SDK builds earlier than `0.55.0-beta.1` receive the older `PendingInvitation` shape instead, which
+ * Returns `Invite` items with the `invite.event`, `invite.invitee`, `event.location` and
+ * `event.creator` scopes already applied. So `event` is the expanded summary instead of a bare
+ * id, with the appointment's dates, flags, notes, location and organizer, and `invitee` is
+ * populated with the recipient's name and thumbnail—what this list has always published. This
+ * endpoint takes no `expand` parameter; the endpoint always applies these scopes.
+ * SDK builds earlier than `0.46.0-beta.1` receive the older `PendingInvitation` shape instead, which
  * embeds the appointment.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListPendingInvitationsInfinite(
@@ -217,15 +220,16 @@ export function useEventsListPendingInvitationsInfinite(
  * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission:
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
- * Returns `Invite` items with the `invite.event` and `invite.invitee` scopes already applied,
- * so `event` is the expanded `{ id, name }` summary instead of a bare id, and `invitee` is
- * populated—the appointment and the recipient this list has always named. This endpoint
- * takes no `expand` parameter; the endpoint always applies both scopes.
- * SDK builds earlier than `0.55.0-beta.1` receive the older `PendingInvitation` shape instead, which
+ * Returns `Invite` items with the `invite.event`, `invite.invitee`, `event.location` and
+ * `event.creator` scopes already applied. So `event` is the expanded summary instead of a bare
+ * id, with the appointment's dates, flags, notes, location and organizer, and `invitee` is
+ * populated with the recipient's name and thumbnail—what this list has always published. This
+ * endpoint takes no `expand` parameter; the endpoint always applies these scopes.
+ * SDK builds earlier than `0.46.0-beta.1` receive the older `PendingInvitation` shape instead, which
  * embeds the appointment.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListPendingInvitationsInfiniteSuspense(

package/src/react-query/eventsListStandingAppointments.ts

@@ -81,13 +81,14 @@ export type EventsListStandingAppointmentsQueryError =
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
  * Returns `Event` items with the `event.location`, `event.attendees`, `event.viewer_invite`,
- * `event.creator` and `event.invitees` scopes already applied, so `location`, `attendees`,
- * `event_creator`, `event_creator_img_url` and `invitees` are populated and `status` carries
- * the reader's own outstanding invite. SDK builds earlier than `0.55.0-beta.1` receive the older
+ * `event.creator`, `event.invitees`, `event.facility` and `event.department` scopes already
+ * applied, so `location`, `attendees`, `event_creator`, `event_creator_img_url` and `invitees`
+ * are populated, `facility` and `department` are `{ id, name }` summaries, and `status` carries
+ * the reader's own outstanding invite. SDK builds earlier than `0.46.0-beta.1` receive the older
  * `StandingAppointment` shape instead.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListStandingAppointments(
@@ -121,13 +122,14 @@ export function useEventsListStandingAppointments(
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
  * Returns `Event` items with the `event.location`, `event.attendees`, `event.viewer_invite`,
- * `event.creator` and `event.invitees` scopes already applied, so `location`, `attendees`,
- * `event_creator`, `event_creator_img_url` and `invitees` are populated and `status` carries
- * the reader's own outstanding invite. SDK builds earlier than `0.55.0-beta.1` receive the older
+ * `event.creator`, `event.invitees`, `event.facility` and `event.department` scopes already
+ * applied, so `location`, `attendees`, `event_creator`, `event_creator_img_url` and `invitees`
+ * are populated, `facility` and `department` are `{ id, name }` summaries, and `status` carries
+ * the reader's own outstanding invite. SDK builds earlier than `0.46.0-beta.1` receive the older
  * `StandingAppointment` shape instead.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListStandingAppointmentsSuspense(
@@ -161,13 +163,14 @@ export function useEventsListStandingAppointmentsSuspense(
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
  * Returns `Event` items with the `event.location`, `event.attendees`, `event.viewer_invite`,
- * `event.creator` and `event.invitees` scopes already applied, so `location`, `attendees`,
- * `event_creator`, `event_creator_img_url` and `invitees` are populated and `status` carries
- * the reader's own outstanding invite. SDK builds earlier than `0.55.0-beta.1` receive the older
+ * `event.creator`, `event.invitees`, `event.facility` and `event.department` scopes already
+ * applied, so `location`, `attendees`, `event_creator`, `event_creator_img_url` and `invitees`
+ * are populated, `facility` and `department` are `{ id, name }` summaries, and `status` carries
+ * the reader's own outstanding invite. SDK builds earlier than `0.46.0-beta.1` receive the older
  * `StandingAppointment` shape instead.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListStandingAppointmentsInfinite(
@@ -215,13 +218,14 @@ export function useEventsListStandingAppointmentsInfinite(
  * the caller's role and their relationship to the record decide what the endpoint returns.
  *
  * Returns `Event` items with the `event.location`, `event.attendees`, `event.viewer_invite`,
- * `event.creator` and `event.invitees` scopes already applied, so `location`, `attendees`,
- * `event_creator`, `event_creator_img_url` and `invitees` are populated and `status` carries
- * the reader's own outstanding invite. SDK builds earlier than `0.55.0-beta.1` receive the older
+ * `event.creator`, `event.invitees`, `event.facility` and `event.department` scopes already
+ * applied, so `location`, `attendees`, `event_creator`, `event_creator_img_url` and `invitees`
+ * are populated, `facility` and `department` are `{ id, name }` summaries, and `status` carries
+ * the reader's own outstanding invite. SDK builds earlier than `0.46.0-beta.1` receive the older
  * `StandingAppointment` shape instead.
  *
- * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
- * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
+ * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+ * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
  * build compares against it.
  */
 export function useEventsListStandingAppointmentsInfiniteSuspense(

package/src/react-query/vendorsGetVendorCredentialDetails.ts

@@ -63,6 +63,10 @@ export type VendorsGetVendorCredentialDetailsQueryError =
  * is expanded, a company manager viewing a vendor-owned credential (not a company-owned one) only
  * receives the files they personally uploaded on the vendor's behalf.
  *
+ * For that same restricted company manager, `json_data` is returned as `null` unless they are the
+ * one who first submitted this version of the credential - everything else in the response
+ * (status, dates, notes, credential/invoice/etc.) is unaffected.
+ *
  * The following `expand` scopes are available:
  *
  * - `vendor_credential.credential`
@@ -127,6 +131,10 @@ export function useVendorsGetVendorCredentialDetails(
  * is expanded, a company manager viewing a vendor-owned credential (not a company-owned one) only
  * receives the files they personally uploaded on the vendor's behalf.
  *
+ * For that same restricted company manager, `json_data` is returned as `null` unless they are the
+ * one who first submitted this version of the credential - everything else in the response
+ * (status, dates, notes, credential/invoice/etc.) is unaffected.
+ *
  * The following `expand` scopes are available:
  *
  * - `vendor_credential.credential`

package/src/react-query/vendorsListVendorCredentialHistory.ts

@@ -78,6 +78,10 @@ export type VendorsListVendorCredentialHistoryQueryError =
  * Lists vendor credentials history
  *
  * **Permissions.** Requires the `vendor_credentials.view` permission.
+ *
+ * Each item's `submitted_by_current_user` says whether the calling user is the one who first
+ * submitted that version, so a vendor or company manager can tell their own submissions apart
+ * from ones made by someone else with access to the same credential.
  */
 export function useVendorsListVendorCredentialHistory(
   request: operations.ListVendorCredentialHistoryRequest,
@@ -107,6 +111,10 @@ export function useVendorsListVendorCredentialHistory(
  * Lists vendor credentials history
  *
  * **Permissions.** Requires the `vendor_credentials.view` permission.
+ *
+ * Each item's `submitted_by_current_user` says whether the calling user is the one who first
+ * submitted that version, so a vendor or company manager can tell their own submissions apart
+ * from ones made by someone else with access to the same credential.
  */
 export function useVendorsListVendorCredentialHistorySuspense(
   request: operations.ListVendorCredentialHistoryRequest,
@@ -136,6 +144,10 @@ export function useVendorsListVendorCredentialHistorySuspense(
  * Lists vendor credentials history
  *
  * **Permissions.** Requires the `vendor_credentials.view` permission.
+ *
+ * Each item's `submitted_by_current_user` says whether the calling user is the one who first
+ * submitted that version, so a vendor or company manager can tell their own submissions apart
+ * from ones made by someone else with access to the same credential.
  */
 export function useVendorsListVendorCredentialHistoryInfinite(
   request: operations.ListVendorCredentialHistoryRequest,
@@ -179,6 +191,10 @@ export function useVendorsListVendorCredentialHistoryInfinite(
  * Lists vendor credentials history
  *
  * **Permissions.** Requires the `vendor_credentials.view` permission.
+ *
+ * Each item's `submitted_by_current_user` says whether the calling user is the one who first
+ * submitted that version, so a vendor or company manager can tell their own submissions apart
+ * from ones made by someone else with access to the same credential.
  */
 export function useVendorsListVendorCredentialHistoryInfiniteSuspense(
   request: operations.ListVendorCredentialHistoryRequest,

package/src/sdk/events.ts

@@ -210,15 +210,16 @@ export class Events extends ClientSDK {
    * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission:
    * the caller's role and their relationship to the record decide what the endpoint returns.
    *
-   * Returns `Invite` items with the `invite.event` and `invite.invitee` scopes already applied,
-   * so `event` is the expanded `{ id, name }` summary instead of a bare id, and `invitee` is
-   * populated—the appointment and the recipient this list has always named. This endpoint
-   * takes no `expand` parameter; the endpoint always applies both scopes.
-   * SDK builds earlier than `0.55.0-beta.1` receive the older `PendingInvitation` shape instead, which
+   * Returns `Invite` items with the `invite.event`, `invite.invitee`, `event.location` and
+   * `event.creator` scopes already applied. So `event` is the expanded summary instead of a bare
+   * id, with the appointment's dates, flags, notes, location and organizer, and `invitee` is
+   * populated with the recipient's name and thumbnail—what this list has always published. This
+   * endpoint takes no `expand` parameter; the endpoint always applies these scopes.
+   * SDK builds earlier than `0.46.0-beta.1` receive the older `PendingInvitation` shape instead, which
    * embeds the appointment.
    *
-   * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
-   * `0.55.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
+   * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+   * `0.46.0-beta.1` itself already receives `Invite`. See the `Invite` schema for exactly how a
    * build compares against it.
    */
   async listPendingInvitations(
@@ -243,15 +244,16 @@ export class Events extends ClientSDK {
    * **Permissions.** Requires a valid token. This endpoint is not gated on a named permission.
    * The caller's role and their relationship to the record decide what the response includes.
    *
-   * Returns `Event` items with the `event.creator` and `event.invitees` scopes already applied,
-   * so the server populates `event_creator`, `event_creator_img_url` and `invitees`—the fields this
-   * feed has always carried. SDK builds below `0.55.0-beta.1` receive the older `Feed` shape
-   * instead, in which `facility` and `department` are name strings, not ids; the server
-   * chooses by the `X-SDK-User-Agent` header the SDK sends, so an existing client keeps the
-   * shape it was generated against until you regenerate it.
+   * Returns `Event` items with the `event.creator`, `event.invitees`, `event.facility` and
+   * `event.department` scopes already applied, so the server populates `event_creator`,
+   * `event_creator_img_url` and `invitees`, and `facility` and `department` are `{ id, name }`
+   * summaries—the fields this feed has always carried. SDK builds below `0.46.0-beta.1`
+   * receive the older `Feed` shape instead, in which `facility` and `department` are name
+   * strings, not ids; the server chooses by the `X-SDK-User-Agent` header the SDK sends, so an
+   * existing client keeps the shape it was generated against until you regenerate it.
    *
-   * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
-   * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
+   * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+   * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how the server compares a
    * build against it.
    */
   async listFeed(
@@ -275,13 +277,14 @@ export class Events extends ClientSDK {
    * the caller's role and their relationship to the record decide what the endpoint returns.
    *
    * Returns `Event` items with the `event.location`, `event.attendees`, `event.viewer_invite`,
-   * `event.creator` and `event.invitees` scopes already applied, so `location`, `attendees`,
-   * `event_creator`, `event_creator_img_url` and `invitees` are populated and `status` carries
-   * the reader's own outstanding invite. SDK builds earlier than `0.55.0-beta.1` receive the older
+   * `event.creator`, `event.invitees`, `event.facility` and `event.department` scopes already
+   * applied, so `location`, `attendees`, `event_creator`, `event_creator_img_url` and `invitees`
+   * are populated, `facility` and `department` are `{ id, name }` summaries, and `status` carries
+   * the reader's own outstanding invite. SDK builds earlier than `0.46.0-beta.1` receive the older
    * `StandingAppointment` shape instead.
    *
-   * The boundary is the prerelease build `0.55.0-beta.1`, not the `0.55.0` release, so
-   * `0.55.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
+   * The boundary is the prerelease build `0.46.0-beta.1`, not the `0.46.0` release, so
+   * `0.46.0-beta.1` itself already receives `Event`. See the `Event` schema for exactly how a
    * build compares against it.
    */
   async listStandingAppointments(

package/src/sdk/vendors.ts

@@ -296,6 +296,10 @@ export class Vendors extends ClientSDK {
    * is expanded, a company manager viewing a vendor-owned credential (not a company-owned one) only
    * receives the files they personally uploaded on the vendor's behalf.
    *
+   * For that same restricted company manager, `json_data` is returned as `null` unless they are the
+   * one who first submitted this version of the credential - everything else in the response
+   * (status, dates, notes, credential/invoice/etc.) is unaffected.
+   *
    * The following `expand` scopes are available:
    *
    * - `vendor_credential.credential`
@@ -637,6 +641,10 @@ export class Vendors extends ClientSDK {
    * Lists vendor credentials history
    *
    * **Permissions.** Requires the `vendor_credentials.view` permission.
+   *
+   * Each item's `submitted_by_current_user` says whether the calling user is the one who first
+   * submitted that version, so a vendor or company manager can tell their own submissions apart
+   * from ones made by someone else with access to the same credential.
    */
   async listVendorCredentialHistory(
     request: operations.ListVendorCredentialHistoryRequest,