Log candidate activity
Log a progression trigger on a candidate in a job, with an optional note.
POST https://cotlet.dev/api/v1/loxo/jobs/{job_id}/activities
write Confirm
Logs the trigger as the activity drop-down on the profile does. Loxo adds two events, "Moved to {stage}" and the trigger, so the candidate also changes stage. A trigger name your workflow does not have fails the call. A stage with an Email Automation can start sending its emails. By default you confirm each call; you can switch that off for this tool.
Parameters
| Name | Type | Description |
|---|---|---|
| job_id integer required | integer | Job id. |
| person_id integer required | integer | Person id. |
| activity string required | string | Progression trigger name from list_workflow_stages, for example 1st Interview. |
| note string | string | Text saved with the activity. |
Request
curl -X POST https://cotlet.dev/api/v1/loxo/jobs/2481530/activities \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"person_id":48211102,"activity":"1st Interview","note":"Good system design answers."}'result = client.call("loxo", "log_activity", {"job_id":2481530,"person_id":48211102,"activity":"1st Interview","note":"Good system design answers."})const result = await cotlet.call('loxo', 'log_activity', {"job_id":2481530,"person_id":48211102,"activity":"1st Interview","note":"Good system design answers."});cotlet call loxo log_activity --data '{"job_id":2481530,"person_id":48211102,"activity":"1st Interview","note":"Good system design answers."}'Example response
{
"job_id": 2481530,
"person_id": 48211077,
"stage": "Interviewing",
"events": [
"Moved to Interviewing",
"1st Interview"
],
"note": "Strong on Spark, wants a remote role."
}