| All Verbs | /SignHashWithData/{ClientKey} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ClientKey | path | string | No | |
| AuthorizationID | query | string | No | |
| UserSSN | query | string | No | |
| HashData | query | string | No | |
| Message | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Result | form | byte[] | No | |
| ServiceSuccessResult | form | bool | No | |
| ErrorMesage | form | string | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /SignHashWithData/{ClientKey} HTTP/1.1
Host: imzagerservices.eyyubiye.bel.tr
Accept: application/json
Content-Type: application/json
Content-Length: length
{"ClientKey":"String","AuthorizationID":"String","UserSSN":"String","HashData":"String","Message":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Result":"AA==","ServiceSuccessResult":false,"ErrorMesage":"String"}