Skip to content
Qualia Docs

Episodes_TakeOverEpisodeLease

POST
/v1/accounts/{account}/datasets/{dataset}/episodes/{episode}:takeOverEpisodeLease
 
curl --request POST \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/episodes/example:takeOverEpisodeLease \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <X-API-Key>' \
  --data '{ "episode": "example", "tab": "example" }'

Replaces another person’s live lease with the caller’s, for this tab, and records EPISODE_LEASE_TAKEN (not undoable). Admins and owners only. With no live lease of another person it acquires, and records nothing. (— api-linter: core::0136::prepositions=disabled aip.dev/not-precedent: “take over” is one verb, the one the studio shows. —)

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.

episode
required
string

The episode id.

Request Body required

Section titled “Request Body required ”
Media type application/json

Request for Episodes.TakeOverEpisodeLease.

object
episode
required

Accounts/{account}/datasets/{dataset}/episodes/{episode}

string
tab
required

The caller’s tab.

string
Example generated
{
  "episode": "example",
  "tab": "example"
}

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

Response for Episodes.TakeOverEpisodeLease.

object
lease

The caller’s lease.

object
holder

The holder’s user id (as Actor.user).

string
holderName

The holder’s display name at the time they took it; empty when they have none. (— api-linter: core::0122::name-suffix=disabled aip.dev/not-precedent: a person’s display name, not a resource name; events-api’s lease frames call it this. —)

string
expireTime

When it lapses unless renewed.

string format: date-time
Example generated
{
  "lease": {}
}

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"
    }
  ]
}