PUT /api/apps/versions/{AppVersionID}/oauthclient

Updates information about the OAuth Profile for a specific app version. Legacy operation. The newer operation is PUT /api/apps/versions/{AppVersionID}/oauthclient (same endpoint with different payload and content-type).

Workflow: This operation checks whether the resource is governed by a workflow, and if so whether the action is valid based on the current state of the resource. If the action is not valid, the operation will fail.

Authorization Roles/Permissions: Must be logged in. App team member, Business Admin

This topic includes the following sections:

HTTP Method


Back to top



Back to top

Sample Request

The example below shows an update request for the OAuth client properties.

Sample request URL


Sample request headers

PUT /api/apps/versions/9CA3Avaz8e96zMUKhaL4mM4s.acmepaymentscorp/oauthclient HTTP/1.1
Accept: */*
Content-Type: application/vnd.soa.v71+json

Sample request body

  "LegalDisclaimer":"Copyright 2016",

Back to top

Request Headers

For general information on request header values, refer to HTTP Request Headers.

Header Description
Accept Any Accept header value that supports a response Content-Type of text/plain is valid; for example, */*.
Content-Type application/json, application/vnd.soa.v71+json
AtmoAuthToken_{fedmemberid} The platform cookie. This is the Akana API Platform authorization token, and must be sent with every API request that requires login.
X-Csrf-Token_{fedmemberID} The CSRF prevention header; may or may not be required, depending on platform settings. See CSRF Prevention on the Platform. By default, the CSRF header is not required for GET operations and is required for all others, with a few exceptions relating to user login.

Back to top

Request Parameters

Parameter Parm Type Data Type Required Description
AppVersionID Path string Required The unique ID for a specific app version.
OAuthClient71 Body OAuthClient71 Required

Includes information about the OAuth Client settings for the specified app. This object is the payload for legacy operation PUT /api/apps/versions/{AppVersionID}/oauthclient. The newer operation is PUT /api/apps/versions/{AppVersionID}/oauthclient (same endpoint with different payload and content-type).

Only one RedirectURI value is supported.

Back to top


If successful, this operation returns HTTP status code 200, with a positive response.

Back to top

Sample Response

The sample response below shows that this operation completed successfully.

Sample response headers

HTTP/1.1 200 OK
Date: Thu, 14 Jan 2016 21:10:05 GMT
Content-Type: text/plain

Sample response body


Back to top

Response Headers

For general information on response header values, refer to HTTP Response Headers.

Header Description
Content-Type text/plain

Back to top

Response Body

Name Type Description
Response string A value indicating that the operation was successful.

Back to top

Error Codes/Messages

If the call is unsuccessful an error code/message is returned. One or more examples of possible errors for this operation are shown below.

Item Value
400 Bad request: Returned if the client sends a malformed request; for example, invalid parameters or body content.For example, you might get this response if you send an incorrect JSON object in the request, or specified the wrong media type in the Content-Type header.
401 Unauthorized. For example, you would get this response if you didn't include the custom X-Csrf-Token_{fedmemberID} header in the request, when it was required by the platform settings; or if you included an invalid or expired value for this header. You would also get this response for any operation that requires login (almost all) if the login cookie was missing.
500 An error occurred processing the call.

More information about Akana API Platform API error messages.

Back to top

Related Topics