POST | /users/apikeys/{Environment} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Environment | path | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Results | form | List<ErpUserApiKey> | No | |
ResponseStatus | form | ResponseStatus | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Key | form | string | No | |
KeyType | form | string | No | |
ExpiryDate | form | DateTime? | No | |
Environment | form | string | No | |
Notes | form | string | No | |
CreatedDate | form | DateTime | No | |
CancelledDate | form | DateTime? | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /users/apikeys/{Environment} HTTP/1.1
Host: apex.nikoratrade.ge
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
Environment: String
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { Results: [ { Key: String, KeyType: String, ExpiryDate: 0001-01-01, Environment: String, Notes: String, CreatedDate: 0001-01-01, CancelledDate: 0001-01-01 } ], ResponseStatus: { ErrorCode: String, Message: String, StackTrace: String, Errors: [ { ErrorCode: String, FieldName: String, Message: String, Meta: { String: String } } ], Meta: { String: String } } }