Enviar um conteúdo no projeto

Envia um conteúdo — texto, áudio ou arquivo — para um ou mais projetos. Cada projeto informado recebe uma entrada própria: quando mais de uma é criada, a resposta traz medias (lista) no lugar de media (objeto).

Áudio e arquivos são enviados como multipart/form-data. Menções escritas no texto disparam as notificações correspondentes — veja Menções. Projetos que já foram mesclados não aceitam novos conteúdos.

post/api/management/save-media

Request body

type1 | 2 | 3 required

Tipo do conteúdo: 1 texto, 2 arquivo, 3 áudio.

project_idsstring[]

Projetos que recebem o conteúdo.

textstring

Texto do conteúdo. Obrigatório no tipo 1. Até 50.000 caracteres.

{"stackTrail":"paths:/api/management/save-media:post:requestBody:content:application/json:schema:properties:audio","oasType":"schema","type":"unknown","description":"Arquivo de áudio. Obrigatório no tipo 3 (multipart/form-data)."}

channel_idstring uuid nullable

Canal pelo qual o conteúdo é enviado. Sem ele, o conteúdo fica interno.

channel_namestring nullable

Nome do canal, alternativa a channel_id. Os dois não podem vir juntos.

task_idstring uuid nullable

Tarefa que recebe o conteúdo, quando o envio é de uma tarefa.

Response

Conteúdo enviado a vários projetos

responseboolean required

Sempre true quando a operação é concluída.

Changes

Changed in 2 of the 79 revisions of this API.181017

Aug 24, 20263c590152d5b5181016See the full diff
- ▲
  the request property type changed from string to no type, and format from binary to no format
  request-property-type-changed
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property / became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the response property // became nullable for the status
  response-property-became-nullable
- ▲
  the / response's property format changed from uri to no format for status
  response-property-type-changed
- ●
  removed the request property
  request-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property / from the response with the status
  response-optional-property-removed
- ○
  added the new optional request property
  new-optional-request-property
- ○
  added the new optional request property
  new-optional-request-property
- ○
  added the new optional request property
  new-optional-request-property
- ○
  added the new optional request property
  new-optional-request-property
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  added the optional property // to the response with the status
  response-optional-property-added
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
- ○
  the response property became required for the status
  response-property-became-required
Aug 19, 20263d619d9db20d1See the full diff
- ○
  api tag Conteúdos e arquivos added
  api-tag-added

Full history