From d813b8e12c6e8839d9496c65861ab7ab070bc322 Mon Sep 17 00:00:00 2001
From: Travis Ralston <travpc@gmail.com>
Date: Tue, 10 Sep 2019 09:35:37 -0600
Subject: [PATCH] Mention M_INVALID_PARAM

---
 api/identity/v2_lookup.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/api/identity/v2_lookup.yaml b/api/identity/v2_lookup.yaml
index 561700f4..8acafd75 100644
--- a/api/identity/v2_lookup.yaml
+++ b/api/identity/v2_lookup.yaml
@@ -136,6 +136,9 @@ paths:
             presented with the ``M_INVALID_PEPPER`` error code. Clients SHOULD make
             a call to ``/hash_details`` to get a new pepper in this scenario, being
             careful to avoid retry loops.
+
+            ``M_INVALID_PARAM`` can also be returned to indicate the client supplied
+            an ``algorithm`` that is unknown to the server.
           examples:
             application/json: {
               "errcode": "M_INVALID_PEPPER",