@seamapi/types 1.874.0 → 1.876.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -44782,6 +44782,133 @@ type Routes = {
44782
44782
  jsonResponse: {};
44783
44783
  maxDuration: undefined;
44784
44784
  };
44785
+ '/access_methods/assign_card': {
44786
+ route: '/access_methods/assign_card';
44787
+ method: 'POST';
44788
+ queryParams: {};
44789
+ jsonBody: {};
44790
+ commonParams: {
44791
+ /** ID of the card-mode `access_method` to assign the card to. */
44792
+ access_method_id: string;
44793
+ /** Card number of the card credential to assign. */
44794
+ card_number: string;
44795
+ };
44796
+ formData: {};
44797
+ jsonResponse: {
44798
+ /** Represents an access method for an Access Grant. Access methods describe the modes of access, such as PIN codes, plastic cards, and mobile keys. For a mobile key, the access method also stores the URL for the associated Instant Key. */
44799
+ access_method: {
44800
+ /** ID of the Seam workspace associated with the access method. */
44801
+ workspace_id: string;
44802
+ /** ID of the access method. */
44803
+ access_method_id: string;
44804
+ /** Display name of the access method. */
44805
+ display_name: string;
44806
+ /** Access method mode. Supported values: `code`, `card`, `mobile_key`, `cloud_key`. */
44807
+ mode: 'code' | 'card' | 'mobile_key' | 'cloud_key';
44808
+ /** Date and time at which the access method was created. */
44809
+ created_at: string;
44810
+ /** Date and time at which the access method was issued. */
44811
+ issued_at: string | null;
44812
+ /** Indicates whether the access method has been issued. */
44813
+ is_issued: boolean;
44814
+ /** URL of the Instant Key for mobile key access methods. */
44815
+ instant_key_url?: string | undefined;
44816
+ /** Token of the client session associated with the access method. */
44817
+ client_session_token?: string | undefined;
44818
+ /** Indicates whether encoding with an card encoder is required to issue or reissue the plastic card associated with the access method. */
44819
+ is_encoding_required?: boolean | undefined;
44820
+ /** Indicates whether the access method is ready to be encoded. This is true when the credential has been created and the card has not yet been issued. */
44821
+ is_ready_for_encoding?: boolean | undefined;
44822
+ /** The actual PIN code for code access methods. */
44823
+ code?: (string | null) | undefined;
44824
+ /** Warnings associated with the [access method](https://docs.seam.co/latest/capability-guides/access-grants/delivering-access-methods). */
44825
+ warnings: ({
44826
+ /** Date and time at which Seam created the warning. */
44827
+ created_at: string;
44828
+ /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
44829
+ message: string;
44830
+ /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
44831
+ warning_code: 'being_deleted';
44832
+ } | {
44833
+ /** Date and time at which Seam created the warning. */
44834
+ created_at: string;
44835
+ /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
44836
+ message: string;
44837
+ /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
44838
+ warning_code: 'updating_access_times';
44839
+ } | {
44840
+ /** Date and time at which Seam created the warning. */
44841
+ created_at: string;
44842
+ /** Detailed description of the warning. Provides insights into the issue and potentially how to rectify it. */
44843
+ message: string;
44844
+ /** Unique identifier of the type of warning. Enables quick recognition and categorization of the issue. */
44845
+ warning_code: 'pulled_backup_access_code';
44846
+ /** ID of the original access method from which this backup access method was split, if applicable. */
44847
+ original_access_method_id?: string | undefined;
44848
+ })[];
44849
+ /** Pending mutations for the [access method](https://docs.seam.co/latest/capability-guides/access-grants/delivering-access-methods). Indicates operations that are in progress. */
44850
+ pending_mutations: ({
44851
+ /** Date and time at which the mutation was created. */
44852
+ created_at: string;
44853
+ /** Detailed description of the mutation. */
44854
+ message: string;
44855
+ /** Mutation code to indicate that Seam is in the process of provisioning access for this access method on new devices. */
44856
+ mutation_code: 'provisioning_access';
44857
+ /** Previous device configuration. */
44858
+ from: {
44859
+ /** Previous device IDs where access was provisioned. */
44860
+ device_ids: string[];
44861
+ };
44862
+ /** New device configuration. */
44863
+ to: {
44864
+ /** New device IDs where access is being provisioned. */
44865
+ device_ids: string[];
44866
+ };
44867
+ } | {
44868
+ /** Date and time at which the mutation was created. */
44869
+ created_at: string;
44870
+ /** Detailed description of the mutation. */
44871
+ message: string;
44872
+ /** Mutation code to indicate that Seam is in the process of revoking access for this access method from devices. */
44873
+ mutation_code: 'revoking_access';
44874
+ /** Previous device configuration. */
44875
+ from: {
44876
+ /** Previous device IDs where access existed. */
44877
+ device_ids: string[];
44878
+ };
44879
+ /** New device configuration. */
44880
+ to: {
44881
+ /** New device IDs where access should remain. */
44882
+ device_ids: string[];
44883
+ };
44884
+ } | {
44885
+ /** Date and time at which the mutation was created. */
44886
+ created_at: string;
44887
+ /** Detailed description of the mutation. */
44888
+ message: string;
44889
+ /** Mutation code to indicate that Seam is in the process of updating the access times for this access method. */
44890
+ mutation_code: 'updating_access_times';
44891
+ /** Previous access time configuration. */
44892
+ from: {
44893
+ /** Previous start time for access. */
44894
+ starts_at: string | null;
44895
+ /** Previous end time for access. */
44896
+ ends_at: string | null;
44897
+ };
44898
+ /** New access time configuration. */
44899
+ to: {
44900
+ /** New start time for access. */
44901
+ starts_at: string | null;
44902
+ /** New end time for access. */
44903
+ ends_at: string | null;
44904
+ };
44905
+ })[];
44906
+ /** ID of the customization profile associated with the access method. */
44907
+ customization_profile_id?: string | undefined;
44908
+ };
44909
+ };
44910
+ maxDuration: undefined;
44911
+ };
44785
44912
  '/access_methods/delete': {
44786
44913
  route: '/access_methods/delete';
44787
44914
  method: 'DELETE' | 'POST';
package/dist/index.cjs CHANGED
@@ -37076,7 +37076,7 @@ var openapi = {
37076
37076
  paths: {
37077
37077
  "/access_codes/create": {
37078
37078
  post: {
37079
- description: "Creates a new [access code](https://docs.seam.co/latest/capability-guides/smart-locks/access-codes).",
37079
+ description: "Creates a new [access code](https://docs.seam.co/latest/low-level-apis/access-codes). For granting access, we recommend [Access Grants](https://docs.seam.co/latest/use-cases/granting-access) instead: they work across both standalone smart locks and access control systems and manage the underlying codes for you. Use this low-level endpoint only when you need direct control over a code on a single device, such as setting a custom PIN value.",
37080
37080
  operationId: "accessCodesCreatePost",
37081
37081
  requestBody: {
37082
37082
  content: {
@@ -39885,7 +39885,7 @@ var openapi = {
39885
39885
  },
39886
39886
  "/access_grants/create": {
39887
39887
  post: {
39888
- description: "Creates a new Access Grant.",
39888
+ description: "Creates a new [Access Grant](https://docs.seam.co/latest/use-cases/granting-access/access-grants). Access Grants are the default and recommended way to grant a user access to any physical space, irrespective of the locking hardware. They work with both standalone smart locks (using `device_ids`) and access control systems (using `acs_entrance_ids` or `space_ids`), and can issue PIN codes, key cards, and mobile keys through a single request.",
39889
39889
  operationId: "accessGrantsCreatePost",
39890
39890
  requestBody: {
39891
39891
  content: {
@@ -43774,6 +43774,66 @@ var openapi = {
43774
43774
  "x-title": "Update an Access Grant"
43775
43775
  }
43776
43776
  },
43777
+ "/access_methods/assign_card": {
43778
+ post: {
43779
+ description: "Assigns an existing card credential to a card-mode access method, identified by `card_number`.",
43780
+ operationId: "accessMethodsAssignCardPost",
43781
+ requestBody: {
43782
+ content: {
43783
+ "application/json": {
43784
+ schema: {
43785
+ properties: {
43786
+ access_method_id: {
43787
+ description: "ID of the card-mode `access_method` to assign the card to.",
43788
+ format: "uuid",
43789
+ type: "string"
43790
+ },
43791
+ card_number: {
43792
+ description: "Card number of the card credential to assign.",
43793
+ type: "string"
43794
+ }
43795
+ },
43796
+ required: ["access_method_id", "card_number"],
43797
+ type: "object"
43798
+ }
43799
+ }
43800
+ }
43801
+ },
43802
+ responses: {
43803
+ 200: {
43804
+ content: {
43805
+ "application/json": {
43806
+ schema: {
43807
+ properties: {
43808
+ access_method: {
43809
+ $ref: "#/components/schemas/access_method"
43810
+ },
43811
+ ok: { type: "boolean" }
43812
+ },
43813
+ required: ["access_method", "ok"],
43814
+ type: "object"
43815
+ }
43816
+ }
43817
+ },
43818
+ description: "OK"
43819
+ },
43820
+ 400: { description: "Bad Request" },
43821
+ 401: { description: "Unauthorized" }
43822
+ },
43823
+ security: [
43824
+ { pat_with_workspace: [] },
43825
+ { console_session_with_workspace: [] },
43826
+ { api_key: [] }
43827
+ ],
43828
+ summary: "/access_methods/assign_card",
43829
+ tags: [],
43830
+ "x-fern-sdk-group-name": ["access_methods"],
43831
+ "x-fern-sdk-method-name": "assign_card",
43832
+ "x-fern-sdk-return-value": "access_method",
43833
+ "x-response-key": "access_method",
43834
+ "x-title": "Assign a Card to an Access Method"
43835
+ }
43836
+ },
43777
43837
  "/access_methods/delete": {
43778
43838
  delete: {
43779
43839
  description: "Deletes an access method.",
@@ -47507,7 +47567,7 @@ var openapi = {
47507
47567
  },
47508
47568
  "/acs/credentials/create": {
47509
47569
  post: {
47510
- description: "Creates a new [credential](https://docs.seam.co/latest/capability-guides/access-systems/managing-credentials) for a specified [ACS user](https://docs.seam.co/latest/capability-guides/access-systems/user-management).",
47570
+ description: "Creates a new [credential](https://docs.seam.co/latest/low-level-apis/managing-credentials) for a specified [ACS user](https://docs.seam.co/latest/capability-guides/access-systems/user-management). For granting access, we recommend [Access Grants](https://docs.seam.co/latest/use-cases/granting-access) instead: they create and manage the underlying credentials for you, across access systems and standalone smart locks alike. Use this low-level endpoint only when you need direct control over an individual ACS credential.",
47511
47571
  operationId: "acsCredentialsCreatePost",
47512
47572
  requestBody: {
47513
47573
  content: {