diff --git a/event_data/index.txt b/event_data/index.txt
index a577b3c..f80d3e5 100644
--- a/event_data/index.txt
+++ b/event_data/index.txt
@@ -12,6 +12,7 @@ Event Data
 <li>startParam</li>
 <li>endParam</li>
 <li>cacheParam</li>
+<li>lazyFetching</li>
 <li class='callback'><a href='loading'>loading</a> <em>(callback)</em></li>
 <li class='method'><a href='updateEvent'>updateEvent</a> <em>(method)</em></li>
 <li class='method'><a href='clientEvents'>clientEvents</a> <em>(method)</em></li>
diff --git a/event_data/lazyFetching.txt b/event_data/lazyFetching.txt
new file mode 100644
index 0000000..ad8f7df
--- /dev/null
+++ b/event_data/lazyFetching.txt
@@ -0,0 +1,18 @@
+
+lazyFetching *1.4.5*
+====================
+
+Determines when event fetching should occur.
+
+<div class='spec' markdown='1'>
+Boolean, *default*: `true`
+</div>
+
+When set to `true` (the default), the calendar will only fetch events when it absolutely
+needs to, minimizing AJAX calls. For example, say your calendar starts out in month view, in February.
+FullCalendar will fetch events for the entire month of February and store them in its internal cache.
+Then, say the user switches to week view and begins browsing the weeks in February.
+The calendar will avoid fetching events because it already has this information stored.
+
+When set to `false`, the calendar will fetch events any time the view is switched,
+or any time the current date changes (for example, as a result of the user clicking prev/next).