From 75c52e75e7199230465edbe8c569cd4b915c6e78 Mon Sep 17 00:00:00 2001 From: Omkar Shanbhag Date: Wed, 16 Jul 2025 17:14:28 -0400 Subject: [PATCH] update tx auto quickstart --- .../signing-automation-quickstart.mdx | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/getting-started/signing-automation-quickstart.mdx b/getting-started/signing-automation-quickstart.mdx index 934de841..ef214ee0 100644 --- a/getting-started/signing-automation-quickstart.mdx +++ b/getting-started/signing-automation-quickstart.mdx @@ -37,6 +37,12 @@ Create a new key named `quickstart` using the turnkey CLI: turnkey generate api-key --organization $ORGANIZATION_ID --key-name quickstart ``` +Create a new encryption key using the turnkey CLI: + +```bash +turnkey generate encryption-key --organization $ORGANIZATION_ID --user $USER_ID +``` + You'll see output like this: ```json @@ -59,7 +65,7 @@ turnkey wallets create --name default --key-name quickstart ``` - This command requires a key named `quickstart` to exist in your configuration. This key should have been created during the [Quickstart](/getting-started/quickstart) guide. If you haven't created it yet, please complete the initial setup steps first. + This command requires a key named `quickstart` to exist in your configuration. This key should have been created during the [Quickstart](/getting-started/quickstart) guide. It also requires you to create an encryption key named "default" which you'd find in the encryption-keys directory of your turnkey config. If you haven't created those yet, please complete the initial setup steps first. If the key doesn't exist, you'll see an error like this: @@ -77,6 +83,14 @@ If the key exists but has not been added to your organization, you'll see an err } ``` +If the encryption key doesn't exist, you'll see an error like this: + +```json +{ + "error": "failed to associate the API key with an organization; please manually specify the organization ID" +} +``` +