diff --git a/src/pages/getting-started/endpoints.mdx b/src/pages/getting-started/endpoints.mdx
index 7628f64..1c11bf3 100644
--- a/src/pages/getting-started/endpoints.mdx
+++ b/src/pages/getting-started/endpoints.mdx
@@ -56,7 +56,8 @@ To provide information about the provider, we will create a `config.json` file w
 {
   "coreProvider": ...,
   "networkId": "preprod",
-  "logging": [{ "type": { "tag": "stderr" }, "severity": "Debug", "verbosity": "V2" }]
+  "logging": [{ "type": { "tag": "stderr" }, "severity": "Debug", "verbosity": "V2" }],
+  "logTiming": false
 }
 ```
 
@@ -88,6 +89,7 @@ Here is the explanation for each of the JSON keys above:
   * For Blockfrost, `blockfrostKey` holds the required api key.
 * **`networkId`**: Specifies your network and must be one of `mainnet`, `preprod`, `preview`, `testnet` (for legacy testnet) & `privnet` (for local private network).
 * **`logging`**: It's a list of [scribes](https://hackage.haskell.org/package/katip-0.8.7.3/docs/Katip.html#t:Scribe) to register. Its parameters (like `severity`, `verbosity`) and its general usage can be understood by going over their official haddock documentation [here](https://hackage.haskell.org/package/katip-0.8.7.2/docs/Katip.html). Katip is also explained in [this](https://link.springer.com/book/10.1007/978-1-4842-3739-7) book on web development in Haskell. Please have a look at haddock for `FromJSON` and `ToJSON` instances of [`GYLogScriptType`](https://haddock.atlas-app.io/GeniusYield-Types-Logging.html#t:GYLogScribeType) to see sample usage.
+* **`logTiming`**: (Optional) If set to `true`, operations involving provider are timed and corresponding durations are logged.
 
 ### Parsing Given Configuration