diff --git a/CMakeLists.txt b/CMakeLists.txt
index 71135af..8ededfd 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -58,12 +58,6 @@ else()
 set(CONSERVATIVE_DISK_SAVE_VAL true)
 endif()
 
-if(API_VERSION)
-set(API_VERSION_VAL ${API_VERSION})
-else()
-set(API_VERSION_VAL 1)
-endif()
-
 if(MULTI_THREADED)
 set(MULTI_THREADED_VAL ${MULTI_THREADED})
 else()
diff --git a/ccash_config.hpp.in b/ccash_config.hpp.in
index bc0c94b..e875840 100644
--- a/ccash_config.hpp.in
+++ b/ccash_config.hpp.in
@@ -36,6 +36,6 @@ version 2 will work
 version 3 will work
 etc
 */
-#define API_VERSION @API_VERSION_VAL@
+#define API_VERSION 1
 
 #define MULTI_THREADED @MULTI_THREADED_VAL@
\ No newline at end of file
diff --git a/docs/building.md b/docs/building.md
index 324c007..7922403 100644
--- a/docs/building.md
+++ b/docs/building.md
@@ -27,16 +27,15 @@ cd build
 
 ### CMake Flags
 there are multiple flags responsible configuring CCash:
-| name                   |      default       | description                                                                                                                                             | pros                                 | cons                                                          |
-| :--------------------- | :----------------: | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ------------------------------------------------------------- |
-| USER_SAVE_LOC          |  "../users.json"   | where the users are saved                                                                                                                               | `N/A`                                | `N/A`                                                         |
-| DROGON_CONFIG_LOC      |  "../config.json"  | where the config is located                                                                                                                             | `N/A`                                | `N/A`                                                         |
-| MAX_LOG_SIZE           |        100         | max number of logs per user, last `n` transactions. If both this and pre log are toggled to 0 logs will not be compiled.                                | large history                        | higher memory usage                                           |
-| PRE_LOG_SIZE           |         10         | the amount of transactions allocated in advance                                                                                                         | faster to not alloc each transaction | higher memory usage                                           |
-| CONSERVATIVE_DISK_SAVE |       `true`       | when `true` only saves when changes are made                                                                                                            | low # of disk operations             | some atomic overhead                                          |
-| API_VERSION            | ${CURRENT_VERSION} | indicates which API version is being used, often backwards compatible                                                                                   | `N/A`                                | `N/A`                                                         |
-| MULTI_THREADED         |       `true`       | when `true` the program is compiled to utilize `n` threads which corresponds to how many Cores your CPU has, plus 1 for saving                          | speed                                | memory lock overhead may be in vain on a single core machines |
-| RETURN_ON_DEL_NAME     |       `N/A`        | when defined, return on delete will be toggled and any accounts deleted will send their funds to the defined account, this prevent currency destruction | prevents destruction of currency     | deleting accounts is made slower                              |
+| name                   |     default      | description                                                                                                                                             | pros                                 | cons                                                        |
+| :--------------------- | :--------------: | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | ----------------------------------------------------------- |
+| USER_SAVE_LOC          | "../users.json"  | where the users are saved                                                                                                                               | `N/A`                                | `N/A`                                                       |
+| DROGON_CONFIG_LOC      | "../config.json" | where the config is located                                                                                                                             | `N/A`                                | `N/A`                                                       |
+| MAX_LOG_SIZE           |       100        | max number of logs per user, last `n` transactions. If both this and pre log are toggled to 0 logs will not be compiled.                                | large history                        | higher memory usage                                         |
+| PRE_LOG_SIZE           |        10        | the amount of transactions allocated in advance                                                                                                         | faster to not alloc each transaction | higher memory usage                                         |
+| CONSERVATIVE_DISK_SAVE |      `true`      | when `true` only saves when changes are made                                                                                                            | low # of disk operations             | some atomic overhead                                        |
+| MULTI_THREADED         |      `true`      | when `true` the program is compiled to utilize `n` threads which corresponds to how many Cores your CPU has, plus 1 for saving                          | speed                                | memory lock overhead may be in vain on single core machines |
+| RETURN_ON_DEL_NAME     |      `N/A`       | when defined, return on delete will be toggled and any accounts deleted will send their funds to the defined account, this prevent currency destruction | prevents destruction of currency     | deleting accounts is made slower                            |
 
 simply running 
 ```