@turnkey/http 2.22.0 → 3.1.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.
package/CHANGELOG.md CHANGED
@@ -1,16 +1,63 @@
1
1
  # @turnkey/http
2
2
 
3
+ ## 3.1.0
4
+
5
+ ### Minor Changes
6
+
7
+ - 3e4a482: Release per mono v2025.4.4
8
+ - Adds parsing and policy engine support for Ethereum Type 3 (EIP-4844) and Type 4 (EIP-7702) transactions. There is no change to any signing interface or API; you simply can now use Turnkey's signing endpoints to sign those transaction types. See [with-viem](https://github.com/tkhq/sdk/blob/main/examples/with-viem/) for examples.
9
+ - New wallet account creations will now automatically derive the underlying derived account's public key. For example: previously, if derived an Ethereum wallet account, you would get the resulting Ethereum address (`0x...`). If you also wanted the public key associated with that underlying key, you would've had to derive an additional wallet account with `ADDRESS_FORMAT_COMPRESSED`. Now, this will automatically be derived for you. It is now a property that has been added to the wallet account primitive (i.e. accessible via `walletAccount.publicKey`).
10
+
11
+ ## 3.0.0
12
+
13
+ ### Major Changes
14
+
15
+ - f94d36e: Remove deprecated TurnkeyApiService. TurnkeyApi should be used instead.
16
+
17
+ ### Minor Changes
18
+
19
+ - d1083bd: New activity `INIT_OTP_AUTH_V2` which allows alphanumeric boolean and otpLength (6-9) to be passed
20
+
21
+ - This release introduces the `INIT_OTP_AUTH_V2` activity. The difference between it and `INIT_OTP_AUTH` is that it can now accept `alphanumeric` and `otpLength` for selecting crockford bech32 alphanumeric codes and the length of those codes. By default alphanumeric = true, otpLength = 9
22
+
23
+ - This release introduces `sendFromEmailSenderName` to `INIT_OTP_AUTH`, `INIT_OTP_AUTH_V2`, `EMAIL_AUTH` and `EMAIL_AUTH_V2`. This is an optional custom sender name for use with sendFromEmailAddress; if left empty, will default to 'Notifications'.
24
+
3
25
  ## 2.22.0
4
26
 
5
27
  ### Minor Changes
6
28
 
7
- - ecdb29a: Update API as per mono v2025.3.2 - Add CREATE_USERS_V3
29
+ - ecdb29a: Update API as per mono v2025.3.2
30
+
31
+ - This release introduces the `CREATE_USERS_V3` activity. The difference between it and `CREATE_USERS_V2` is that it can now accept `userPhoneNumber` and `oauthProviders`. In total, it accepts the following parameters:
32
+
33
+ ```javascript
34
+ /** @description A list of Users. */
35
+ users: {
36
+ /** @description Human-readable name for a User. */
37
+ userName: string;
38
+ /** @description The user's email address. */
39
+ userEmail?: string;
40
+ /** @description The user's phone number in E.164 format e.g. +13214567890 */
41
+ userPhoneNumber?: string;
42
+ /** @description A list of API Key parameters. This field, if not needed, should be an empty array in your request body. */
43
+ apiKeys: definitions["v1ApiKeyParamsV2"][];
44
+ /** @description A list of Authenticator parameters. This field, if not needed, should be an empty array in your request body. */
45
+ authenticators: definitions["v1AuthenticatorParamsV2"][];
46
+ /** @description A list of Oauth providers. This field, if not needed, should be an empty array in your request body. */
47
+ oauthProviders: definitions["v1OauthProviderParams"][];
48
+ /** @description A list of User Tag IDs. This field, if not needed, should be an empty array in your request body. */
49
+ userTags: string[];
50
+ }
51
+ ```
52
+
53
+ See [source code](https://github.com/tkhq/sdk/blob/60c0c03440785b841d1f6f393612046423dc665f/packages/http/src/__generated__/services/coordinator/public/v1/public_api.types.ts#L2894-L2909) to view details on the nested types.
8
54
 
9
55
  ## 2.21.0
10
56
 
11
57
  ### Minor Changes
12
58
 
13
- - 56a307e: Update api to mono v2025.3.0
59
+ - 56a307e: Update API to mono v2025.3.0
60
+ - This release introduces an `invalidateExisting` flag to the `CreateReadWriteSession` and `Oauth` activities. If enabled, this will invalidate existing read-write and oauth API keys. This is useful in scenarios where a user attempts to create numerous `ReadWrite` or `Oauth` sessions. Because our API caps the number of session keys associated with a user, this flag can clear all other existing session keys of that specific type (e.g. setting `invalidateExisting: true` for `CreateReadWriteSession` will invalidate all previously created read-write session keys)
14
61
 
15
62
  ## 2.20.0
16
63
 
@@ -22,7 +69,17 @@
22
69
 
23
70
  ### Minor Changes
24
71
 
25
- - 57f9cb0: Update endpoints - surface GetWalletAccount
72
+ - 57f9cb0: Update endpoints - surface `GetWalletAccount`. This endpoint takes in the following args:
73
+ ```javascript
74
+ /** @description Unique identifier for a given Organization. */
75
+ organizationId: string;
76
+ /** @description Unique identifier for a given Wallet. */
77
+ walletId: string;
78
+ /** @description Address corresponding to a Wallet Account. */
79
+ address?: string;
80
+ /** @description Path corresponding to a Wallet Account. */
81
+ path?: string;
82
+ ```
26
83
 
27
84
  ## 2.18.0
28
85