Skip to main content
POST
/
reply
Create a new reply
curl --request POST \
  --url https://our-secret-api-url.com/reply \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --header 'X-API-KEY: <x-api-key>' \
  --form 'content=<string>' \
  --form 'hashtags=<string>' \
  --form type=REPLY \
  --form originalId=123 \
  --form parentId=123 \
  --form parentUserId=123 \
  --form media_1='@example-file' \
  --form media_2='@example-file' \
  --form media_3='@example-file' \
  --form media_4='@example-file'
{
  "id": 123,
  "snowflakeId": "<string>",
  "originalId": 123,
  "parentId": 123,
  "media": [
    {
      "id": 123,
      "updatedAt": "2023-11-07T05:31:56Z",
      "replyId": 123,
      "mediaUrl": "<string>",
      "mimeType": "<string>"
    }
  ]
}
The difference between POST /post and POST /reply is that a reply will be added to the Reply table.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

X-API-KEY
string
required

API key required for authentication

Body

multipart/form-data
content
string
required

Content of the reply

hashtags
string[]
required

List of hashtags

type
enum<string>
required

Type of the reply

Available options:
REPLY
originalId
integer
required

ID of the original post/reply

parentId
integer
required

ID of the parent post/reply

parentUserId
integer
required

ID of the parent user

media_1
file

First media file to be uploaded

media_2
file

Second media file to be uploaded

media_3
file

Third media file to be uploaded

media_4
file

Fourth media file to be uploaded

Response

Reply created successfully

id
integer
snowflakeId
string
originalId
integer | null
parentId
integer
media
object[] | null