GET /client/{clientID}. Same information, JSON instead of XML, with a handful of renamed fields and a few that moved elsewhere. Two behaviours change: the id must be the client’s current id, and the call no longer activates the client app.
V2 checks an app permission on every call — V1 checked none — and a call whose permission is missing answers 400 with errorCode 15, the same status as an invalid payload (see 4.4). Grant these to the API user before porting the command; the names are the ones of the permission tree in flowww.
An old id was translated to the surviving client, and its data returned.
404. The absorbed record no longer exists. Search the client again and store the new id — see 4.7.
ClientFWA=1
Was an action: it activated the client app (and created the token) if it was not active yet.
Gone from the GET, which only reads. To activate the app on an existing client, send ClientFWA: 1 in command 18; it generates ClientAppToken if the client had none, and this call reads it back.
Other failures
Result=0 with a code.
Any failure reading the client answers 404. Permissions and an invalid clinic answer 400, with the reason in errorCode.