-Or you may also create it manually, as follows:
-
-```
-[api]
-key=BOT_API_KEY
-email=BOT_EMAIL_ADDRESS
-```
-
-Additionally, you can also specify the parameters as environment variables as follows:
-
-```
-export ZULIP_CONFIG=/path/to/zulipconfig
-export ZULIP_EMAIL=BOT_EMAIL_ADDRESS
-export ZULIP_API_KEY=BOT_API_KEY
-```
-
-The parameters specified in environment variables would override the parameters
-provided in the config file. For example, if you specify the variable `key`
-in the config file and specify `ZULIP_API_KEY` as an environment variable,
-the value of `ZULIP_API_KEY` would be considered.
-
-The following variables can be specified:
-
-1. `ZULIP_CONFIG`
-2. `ZULIP_API_KEY`
-3. `ZULIP_EMAIL`
-4. `ZULIP_SITE`
-5. `ZULIP_CERT`
-6. `ZULIP_CERT_KEY`
-7. `ZULIP_CERT_BUNDLE`
+Another alternative is manually creating your own `.zuliprc` file, or setting
+environment variables that are equivalent. You can find out more about these
+methods [here](/api/configuring-python-bindings).
diff --git a/templates/zerver/api/configuring-python-bindings.md b/templates/zerver/api/configuring-python-bindings.md
new file mode 100644
index 0000000000..c8161178ad
--- /dev/null
+++ b/templates/zerver/api/configuring-python-bindings.md
@@ -0,0 +1,104 @@
+# Configuring the Python bindings
+
+Zulip provides a set of tools that allows interacting with its API more
+easily, called the [Python bindings](https://pypi.python.org/pypi/zulip/).
+One of the most notable use cases for these bindings are bots developed
+using Zulip's [bot framework](/#writing-bots).
+
+In order to use them, you need to configure them with your API key and other
+settings. There are two ways to achieve that:
+
+ - With a file called `.zuliprc`, located in your home directory.
+ - With [environment variables](https://en.wikipedia.org/wiki/
+Environment_variable) set up in your host machine.
+
+A `.zuliprc` file is a plain text document that has the same format as
+Microsft Windows INI files. It looks like this:
+
+```
+[api]
+key=.zuliprc key |
+ Environment variable | +Required | +Description | +
|---|---|---|---|
key |
+ ZULIP_API_KEY |
+ Yes | ++ API key, which you can get through + Zulip's web interface. + | +
email |
+ ZULIP_EMAIL |
+ Yes | ++ The email address of the user who owns the API key mentioned + above. + | +
site |
+ ZULIP_SITE |
+ No | ++ URL where your Zulip server is located. + | +
client_cert_key |
+ ZULIP_CERT_KEY |
+ No | ++ Path to the SSL/TLS private key that the binding should use to + connect to the server. + | +
client_cert |
+ ZULIP_CERT |
+ No* | +
+ The public counterpart of client_cert_key/
+ ZULIP_CERT_KEY. This setting is required if a cert
+ key has been set.
+ |
+
client_bundle |
+ ZULIP_CERT_BUNDLE |
+ No | ++ Path where the server's PEM-encoded certificate is located. CA + certificates are also accepted, in case those CA's have issued the + server's certificate. Defaults to the built-in CA bundle trusted + by Python. + | +
insecure |
+ ZULIP_ALLOW_INSECURE |
+ No | +
+ Allows connecting to Zulip servers with an invalid SSL/TLS
+ certificate. Please note that enabling this will make the HTTPS
+ connection insecure. Defaults to false.
+ |
+