Public identity of an OAuth client, for the consent screen

GET/oauth/client/{clientId}

Path parameters

clientIdstringrequired

Query parameters

widget_originstring

Origin asking to receive this client's authorization code. Only the widget callback sends it; the consent screen omits it.

Responses

200Successful response

successbooleanrequired

Whether the request was successful

errorCodestringrequired

The error code returned by the request

Allowed:not_foundbad_requestalready_existsunauthorizedforbiddeninternal_server_errorservice_unavailabletimeoutconflictprecondition_failedunprocessable_entity

messagestringrequired

The message returned by the request

dataOAuthClientPublicObject

Show properties

clientIdstringrequired

namestringrequired

descriptionstring

logoUrlstring

Public URL of the client's uploaded logo, when it has one

widgetOriginAllowedboolean

Whether the origin passed as widget_origin may receive this client's authorization code. A verdict rather than the registered list, because entries may be wildcards and matching them is not something two separate builds should each implement.

Try it

Server

Base URLCustom base URLOverrides the selected server when set.

Parameters

clientIdpath*widget_originqueryOrigin asking to receive this client's authorization code. Only the widget callback sends it; the consent screen omits it.

Request

curl -X GET "https://api.insy.io/oauth/client/string"

const response = await fetch("https://api.insy.io/oauth/client/string", {
  method: "GET"
});

import requests

response = requests.get(
    "https://api.insy.io/oauth/client/string",
)

Response

{
  "success": true,
  "errorCode": "not_found",
  "message": "Success",
  "data": {
    "clientId": "string",
    "name": "string",
    "description": "string",
    "logoUrl": "string",
    "widgetOriginAllowed": true
  }
}