Creates up to 500 extended cases per bulk operation.
The extended case is an object that includes a case and all its associated details, such as the runbook, notes, quick actions, and more.
This API call returns an operation ID which can be used with Retrieve bulk case creation state or List bulk case creation state to track the operation progress.
Bulk case creation is only available upon request - contact Torq Support for more information.
The request for creating extended cases in bulk.
The request for creating extended cases in bulk.
The cases to be created.
The request for creating an extended case.
The deduplication key to identify the case. If a case with the same deduplication key already exists, the operation will fail.
The case title.
The case description.
The name of the state. The default states are: new, in progress, on hold, resolved, closed. If your workspace has custom states, you can specify them by name.
The severity of the case. The possible values are: informational, low, medium, high, critical.
The email address of the case assignee.
The email of the actor. Only applicable when the actor is a user.
The case resolution SLA duration in seconds.
The case category.
The case tags.
The case custom fields.
The key of the custom field.
The ID of the case to which the custom field applies.
The value of the custom field.
The custom field type enum.
- TYPE_UNSPECIFIED: The custom field value type is unspecified.
- TYPE_SHORT_TEXT: The custom field value type is text.
- TYPE_NUMBER: The custom field value type is number.
- TYPE_BOOLEAN: The custom field value type is boolean.
- TYPE_TIMESTAMP: The custom field value type is timestamp.
- TYPE_LIST_SINGLE_SELECT: The custom field value type is list single select.
The constraints applied to the custom field value if the type is TYPE_SHORT_TEXT.
The minimum length of the custom field value.
The maximum length of the custom field value.
The regular expression that the custom field value must match.
The constraints applied to the custom field value if the type is TYPE_LIST_SINGLE_SELECT.
The list of acceptable values for the custom field.
The case quick actions.
The ID of the case the quick action belongs to.
The title of the quick action.
The ID of the workflow that will be executed when the quick action is selected.
The runbook associated with the case.
The case custom SLA timers.
The name of the custom SLA timer.
The ID of the case to which the custom SLA timer applies.
The duration, in seconds, from the timer start until expiration.
The state of the custom SLA timer.
- STATE_ID_NOT_RUNNING: The custom SLA timer isn't running.
- STATE_ID_RUNNING: The custom SLA timer is running.
Indicates whether the timer is a lead timer.
The case notes.
The unique identifier of the note.
The unique identifier of the case.
The note title.
The note content.
The email of the actor. Only applicable when the actor is a user.
The email of the actor. Only applicable when the actor is a user.
The reason the case was resolved or closed (up to 100 characters).
The detailed overview of the case resolution.
The timestamp when the case was created. If left empty, defaults to the current time during the bulk case creation operation.
The timestamp when the case was last updated. If left empty, defaults to the current time during the bulk case creation operation.
The timestamp when the case was resolved or closed. If left empty, defaults to the current time during the bulk case creation operation.
The email of the case reviewer.
A successful response.
The response returned when creating extended cases in bulk.
The operation ID to track the progress of the bulk creation.
The operation name.
The state of the bulk case creation operation.
- BULK_CREATE_STATE_UNSPECIFIED: Default value.
- BULK_CREATE_STATE_PENDING: The operation is currently running.
- BULK_CREATE_STATE_SUCCEEDED: The operation succeeded.
- BULK_CREATE_STATE_FAILED: The operation failed.
The response for the bulk case creation operation.
The IDs of the cases created.
The error response for the bulk case creation operation.
Invalid bearer token. If you receive this message more than once try creating a new Client ID/Client Secret or generating a new bearer token.
You don't have permission to access this resource.
An unexpected error response.
Any contains an arbitrary serialized protocol buffer message along with a
URL that describes the type of the serialized message.
Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type.
Example 1: Pack and unpack a message in C++.
Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo))
Example 2: Pack and unpack a message in Java.
Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class))
Example 3: Pack and unpack a message in Python.
foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ...
Example 4: Pack and unpack a message in Go
foo := &pb.Foo any, err := anypb.New(foo) if err != nil ... foo := &pb.Foo if err := any.UnmarshalTo(foo); err != nil
The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z".
JSON
The JSON representation of an Any value uses the regular
representation of the deserialized, embedded message, with an
additional field @type which contains the type URL. Example:
package google.profile; message Person
{
"@type": "type.googleapis.com/google.profile.Person",
"firstName":
If the embedded message type is well-known and has a custom JSON
representation, that representation will be embedded adding a field
value which holds the custom JSON in addition to the @type
field. Example (for message [google.protobuf.Duration][]):
{ "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" }
A URL/resource name that uniquely identifies the type of the serialized
protocol buffer message. This string must contain at least
one "/" character. The last segment of the URL's path must represent
the fully qualified name of the type (as in
path/google.protobuf.Duration). The name should be in a canonical form
(e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they
expect it to use in the context of Any. However, for URLs which use the
scheme http, https, or no scheme, one can optionally set up a type
server that maps type URLs to message definitions as follows:
- If no scheme is provided,
httpsis assumed. - An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
- Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be
used with implementation specific semantics.