diff --git a/docs/api-reference.md b/docs/api-reference.md
index b8e4d344b..959c850d6 100644
--- a/docs/api-reference.md
+++ b/docs/api-reference.md
@@ -131,6 +131,40 @@ curl "localhost:10101/index/user/query?columnAttrs=true&shards=0,1" \
 
 By default, all bits and attributes (*for `Row` queries only*) are returned. In order to suppress returning bits, set `excludeBits` query argument to `true`; to suppress returning attributes, set `excludeAttrs` query argument to `true`.
 
+### Import Data
+
+`POST /index/<index-name>/field/<field-name>/import`
+
+Supports high-rate data ingest to a particular shard of a particular field. The
+official client libraries use this endpoint for their import functionality - it
+is not usually necessary to use this endpoint directly. See the documentation for
+imports for
+<a href="https://github.com/pilosa/go-pilosa/blob/master/docs/imports-exports.md">Go</a>,
+<a href="https://github.com/pilosa/java-pilosa/blob/master/docs/imports.md">Java</a>,
+and <a href="https://github.com/pilosa/python-pilosa/tree/master/docs/imports.md">Python</a>.
+
+The request payload is protobuf encoded with the following schema. The RowKeys
+and/or ColumnKeys fields are used if the pilosa field or index are configured
+for keys respectively. Otherwise, the RowIDs and ColumnIDs fields are used. They
+must have the same number of items, and each index into those two lists
+represents a particular bit to be set. Timestamps are optional, but if they
+exist must also contain the same number of items as rows and columns. The
+column IDs must all be in the shard specified in the request.
+
+```
+message ImportRequest {
+	string Index = 1;
+	string Field = 2;
+	uint64 Shard = 3;
+	repeated uint64 RowIDs = 4;
+	repeated uint64 ColumnIDs = 5;
+	repeated string RowKeys = 7;
+	repeated string ColumnKeys = 8;
+	repeated int64 Timestamps = 6;
+}
+```
+
+
 ### Create field
 
 `POST /index/<index-name>/field/<field-name>`
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 563176c62..257e77628 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -89,6 +89,11 @@ The `language` is a `set` field, but since the default field type is `set`, we d
 
 #### Import Data From CSV Files
 
+<div class="note">
+    <p>For demonstration purposes, we're using Pilosa's built in utility to import specially formatted CSV files. For more general usage, see how the various client libraries expose the bulk import functionality in <a href="https://github.com/pilosa/go-pilosa/blob/master/docs/imports-exports.md">Go</a>, <a href="https://github.com/pilosa/java-pilosa/blob/master/docs/imports.md">Java</a>, and <a href="https://github.com/pilosa/python-pilosa/tree/master/docs/imports.md">Python</a>. </p>
+</div>
+
+
 Download the `stargazer.csv` and `language.csv` files here:
 
 ```
diff --git a/docs/query-language.md b/docs/query-language.md
index 9bc231e6f..0f8feb795 100644
--- a/docs/query-language.md
+++ b/docs/query-language.md
@@ -67,6 +67,10 @@ Set(<COLUMN>, <FIELD>=<ROW>, [TIMESTAMP])
 
 `Set` assigns a value of 1 to a bit in the binary matrix, thus associating the given row (the `<ROW>` value) in the given field with the given column.
 
+<div class="note">
+    <p>While using "Set" in PQL is a convenient way to get familiar with Pilosa, it's almost always better to use the import functionality in the <a href="https://github.com/pilosa/go-pilosa/blob/master/docs/imports-exports.md">Go</a>, <a href="https://github.com/pilosa/java-pilosa/blob/master/docs/imports.md">Java</a>, and <a href="https://github.com/pilosa/python-pilosa/tree/master/docs/imports.md">Python</a> clients to ingest lots of data. </p>
+</div>
+
 **Result Type:** boolean
 
 A return value of `true` indicates that the bit was changed to 1.