ArgorantDocs

Answer replies

Every reply from every campaign in one inbox. Answer in the same thread, forward, and mark replies as interested, meeting booked or your own pipeline stage.

See the new replies

Shell
curl "https://app.argorant.com/api/v1/inbox?folder=replies&limit=25" -H "Authorization: Bearer $ARGORANT_API_KEY"

folder is all, replies, interested, not_interested, out_of_office, bounces or unsubscribes. Narrow further with campaign_id, classification or a search word in q. Lists show the first 400 characters of each reply. Page with cursor and next_cursor.

Read a conversation

Shell
curl "https://app.argorant.com/api/v1/inbox/$THREAD" -H "Authorization: Bearer $ARGORANT_API_KEY"

$THREAD is the id from the list. You get the full text and the whole thread, oldest first: your emails, their replies, your answers and forwards.

Answer in the same thread

Shell
curl -X POST "https://app.argorant.com/api/v1/inbox/$THREAD/reply" \
  -H "Authorization: Bearer $ARGORANT_API_KEY" -H "Idempotency-Key: reply-jane-1" \
  -H "Content-Type: application/json" \
  -d '{"body":"Thursday 10:00 works. I will send an invite."}'

The answer goes out at once, in the same thread, from the mailbox that got the reply. An agent should show the text to the user and wait for a yes. The Idempotency-Key makes sure a retry never sends it twice.

Forward it to a colleague

Shell
curl -X POST "https://app.argorant.com/api/v1/inbox/$THREAD/forward" \
  -H "Authorization: Bearer $ARGORANT_API_KEY" -H "Idempotency-Key: fwd-jane-1" \
  -H "Content-Type: application/json" \
  -d '{"to":["sales-lead@yourcompany.com"],"note":"Hot lead, please call her this week."}'

The forward carries the history and attachments. Within three minutes the conversation shows whether it was delivered.

Mark it and track your pipeline

Every workspace has five standard labels: positive (shown as Interested), meeting_request, out_of_office, unsubscribe and neutral (shown as Other). You can switch on not_interested, question, referral, wrong_person and meeting_booked. Add your own stages:

Shell
curl -X POST "https://app.argorant.com/api/v1/reply-statuses" \
  -H "Authorization: Bearer $ARGORANT_API_KEY" -H "Content-Type: application/json" \
  -d '{"label":"Proposal sent","color":"purple"}'

curl -X POST "https://app.argorant.com/api/v1/inbox/$THREAD/classify" \
  -H "Authorization: Bearer $ARGORANT_API_KEY" -H "Content-Type: application/json" \
  -d '{"classification":"proposal_sent"}'

interested is understood as positive. Rename, recolor, hide or show a stage with PATCH /api/v1/reply-statuses/{key}. Delete one of your own stages with DELETE /api/v1/reply-statuses/{key}; its conversations go back to neutral.

Get told right away

A webhook for reply.positive calls your server when someone is interested, so nobody waits for the next check.

From the terminal

Shell
npx argorant inbox list --folder replies
npx argorant inbox read <thread-id>
npx argorant inbox reply <thread-id> --body "Thursday works."
npx argorant inbox classify <thread-id> meeting_booked

On this page