From API key to first email in minutes.

Four steps to an agent that answers email.

1. 1

   Make an API key

   Create one under API keys after you sign up. Scope it to the whole organisation, a pod or a single inbox. You see the secret once.

   Scope it to the organisation, a pod or one inbox. You see the secret once.

   export ACK_API_KEY=ack_live_7h2k_…

2. 2

   Create an inbox

   The inbox ID is the email address. It can receive mail the moment the request returns.

   The inbox ID is the email address. It can receive mail straight away.

   curl https://api.ack.now/v0/inboxes \
     -H "Authorization: Bearer $ACK_API_KEY" \
     --json '{"username": "support-agent"}'
   
   # {"inbox_id": "support-agent@trial.ack.now", …}

   curl https://api.ack.now/v0/inboxes \
    -H "Authorization: Bearer $ACK…" \
    --json '{"username":"support-agent"}'

3. 3

   Hear about new mail

   Point a webhook at your app. URLs must be https and public. The response carries the signing secret.

   Point a webhook at your app. The response carries the signing secret.

   curl https://api.ack.now/v0/webhooks \
     -H "Authorization: Bearer $ACK_API_KEY" \
     --json '{"url": "https://app.northwind.co/hooks/ack",
             "event_types": ["message.received"]}'
   
   # {"webhook_id": "…", "secret": "whsec_…", …}

   POST /v0/webhooks
   {"url": "https://app…/hooks/ack",
    "event_types": ["message.received"]}

4. 4

   Reply in the thread

   ACK sets In-Reply-To and References, so the answer lands in the same conversation in the sender's mail app.

   ACK sets In-Reply-To and References, so the answer stays in the same conversation.

   curl https://api.ack.now/v0/inboxes/support-agent@trial.ack.now\
   /messages/$MESSAGE_ID/reply \
     -H "Authorization: Bearer $ACK_API_KEY" \
     --json '{"text": "Found the duplicate and refunded it."}'

   POST /v0/inboxes/{inbox_id}
        /messages/{message_id}/reply
   {"text": "Found the duplicate…"}