Skip to main content
POST
/
api
/
ats
/
v1
/
activities
Create Activity
curl --request POST \
  --url https://api.bindbee.dev/api/ats/v1/activities \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'x-connector-token: <x-connector-token>' \
  --data '
{
  "user": "018b4bfb-5ece-70b1-ad5e-862a9433aa65",
  "activity_type": "NOTE",
  "body": "John Doe was interviewed for the position of Software Engineer.",
  "visibility": "PUBLIC",
  "candidate": "018b4bfb-5ece-70b1-ad5e-862a9433aa65",
  "subject": "Interview with John Doe"
}
'
{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Authorizations

​
Authorization
string
header
required

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

Headers

​
x-connector-token
string
required

Body

application/json
​
user
string<uuid> | null
required

The user who owns the activity.

Example:

"018b4bfb-5ece-70b1-ad5e-862a9433aa65"

​
activity_type
enum<string>
required

The type of activity. If the value is not one of the defined enum values, the original value passed through will be returned.

Available options:
NOTE,
EMAIL,
OTHER
Example:

"NOTE"

​
body
string | null
required

The body of the activity. This can include notes, comments, or other relevant information.

Example:

"John Doe was interviewed for the position of Software Engineer."

​
visibility
enum<string>
required

Visibility of the activity. If the value is not one of the defined enum values, the original value passed through will be returned.

Available options:
ADMIN_ONLY,
PUBLIC,
PRIVATE
Example:

"PUBLIC"

​
candidate
string<uuid> | null
required

Candidate who applied for the activity.

Example:

"018b4bfb-5ece-70b1-ad5e-862a9433aa65"

​
subject
string | null

The subject of the activity.

Example:

"Interview with John Doe"

Response

Successful Response