Skip to content
Qualia Docs

Mixtures_DeleteSource

DELETE
/v1/accounts/{account}/datasets/{dataset}/sources/{source}
 
curl --request DELETE \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/sources/example \
  --header 'X-API-Key: <X-API-Key>'

Removes a source. The mixture’s rejects on its episodes are kept, in case it comes back. Emits SOURCE_REMOVED.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
account
required
string

The account id.

dataset
required
string

The dataset id.

source
required
string

The source id.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

default

Section titled “default ”

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}