Skip to content
Social

X Post Search

Up to 20 recent X posts for a keyword or author, with engagement counts.

POST/v1/x-post-search
15 credits / searchNewX (Twitter)
Request
curl -X POST https://api.1lookup.dev/v1/x-post-search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"phone validation"}'
Response
{
  "success": true,
  "data": {
    "query": "northwind coffee",
    "posts": [
      {
        "id": "1800000000000000001",
        "url": "https://x.com/priyaraman_ex/status/1800000000000000001",
        "text": "Tried the new Northwind Coffee fall blend this morning. Bright, a little citrus, would buy again.",
        "author": {
          "handle": "priyaraman_ex",
          "display_name": "Priya Raman"
        },
        "posted_at": "2026-11-12T14:05:00Z",
        "likes": 38,
        "reposts": 4,
        "replies": 6,
        "views": 2900
      },
      {
        "id": "1800000000000000002",
        "url": "https://x.com/marcusbell_ex/status/1800000000000000002",
        "text": "Does anyone know if Northwind Coffee ships whole bean to Canada?",
        "author": {
          "handle": "marcusbell_ex",
          "display_name": "Marcus Bell"
        },
        "posted_at": "2026-11-11T19:41:00Z",
        "likes": 3,
        "reposts": 0,
        "replies": 2,
        "views": 410
      }
    ]
  },
  "meta": {
    "credits_used": 15,
    "credits_remaining": 999,
    "cached": false,
    "request_id": "req_8f3a2c1e9b7d"
  }
}

Authorization

Authorizationstring<bearer>required

Your API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.

Body

Send the fields as a JSON object with Content-Type: application/json.

querystringrequired

Keyword or from:handle. Example: phone validation

freshboolean

Skip the 7-day cache and run a new lookup. Charged as a normal lookup.

referencestring

Your own identifier, echoed back in meta and shown in lookup history.

Response

A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.

successboolean

true when the lookup ran.

data.posts[].textvalue

The full text of the matching post.

data.posts[].author.handlevalue

The handle of the account that wrote the post.

data.posts[].posted_atvalue

When the post was published, as an ISO 8601 timestamp in UTC.

data.posts[].likesvalue

Like count at the time of the search.

data.posts[].repostsvalue

How many times the post was reposted.

data.posts[].repliesvalue

Number of replies under the post.

data.posts[].viewsvalue

The public view count X shows for the post.

data.posts[].urlvalue

A direct link to the post, which you can pass to X Post Replies.

meta.credits_usednumber

Credits charged for this call.

meta.credits_remainingnumber

Your balance after the call.

meta.cachedboolean

true when the result came from the 7-day cache.

meta.request_idstring

Quote this when you contact support.

Errors

A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.

HTTPCodeMeaning
401unauthorizedThe key is missing, malformed or revoked.
402insufficient_creditsYour credits are used up and pay as you go is off or at its limit.
422invalid_inputA field is missing or malformed. The field property names it.
429rate_limitedToo many requests for this key. Wait for the Retry-After interval.
500internal_errorSomething failed on our side. Safe to retry.
503source_unavailableAn upstream source did not answer in time. Safe to retry.

Billing

15 credits / search. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.

Product overview and use cases