Get results

The same scoreboard Revnu reads every time it wakes. Read-only: nothing this route returns can be changed through it.

curl -H "Authorization: Bearer $REVNU_API_TOKEN" "https://revnu.com/api/v1/results?since=1789000000000"

Query

Response

{
  "results": {
    "window": { "from": 1789000000000, "to": 1789604800000 },
    "baseline": { "from": 1788395200000, "to": 1789000000000 },
    "harness": { "available": true, "data": { } },
    "email": {
      "available": true,
      "data": {
        "sent": 120,
        "sentBaseline": 96,
        "draftsAwaiting": 4,
        "tracking": { "available": false, "reason": "tracking_off" },
        "replies": {
          "available": true,
          "data": {
            "replies": 7,
            "bounces": 2,
            "repliedContacts": [{ "who": "Jo Park", "company": "Northwind", "agoDays": 1, "intent": "interested" }]
          }
        }
      }
    },
    "outbound": { "available": true, "data": { "routes": [ ] } },
    "linkedin": {
      "available": true,
      "data": {
        "invites": 14,
        "health": { "needsReauth": false, "pausedUntil": null, "pauseReason": null, "inviteHeadroom": 6 },
        "replies": { "available": true, "data": { "count": 3 } }
      }
    },
    "seo": {
      "available": true,
      "data": { "postsPublished": 2, "postsHeld": 1, "postsFailed": 0, "views": 340 }
    },
    "aeo": { "available": true, "data": { } },
    "ads": { "available": false, "reason": "no_campaigns" }
  }
}

The numbers above are an example of the shape, not real figures, and some fields are left out to keep it short. The tables below list every field. baseline is the equal-length window just before window, for comparisons such as sent against sentBaseline.

Each channel section is { "available": true, "data": {…} }, optionally with caveats, or { "available": false, "reason": "…" }. Zero and unknown are different numbers.

Email

Reply rate is not a field: divide replies by sent. For everyone who replied, list GET /leads?status=replied.

LinkedIn

The LinkedIn section reads the workspace owner's connected LinkedIn account. Counts are for the window unless the table says otherwise.

Why LinkedIn pauses and when it resumes is in Why Did LinkedIn Sending Stop?. For one person's connection and conversation, use GET /linkedin/person.

SEO

The SEO section is about the blog Revnu writes for. postsPublished and postsHeld count only posts Revnu wrote, not ones you added yourself.

Search Console reports a day or two late, so gsc covers a window shifted back by two days. from and through give the exact dates. prevClicks is null, not 0, when the data doesn't reach back that far.

Outbound

Outbound is all-time, not windowed: one row per campaign in routes, sorted by sends. Each row has route, delivered, replied, bounced and pending (leads found but not yet sent), plus ready and drafted when Revnu could count them, and sequence with the campaign's approval state.

Why a section is unavailable

What a read-only token can't tell you

Some questions have no field. These come only from asking Revnu in a message, which needs agent:message:

• How a sending inbox's warm-up is going, and when it will start sending. No route returns warm-up progress.

• Why a blog post failed. postsFailed is a count. The cause stays with Revnu.

• The detail behind a LinkedIn pause beyond pauseReason, and what Revnu will do about it.

A message is a request for work, so a token that can ask can also start work. Authentication has the safest way to set that up.

Responses