{"_id":"591d3109830cc30f00ecc82c","parentDoc":null,"category":{"_id":"5605f2bba4574a0d00811365","__v":26,"pages":["5608e4d6c5cff70d007d00d5","5608e4e7c5cff70d007d00d8","5608e4fbc5cff70d007d00da","5608e5096d8c440d000c79f3","5608e5156d8c440d000c79f6","5608e52331beb60d001b6558","5608e8248aedf50d0004cf98","5608e87e8aedf50d0004cf9b","5609bf4f9f85a70d00908530","562822dd5cfea90d00ddc5d7","562831c40653060d00a2f750","563d2732260dde0d00c5eab1","5660d2bee163310d006b19c1","567bb35b93919f0d00c97b1c","567bba643241c20d00b730de","567bbc14b56bac0d0019d933","567bc0473241c20d00b730e5","568b6bd8fe6fcc0d006dc8f7","56a427125fb2530d00421b67","56a42a5194ec0a0d00b3a012","56a42aaa545bc50d000e3ada","56ddff97bea78e20003a778f","56de00ab26744429006648ba","56de12a33168720e00c11b02","56e37f388b32a10e00f79755","56e73362e622c90e00dc55b3"],"project":"55a6e72e8cc73e0d00096635","version":"55a6e72f8cc73e0d00096638","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-26T01:19:55.795Z","from_sync":false,"order":2,"slug":"installation-and-launch","title":"Installation and Launch"},"user":"55a6caa022cfa321008e01d6","__v":0,"project":"55a6e72e8cc73e0d00096635","version":{"_id":"55a6e72f8cc73e0d00096638","project":"55a6e72e8cc73e0d00096635","hasReference":false,"__v":29,"hasDoc":true,"createdAt":"2015-07-15T23:05:19.125Z","releaseDate":"2015-07-15T23:05:19.125Z","categories":["55a6e7308cc73e0d00096639","55b7ed07aea7c8190058badb","5604567c0c78b00d0039b191","5605e6f23a93940d002b3e4a","5605f2bba4574a0d00811365","5605f309a4574a0d00811366","5608e3b98aedf50d0004cf8f","5608e4318aedf50d0004cf90","5608e6b5a7cc2f0d00d9754d","5608e6d331beb60d001b6560","5608f879a7cc2f0d00d97580","560b097887b71d0d000d3bd9","560b13cbafa0990d00979545","560b5cbec341310d00de2a01","560b5cd0c341310d00de2a02","566a35b81e08750d00a0c49b","566a3e8503b4b20d00d02a4a","567889d307bf6a0d0083edc8","569c8b7c15bb390d00db6f9d","56b254dc65ddf50d0076ba8f","57a8ebc4cdeea20e001d2a63","57e48a4000c8680e00fae6e7","5808216773557d0f00a1e428","58105ad54a8aa50f00aa4cba","58105bf298aea40f00afa3ba","58105f548a4aed0f00d67536","581061b898aea40f00afa3be","584b3de7e5f3a42300df6ef7","596839a75965d400155bb750"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-05-18T05:28:41.895Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":13,"body":"To access an existing store token to authorize your Stencil theme, use one of the following procedures:\n\n* [Copying OAuth Tokens](#oauth) – Recommended\n* [Copying Legacy (Basic-Auth) Tokens](#legacy) – Workaround\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"body\": \"As of Stencil CLI version 1.10.0, the [`stencil init`](/docs/initializing-stencil) command defaults to OAuth authentication. We strongly encourage you to [generate new API accounts/tokens](/docs/creating-an-api-account#oauth) as OAuth, to ensure these accounts' compatibility with all current and planned BigCommerce features.\\n\\nBigCommerce plans to eventually deprecate [Basic Auth/Legacy API](https://support.bigcommerce.com/articles/Public/Legacy-API-Accounts) accounts/tokens. However, for Stencil themes that you have already initialized/authorized, the [`stencil start`](/docs/launching-stencil) command still supports your existing Legacy API accounts/tokens.\\n\\nAlso, this documentation includes workarounds for using Legacy API accounts/tokens, for stores whose workflow requires that non–store owners be able to create accounts.\",\n  \"title\": \"OAuth Encouraged; Basic Auth Pending Deprecation\"\n}\n[/block]\n## <a name=\"oauth\"></a> Copying OAuth Tokens – Recommended\n\nTo access an existing OAuth token to authorize your theme:\n\n1. Open the `.txt` file that the BigCommerce control panel generated when you [created the API account](/docs/creating-an-api-account).\n\n    (If you did not retain this file, you will need to generate a new token by repeating the [Creating an API Account](/docs/creating-an-api-account) procedure.)\n\n2. Note the `Client ID` and `Access Token` hashes in the file (or in the control-panel modal for your newly created token).\n\n    <img src=\"https://files.readme.io/78ad268-OAuth-Credentials-Modal.png\" alt=\"OAuth credentials (Client ID, Access Token)\" height=\"60%\" width=\"60%\" style=\"border:1px solid #D1D7E0\">\n\n3. If you are a merchant granting an outside theme developer access to your store, provide these two values to the developer. They will need them when [Authorizing and Initializing Stencil](/docs/initializing-stencil).\n\n4. If you are developing a theme against your own store, you will use the same two values in the same [Authorizing and Initializing Stencil](/docs/initializing-stencil) step, described on the following page.\n<br>\n[block:html]\n{\n  \"html\": \"<h2 id=\\\"legacy\\\"> Copying Legacy (Basic-Auth) Tokens &ndash; Workaround </h2>\\n\\nTo copy an existing Legacy API token to authorize your theme:\\n\\n<ol>\\n<li>Navigate to the control panel's <a href=\\\"https://support.bigcommerce.com/articles/Public/Legacy-API-Accounts\\\">Legacy API Accounts</a> page.<p></p>\\n  </li>\\n\\n<li>\\nIn the appropriate <span class=\\\"inline-code\\\">Username</span> row, select the gear icon at right.<p></p>\\n  </li>\\n\\n<li>From the resulting drop-down, select <span class=\\\"inline-code\\\">Edit</span>.<p></p>\\n</li>  \\n  \\n<li>\\n  In the resulting <span class=\\\"inline-code\\\">Edit Legacy API Account</span> page, select the token in the <span class=\\\"inline-code\\\">API Token</span> field and copy it to your clipboard. Then:<p></p>\\n</li>\\n\\n\\t<ul> <!-- inner list -->\\n\\t\\t<li>If you are a merchant granting an outside theme developer access to your store, provide the developer with the token you've copied. They will need it when <a href=\\\"/docs/initializing-stencil#legacy\\\">Authorizing and Initializing Stencil</a>.<p></p>\\n    </li>  \\n  \\n\\t\\t<li>If you are developing a theme against your own store, keep this token on your clipboard as you proceed to the same <a href=\\\"/docs/initializing-stencil#legacy\\\">Authorizing and Initializing Stencil</a> page.<p></p>\\n    </li>\\n\\t</ul> <!-- inner list -->\\n</ol> \"\n}\n[/block]","excerpt":"","slug":"copying-a-token-to-initialize-stencil","type":"basic","title":"Copying a Token to Initialize Stencil"}

Copying a Token to Initialize Stencil


To access an existing store token to authorize your Stencil theme, use one of the following procedures: * [Copying OAuth Tokens](#oauth) – Recommended * [Copying Legacy (Basic-Auth) Tokens](#legacy) – Workaround [block:callout] { "type": "warning", "body": "As of Stencil CLI version 1.10.0, the [`stencil init`](/docs/initializing-stencil) command defaults to OAuth authentication. We strongly encourage you to [generate new API accounts/tokens](/docs/creating-an-api-account#oauth) as OAuth, to ensure these accounts' compatibility with all current and planned BigCommerce features.\n\nBigCommerce plans to eventually deprecate [Basic Auth/Legacy API](https://support.bigcommerce.com/articles/Public/Legacy-API-Accounts) accounts/tokens. However, for Stencil themes that you have already initialized/authorized, the [`stencil start`](/docs/launching-stencil) command still supports your existing Legacy API accounts/tokens.\n\nAlso, this documentation includes workarounds for using Legacy API accounts/tokens, for stores whose workflow requires that non–store owners be able to create accounts.", "title": "OAuth Encouraged; Basic Auth Pending Deprecation" } [/block] ## <a name="oauth"></a> Copying OAuth Tokens – Recommended To access an existing OAuth token to authorize your theme: 1. Open the `.txt` file that the BigCommerce control panel generated when you [created the API account](/docs/creating-an-api-account). (If you did not retain this file, you will need to generate a new token by repeating the [Creating an API Account](/docs/creating-an-api-account) procedure.) 2. Note the `Client ID` and `Access Token` hashes in the file (or in the control-panel modal for your newly created token). <img src="https://files.readme.io/78ad268-OAuth-Credentials-Modal.png" alt="OAuth credentials (Client ID, Access Token)" height="60%" width="60%" style="border:1px solid #D1D7E0"> 3. If you are a merchant granting an outside theme developer access to your store, provide these two values to the developer. They will need them when [Authorizing and Initializing Stencil](/docs/initializing-stencil). 4. If you are developing a theme against your own store, you will use the same two values in the same [Authorizing and Initializing Stencil](/docs/initializing-stencil) step, described on the following page. <br> [block:html] { "html": "<h2 id=\"legacy\"> Copying Legacy (Basic-Auth) Tokens &ndash; Workaround </h2>\n\nTo copy an existing Legacy API token to authorize your theme:\n\n<ol>\n<li>Navigate to the control panel's <a href=\"https://support.bigcommerce.com/articles/Public/Legacy-API-Accounts\">Legacy API Accounts</a> page.<p></p>\n </li>\n\n<li>\nIn the appropriate <span class=\"inline-code\">Username</span> row, select the gear icon at right.<p></p>\n </li>\n\n<li>From the resulting drop-down, select <span class=\"inline-code\">Edit</span>.<p></p>\n</li> \n \n<li>\n In the resulting <span class=\"inline-code\">Edit Legacy API Account</span> page, select the token in the <span class=\"inline-code\">API Token</span> field and copy it to your clipboard. Then:<p></p>\n</li>\n\n\t<ul> <!-- inner list -->\n\t\t<li>If you are a merchant granting an outside theme developer access to your store, provide the developer with the token you've copied. They will need it when <a href=\"/docs/initializing-stencil#legacy\">Authorizing and Initializing Stencil</a>.<p></p>\n </li> \n \n\t\t<li>If you are developing a theme against your own store, keep this token on your clipboard as you proceed to the same <a href=\"/docs/initializing-stencil#legacy\">Authorizing and Initializing Stencil</a> page.<p></p>\n </li>\n\t</ul> <!-- inner list -->\n</ol> " } [/block]