From 2eb9708f7fcdead5e21ad22bd8a054e1ae4bfd31 Mon Sep 17 00:00:00 2001
From: aqtusia <47819902+aqtusia@users.noreply.github.com>
Date: Sun, 14 Apr 2019 18:21:59 +0200
Subject: [PATCH] Replace /unbind with /3pid/unbind

---
 proposals/1915-unbind-identity-server-param.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/proposals/1915-unbind-identity-server-param.md b/proposals/1915-unbind-identity-server-param.md
index 053552f6f..6817ece3d 100644
--- a/proposals/1915-unbind-identity-server-param.md
+++ b/proposals/1915-unbind-identity-server-param.md
@@ -55,12 +55,12 @@ from the given identity server.
 
 ### Identity Server 3PID Unbind API
 
-Add `POST /_matrix/identity/api/v1/unbind` with `mxid` and `threepid` fields.
+Add `POST /_matrix/identity/api/v1/3pid/unbind` with `mxid` and `threepid` fields.
 The `mxid` is the user's `user_id` and `threepid` is a dict with the usual
 `medium` and `address` fields.
 
 If the server returns a 400, 404 or 501 HTTP error code then the homeserver
-should assume that the identity server doesn't support the `/unbind` API, unless
+should assume that the identity server doesn't support the `/3pid/unbind` API, unless
 it returns a specific matrix error response (i.e. the body is a JSON object with
 `error` and `errcode` fields).
 
@@ -73,7 +73,7 @@ The identity server should authenticate the request in one of two ways:
 Example:
 
 ```
-POST /_matrix/identity/api/v1/unbind HTTP/1.1
+POST /_matrix/identity/api/v1/3pid/unbind HTTP/1.1
 
 {
     "mxid": "@foobar:example.com",