diff --git a/ddclient.conf.in b/ddclient.conf.in
index 83a8b15..c4d5172 100644
--- a/ddclient.conf.in
+++ b/ddclient.conf.in
@@ -199,7 +199,7 @@ ssl=yes					# use ssl-support.  Works with
 ## Single host update
 # protocol=gandi
 # zone=example.com
-# password=my-gandi-access-token
+# password=my-gandi-api-key
 # ttl=10800 # optional
 # myhost.example.com
 
diff --git a/ddclient.in b/ddclient.in
index bbc0346..5c99bb5 100755
--- a/ddclient.in
+++ b/ddclient.in
@@ -7455,8 +7455,9 @@ Description of Gandi's LiveDNS API can be found at:
     https://api.gandi.net/docs/livedns/
 
 Available configuration variables:
-  * password: The Gandi access token. If you don’t have one yet, you can generate
-    your production access token from the Gandi Admin application. Required.
+  * password: The Gandi API key. If you don’t have one yet, you can generate
+    your production API key from the API Key Page (in the Security section).
+    Required.
   * zone: The DNS zone to be updated. Required.
   * ttl: The time-to-live value associated with the updated DNS record.
     Optional; uses Gandi's default (10800) if unset.
@@ -7465,13 +7466,13 @@ Example ${program}.conf file entries:
   ## Single host update.
   protocol=gandi
   zone=example.com
-  password=my-gandi-access-token
+  password=my-gandi-api-key
   host.example.com
 
   ## Multiple host update.
   protocol=gandi
   zone=example.com
-  password=my-gandi-access-token
+  password=my-gandi-api-key
   ttl=3600 # optional
   hosta.example.com,hostb.sub.example.com
 EoEXAMPLE
@@ -7495,7 +7496,7 @@ sub nic_gandi_update {
 
             my $headers;
             $headers  = "Content-Type: application/json\n";
-            $headers .= "Authorization: Bearer $config{$h}{'password'}\n";
+            $headers .= "Authorization: Apikey $config{$h}{'password'}\n";