Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Name | query | string | Yes | |
ApiKey | query | string | Yes | |
ApiKeyHeader | query | string | Yes | |
ApiBaseUrl | query | string | Yes | |
HeartbeatUrl | query | string | Yes | |
Concurrency | query | int | No | |
Priority | query | int | No | |
Enabled | query | bool | No | |
OfflineDate | query | DateTime? | No | |
Models | query | List<string> | Yes | |
GenerationApiTypeId | query | int? | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Id | form | string | No | |
ResponseStatus | form | ResponseStatus | 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 /jsv/reply/CreateGenerationApiProvider HTTP/1.1
Host: blazordiffusion.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
name: String,
apiKey: String,
apiKeyHeader: String,
apiBaseUrl: String,
heartbeatUrl: String,
concurrency: 0,
priority: 0,
enabled: False,
offlineDate: 0001-01-01,
models:
[
String
],
generationApiTypeId: 0
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { id: String, responseStatus: { errorCode: String, message: String, stackTrace: String, errors: [ { errorCode: String, fieldName: String, message: String, meta: { String: String } } ], meta: { String: String } } }