<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=9151474&amp;fmt=gif">
Skip to content

Connector · Social

X Ads data, collected and structured for you.

Odins pulls spend from X Ads every day and structures it per campaign with the rest of your media data, with history requested from 2020. Use it in Odins, in your own warehouse, or through your AI assistant.

Fully managed · reviewed November 2026

Two ways to get X Ads data out.

The X Ads API covers campaigns, audiences, creatives and analytics, and an app has to be approved before it can call it. The work sits in the syncing: one request per placement, days cut in the account's time zone, and spend that stays an estimate for days.

Build and run it yourself

  1. Create a developer account and an app, then request Ads API access with the Ads API Access Form. X says to allow up to 3 business days for review.
  2. Sign every request with OAuth 1.0a. The advertiser authorizes your app in a 3-legged flow, or adds your X user to the ads account, where CAMPAIGN_ANALYST can view campaigns and stats.
  3. For history, create asynchronous jobs with POST stats/jobs/accounts/:account_id, poll until they finish, then download and unzip the file. A job covers up to 90 days and 20 entity IDs. The synchronous endpoint stops at 7 days.
  4. Ask once per placement: ALL_ON_TWITTER, SPOTLIGHT and TREND each need a request of their own.
  5. Read recent days again. billed_charge_local_micro is an estimate for up to 3 days, and X processes billing data for up to 14 days.
  6. Divide spend by one million, align days with midnight in the account's time zone, and map campaigns to your own markets and product lines.

Then monitor it, wait out every rate limit reset, and move to the next API version when X announces one.

Have Odins run it

  1. Access is set up with you at onboarding, through your Odins onboarding link. Credentials are never sent by email.
  2. We sync every day, monitor the pipeline and maintain the connector as X changes its API.
  3. You get spend per campaign per day, in the same structure as every other channel, with history requested from 2020.
  4. More detail, such as ad group level, is added when you ask for it.

The same goes for every other source you use. One team runs all of them. See all connectors

What the X Ads API offers.

For spend and performance, the analytics endpoints do the work and a few list endpoints supply names, currency and time zone. X's own documentation is the reference.

GET https://ads-api.x.com/12/stats/accounts/:account_id

EndpointWhat it returnsGood to know
GET stats/accounts/:account_id Synchronous analytics for the metric groups you name, by hour, day or total. At most 7 days and 20 entity IDs per request.
POST stats/jobs/accounts/:account_id Creates an asynchronous job for the same metrics. Up to 90 days, or 45 days with segmentation.
GET stats/jobs/accounts/:account_id Job status and, once the job has finished, the URL of the gzip results file.
GET stats/accounts/:account_id/active_entities The entities whose metrics changed in a period. At most 90 days per request.
GET accounts/:account_id/campaigns Campaign names, status, budgets and currency. Up to 1,000 records per request.

Metric groups

  • BILLING
  • ENGAGEMENT
  • VIDEO
  • WEB_CONVERSION
  • MOBILE_CONVERSION
  • LIFE_TIME_VALUE_MOBILE_CONVERSION
  • Auth OAuth 1.0a
  • Format JSON, job results gzipped
  • Quota 250 synchronous requests per 15 minutes

Worth knowing about X Ads data.

Spend stays an estimate for days.

X locks every metric after 24 hours except spend. billed_charge_local_micro is an estimate for up to 3 days and can decrease after 24 hours, through credits for overspend and billable events found to be junk.

Days follow the account's time zone.

With DAY granularity, start and end times must sit on midnight in the ads account's time zone. The time zone cannot be edited through the API.

API totals can differ from the Ads UI.

X names two usual causes: a placement that was not requested, and end times, which are exclusive in the API and inclusive in the Ads UI.

Spend comes in micros, without VAT.

Currency values are in micros, so 5.50 is encoded as 5,500,000. The currency field on the campaign gives the three-letter code. Spend arrives excluding VAT.

What you get back.

Two layers. The raw one mirrors X Ads. The structured one is the table every source lands in, organised by your own markets and product lines.

Structured layer

Per campaign, per day
In the structured tableFor X Ads
DateDaily
Company and marketSet by your routing rules on campaign names
Channel and mediaFollows your media plan
Source campaignCampaign
SpendSpend, excluding VAT

Raw layer

As X returns it

Daily spend per campaign as the X Ads API reports it. More detail is added on request.

Use it where you work.

In your warehouse

Raw and structured tables delivered to BigQuery, Snowflake, Redshift or Databricks. Some customers use Odins for this alone.

How data integration works

In Odins

Reporting across every channel, and a model that shows what X contributes and where more spend still pays.

See the platform

Through your AI assistant

Connect Claude, ChatGPT or Copilot to Odins with MCP and ask for the numbers in plain language.

How the Odins MCP works

Questions.

Does X Ads have an API?

Yes. The X Ads API covers campaign management, audiences, creatives and analytics. An app has to be approved for Ads API access first, and every request is signed with OAuth 1.0a. Parts of it still carry the Twitter name, such as the placement value ALL_ON_TWITTER.

How do I get X Ads data into BigQuery?

Access is set up with you at onboarding, through your Odins onboarding link. Odins syncs daily and delivers raw tables plus one structured cross-channel dataset to BigQuery, Snowflake, Redshift or Databricks.

How far back does X Ads data go?

X's documentation states no cutoff for analytics history, and says an entity's status does not affect whether its metrics are available. Odins requests history from 2020.

What are the rate limits on the X Ads API?

Synchronous analytics allow 250 requests per 15 minutes at user level. Asynchronous analytics allow 100 jobs in processing at a time per ads account. A rate-limited request returns HTTP 429.

Your sources

Send us your list of sources.

Tell us which platforms you use. We reply with what is covered, how access works and what you get back.

Send your list
The Odins letter

Where marketing budgets work hardest, once a month.

One short email: a question about marketing investment, answered with numbers, and what it means for the next budget decision.

  • One email a month
  • Written by the team that builds and runs the models

Protected by reCAPTCHA: Google's Privacy Policy and Terms apply.