This hourly T-Values Reporting API is still available if you already have credentials. New reporting should use Programmatic TAP access.
For how to tag clicks (t1, t2, t3) and how they show up in TAP earnings exports, see T-Values (Tracking Tags). Start there unless you actually need this HTTP API.
T-Values Reporting API
Use this only if Talroo gave you a username / password for the legacy JSON pipeline. Everyone else should use the Earnings Report CSV (with optional t1–t3) and Tracking Tags.
Email publishers@talroo.com for access or rotations. Don't reuse old keys unless we've confirmed this API is still enabled for your publisher id.
Authentication
POST https://nv3xq21kwj.execute-api.us-east-1.amazonaws.com/prod/auth
Request body:
{
"username": "YOUR_USERNAME",
"password": "YOUR_PASSWORD"
}
Response:
{
"id_token": "eyJhbGciOiJIUzI1NiIs...",
"access_token": "eyJhbGciOiJIUzI1NiIs...",
"refresh_token": "eyJhbGciOiJIUzI1NiIs...",
"expires_in": 3600
}
Report Data Endpoint
GET https://0tphaqutzi.execute-api.us-east-1.amazonaws.com/prod/reports/publisher/t_values_date_breakdown
Required headers:
Authorization: Bearer {ID_TOKEN}
Example response:
{
"data_type": "tabular",
"data_timestamp": 1759999999,
"columns": ["Date", "T1", "T2", "T3", "Clicks", "Earnings"],
"data": [
["2022-08-17", "value1", "value2", "value3", 150, 75.50],
["2022-08-16", "value1", "value2", "value3", 200, 100.00]
]
}
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
time_range | string | Yes | Time bucket for retrieval |
f_t1 | integer | No* | Include t1 groupings (1 = yes, 0 = no) |
f_t2 | integer | No* | Include t2 groupings |
f_t3 | integer | No* | Include t3 groupings |
f_publisher_id | string | No | Filter by Talroo feed identifier |
At least one of f_t1, f_t2, or f_t3 must be 1 or you get empty results. Check TAP after you change filters.
Time Ranges
| Value | Meaning |
|---|---|
thisfull_day | Today, including the latest hourly update |
previous_day | Yesterday (UTC, closed) |
epoch_start~epoch_end | Custom window (epoch_start and epoch_end are UNIX seconds, daily grain) |
Example
time_range=1643882400~1643885999
That window is UTC seconds. If it disagrees with TAP, TAP is the number finance uses.
Epochs are UTC. TAP often displays US Eastern. Convert before you stitch this to payouts.
Response Shape
Columns appear based on toggles (f_t1, f_t2, f_t3). Clicks and Earnings always accompany whichever tag columns you enabled:
{
"columns": [
"Date",
"T1",
"T2",
"T3",
"Clicks",
"Earnings"
],
"data": [
["2022-08-17", "value1", "value2", "value3", 150, 75.50]
]
}
Error Handling
| Status | Meaning | What to do |
|---|---|---|
| 200 | Success | Parse data; validate column order before inserts |
| 401 | Unauthorized | Regenerate bearer token via /auth |
| 404 | Not found | Rare. Retry a couple of times with backoff. |
| 429 | Throttled | Back off exponentially; widen intervals between pulls |
| 500 | Platform issue | Pause automation and email publishers@talroo.com |
The data refreshes a little after minute 45 of each hour. Filter to the tag dimensions (f_tx) you actually report on. Wide queries make large payloads. Refresh ID tokens at least 5 minutes before they expire. Rotate credentials if they're leaked.