| All Verbs | /apikeys/regenerate | ||
|---|---|---|---|
| All Verbs | /apikeys/regenerate/{Environment} |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Environment | path | string | No | |
| Meta | query | Dictionary<string, string> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Results | form | List<UserApiKey> | No | |
| Meta | form | Dictionary<string, string> | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Key | form | string | No | |
| KeyType | form | string | No | |
| ExpiryDate | form | DateTime? | No | |
| Meta | form | Dictionary<string, string> | 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 /apikeys/regenerate HTTP/1.1
Host: gemma.api.kerberos.energy
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
environment: String,
meta:
{
String: String
}
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
results:
[
{
key: String,
keyType: String,
expiryDate: 0001-01-01T00:00:00,
meta:
{
String: String
}
}
],
meta:
{
String: String
},
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}