Logs

Know what happened to every email

Search your deliveries by status, recipient, subject and date, read any email by its id, and watch bounces as they come in, all through one endpoint.

  • JSON commands
  • 50 per page
  • Filter and search
  • Last 60 days
  • Read-only
POSThttps://g.sendcorex.com/v1/logslogs:read

How it works

One log per email

Every email you send gets a log with its recipient, subject, status and the answer of the recipient server. The id is the same one you got back when you sent.

One endpoint, two commands

list_logs searches and pages through your logs; get_logs reads them by id. Both go to POST /v1/logs, up to 20 commands per request.

Made for polling

Ask for new bounces every few seconds without worrying about load: repeated reads share one result, and warm-up emails are never in the way.

Get started

Only the key is needed before your first request.

  1. 1

    Create an API key with logs:read

    In the dashboard, open Developers → API Keys and create a key with the logs:read scope. You can add it to a key you already use for sending.

    The webmail token does not work here. Logs use the dashboard API key.

  2. 2

    Search your logs

    List Logs takes any mix of status, recipient, subject words, domain, sender and dates, and returns 50 logs per page.

  3. 3

    Read one email

    Get Logs reads up to 50 logs by id. Add include_content to see the HTML that was delivered.

The log

Both commands return logs in this shape.

{
  "id": "3f2a1b4c-8e9d-4f7a-b2c3-1a2b3c4d5e6f",
  "to": "ana@acme.com",
  "from": "noreply@yourdomain.com",
  "domain": "acme.com",
  "from_domain": "yourdomain.com",
  "subject": "Your order #1042 has shipped",
  "status": "delivered",
  "status_code": 2,
  "response": "250 2.0.0 OK 1760684401 a1si123456",
  "message": null,
  "blocked": false,
  "block_reason": null,
  "retries": 0,
  "tracking_id": "7CK-JDL-Y1L-20261017",
  "sent_at": "2026-10-17T06:00:01.204Z",
  "updated_at": "2026-10-17T06:00:02.913Z"
}
status

delivered, bounced, spam or rate_limited. Filter by one or several.

response

The exact answer of the recipient server. For a bounce, it says why.

blocked

true when Sendcorex did not send to this address, for example because it is suppressed.

content

Not part of the log by default. Get Logs returns the HTML with include_content.

Your first request

Two searches in one request: your bounces this month, and the last emails to one customer. Replace SENDCOREX_API_KEY with your API key.

curl -X POST 'https://g.sendcorex.com/v1/logs' \
  -H "Authorization: $SENDCOREX_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "commands": [
    { "command": "list_logs", "args": { "status": "bounced", "after": "2026-10-01" } },
    { "command": "list_logs", "args": { "recipient": "ana@acme.com", "limit": 10 } }
  ]
}'

You get one result per command, each with its logs and a next_cursor for the next page. The same request in 8 languages is in List Logs.

Common tasks

Clean bounces from your list

Poll bounced logs every few seconds with after set to the last one you saw, and remove those addresses on your side.

Watching for new bounces

Answer "did my email arrive?"

Look up a customer by recipient and show the status and the server response of their last emails.

List Logs

Check one send

Keep the id you get back when you send, and read its log later with Get Logs.

Get Logs

See what was delivered

Get Logs with include_content returns the HTML, for support screens or audits.

Reading the body

Full reference

Everything marked CMD is a command sent through POST /v1/logs, up to 20 per request.