CCC API v8.4.0.0

CreateIdProvider

The following routes are available for this service:
POST	/api/idp	Create id provider configuration.

**CreateIdProvider** Parameters:
Name	Parameter	Data Type	Required
LoginUrl	body	String	No
TokenUrl	body	String	No
LogoutUrl	body	String	No
ClientId	body	String	No
SecretId	body	String	No
CertificateId	body	String	No
Certificate2Id	body	String	No
Name	body	String	No
Description	body	String	No
TypeGuid	body	Guid	No

**CreateIdProviderResponse** Parameters:
Name	Parameter	Data Type	Required	Description
IdProviderGuid	body	Guid	No

**BaseResponse** Parameters:
Name	Parameter	Data Type	Required	Description
ResponseStatus	form	ResponseStatus	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /api/idp HTTP/1.1 
Host: api.secure-messaging.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{
  "loginUrl": "String",
  "tokenUrl": "String",
  "logoutUrl": "String",
  "clientId": "String",
  "secretId": "String",
  "certificateId": "String",
  "certificate2Id": "String",
  "name": "String",
  "description": "String",
  "typeGuid": "00000000000000000000000000000000"
}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{
  "idProviderGuid": "00000000000000000000000000000000",
  "responseStatus": {
    "errorCode": "String",
    "message": "String",
    "stackTrace": "String",
    "errors": [
      {
        "errorCode": "String",
        "fieldName": "String",
        "message": "String",
        "meta": {
          "String": "String"
        }
      }
    ],
    "meta": {
      "String": "String"
    }
  }
}