diff --git a/Changelog b/Changelog
index d590475f8409fb948b53fa7b789e6bd78e42c665..b5d58cb2f143379adc91d7f86702b1a52b207c85 100644
--- a/Changelog
+++ b/Changelog
@@ -1,3 +1,8 @@
+git HEAD
+
+    * Travel::Routing::DE::EFA::Exception::Ambiguous: Add post_value accessor
+      which contains the ambiguous input value
+
 Travel::Routing::DE::VRR 2.08 - Wed Oct 08 2014
 
     * efa: Add -l / --list option
diff --git a/lib/Travel/Routing/DE/EFA/Exception.pod b/lib/Travel/Routing/DE/EFA/Exception.pod
index 5ec29916d862b0223306284d159c3873d90957c8..d01087a84bc2d705db7fb6a21fc7a7b2eaa106d3 100644
--- a/lib/Travel/Routing/DE/EFA/Exception.pod
+++ b/lib/Travel/Routing/DE/EFA/Exception.pod
@@ -45,8 +45,8 @@ We got no parsable data from the EFA service
 =head2 Travel::Routing::DE::EFA::Exception::Ambiguous
 
 Our request contained ambiguous data. B<post_key> contains the relevant POST
-key, B<possibilities> is a comma-separated string of possible key values (as
-reported by the EFA service).
+key and B<post_value> the corresponding input value.  B<possibilities> is a
+pipe-separated string of acceptable values reported by the EFA service.
 
 =head2 Travel::Routing::DE::EFA::Exception::NoConnections