Emote generation

In order to create an emote the following flow must happen:

First, a user must have been created, follow the user creation guide if it's not already done.

You will have to create a generation token with the following route.

Generate token with metadata

post

Get a token to authenticate a process creation with the ability to include metadata

Authorizations

Query parameters

userIdanyOptional

Virtual world's user ID.

Body

application/jsondescriptionx-gitbook-description-html

someKeystringOptionalExample: someValue

Responses

post

HTTPcURLJavaScriptPython

POST /v1/process/token HTTP/1.1
Host: sdk-api.dev.kinetix.tech
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 23

{
  "someKey": "someValue"
}

application/jsondescriptionx-gitbook-description-html

{
  "uuid": "text",
  "url": "text",
  "expire": "2025-04-25T08:54:23.274Z"
}

You can generate a QR code with the 'url' field in order to redirect to the PWA. The PWA will use the token and run the process on it's own. The token can only be used once, and has a 5 minutes TTL in order to prevent abuses. You have the ability to provide arbitrary metadata that will be attached to the process and then the emote. This could be used for example to implement customizable emotes with GTA's animation flags. As the server owner, you are responsible for the token generation. Generation processes will cost money and you have to design your system in a way that ensure you can generate revenue.

You can list the processes of a user with the following route :

List user processes

get

List all the ongoing user processes. The user must be associated to requesting virtual world

Authorizations

Path parameters

userIdanyRequired

Virtual world's user ID.

Query parameters

pendingstring · enumOptional

Filter by status pending

Possible values:

processingstring · enumOptional

Filter by status processing

Possible values:

donestring · enumOptional

Filter by status done

Possible values:

failedstring · enumOptional

Filter by status failed

Possible values:

validatedstring · enumOptional

Filter by status validated

Possible values:

rejectedstring · enumOptional

Filter by status rejected

Possible values:

sinceanyOptional

Filter by creation date

Example: 2023-01-01T12:12:30Z

Responses

get

HTTPcURLJavaScriptPython

GET /v2/users/{userId}/processes HTTP/1.1
Host: sdk-api.dev.kinetix.tech
x-api-key: YOUR_API_KEY
Accept: */*

[
  {
    "uuid": "00000000-0000-0000-0000-000000000000",
    "emote": "00000001-0001-0001-0001-000000000001",
    "animation": "00000002-0002-0002-0002-000000000002",
    "video": "00000003-0003-0003-0003-000000000003",
    "vw": 123,
    "user": 12345,
    "progression": 100,
    "createdAt": "2023-01-01T12:12:30Z",
    "name": "foo",
    "validated": false,
    "rejected": true,
    "hierarchy": {
      "children": 2,
      "child": {
        "uuid": "uuid1",
        "child": {
          "uuid": "uuid2",
          "child": null
        }
      },
      "parents": 0,
      "parent": null
    }
  }
]

The emote creation process will evolve through these different states :

Process statuses

• Pending: When the process is queued to be processed by our GPU cluster

• Processing: When the ML algorithm is running on the video

• Done: When the inference was successful

• Failed:

  • An unknown error happens when the algorithm failed due to an unhandled error

  • A known error code will be returned if the video input is not processable

    • Too many people

    • No human detected on screen

    • The detected actor is too small

• Validated & Rejected: Optional user validation step that is detailed here.

When the YCD File generation setting is enabled, an extra status called 'gta_done' will be present in the webhook.

You are also able to filter the processes by their creation date, allowing you for example to only display the processes recently created.

In order to fetch the content of a successful process, you need to call the emote route with the 'emote' uuid of the process object:

Get Kinetix emote

get

Get the inform

Authorizations

Path parameters

uuidanyOptional

Emote uuid

Responses

get

HTTPcURLJavaScriptPython

GET /v1/emotes/{uuid} HTTP/1.1
Host: sdk-api.dev.kinetix.tech
x-api-key: YOUR_API_KEY
Accept: */*

{
  "id": 1,
  "uuid": "123e4567-e89b-12d3-a456-426614174000",
  "name": "text",
  "type": "text",
  "files": [
    {
      "id": 1,
      "name": "123e4567-e89b-12d3-a456-426614174000",
      "extension": "text",
      "assetId": 1,
      "url": "text",
      "createdAt": "2025-04-25T08:54:23.274Z"
    }
  ],
  "createdAt": "2025-04-25T08:54:23.274Z"
}

With this route you are able to get the asset's metadata and all the associated files, including the YCD file through a signed download link.

In our FiveM implementation, we download the output file and let the Cfx Server handle the Client - Server streaming. This way, even if the API was down, you would still be able to play existing emotes in game.