Overview
OpenAI Ads data synced to V4MOS.AI, through the integration's own endpoints
The V4MOS.AI OpenAI Ads API gives you the raw records synced from the OpenAI Ads accounts connected to your organization: ad accounts, campaigns, ad groups, ads and their daily insights. Rows come as they were synced, with the warehouse column names (snake_case), so you can load them straight into your BI. All endpoints use the /v1/openai-ads prefix and the same authentication, pagination and response format.
Getting started
Base URL: https://data.v4mos.ai. Every call requires your API credentials and the organizationId — see Authentication.
- Connect OpenAI Ads in app.v4mos.ai (Connected accounts) and wait for the first sync.
- Call any endpoint below with your
organizationId, for exampleGET /v1/openai-ads/ad-accounts?organizationId=…. - Every row carries
integration_idandintegration_name: the connected account it came from. To read a single account, pass that value asintegrationId.
Available endpoints
- getAd accounts
/v1/openai-ads/ad-accountsOne row per ad account: name, status, timezone, currency and review status. - getCampaigns
/v1/openai-ads/campaignsOne row per campaign: status, mode, objective, bidding and budget limits (in micros). - getAd groups
/v1/openai-ads/ad-groupsOne row per ad group: status and bidding configuration (max bid in micros). - getAds
/v1/openai-ads/adsOne row per ad: status, review status and creative (title, body, target URL, image). - getCampaign insights
/v1/openai-ads/campaign-insightsOne row per campaign per day: impressions, clicks, spend and conversions. - getCampaign conversion insights
/v1/openai-ads/campaign-conversion-insightsOne row per campaign per day: conversions split into click-through and view-through, and attributed sales. - getAd group insights
/v1/openai-ads/ad-group-insightsOne row per ad group per day: impressions, clicks, spend and conversions. - getAd insights
/v1/openai-ads/ad-insightsOne row per ad per day: impressions, clicks, spend and conversions.
Resources
| Endpoint | What one row is | dateFrom / dateTo filter |
|---|---|---|
GET /v1/openai-ads/ad-accounts | One row per ad account: name, status, timezone, currency and review status. | — |
GET /v1/openai-ads/campaigns | One row per campaign: status, mode, objective, bidding and budget limits (in micros). Times are epoch seconds. | — |
GET /v1/openai-ads/ad-groups | One row per ad group: status and bidding configuration (max bid in micros). Times are epoch seconds. | — |
GET /v1/openai-ads/ads | One row per ad: status, review status and creative (title, body, target URL, image). Times are epoch seconds. | — |
GET /v1/openai-ads/campaign-insights | One row per campaign per day: impressions, clicks, spend and conversions. | date |
GET /v1/openai-ads/campaign-conversion-insights | One row per campaign per day: conversions split into click-through and view-through, and attributed sales. | date |
GET /v1/openai-ads/ad-group-insights | One row per ad group per day: impressions, clicks, spend and conversions. | date |
GET /v1/openai-ads/ad-insights | One row per ad per day: impressions, clicks, spend and conversions. | date |
Pagination and filters
page(default 1) andlimit(default 500, max 5000).meta.hasNextPagesays whether another page exists; rows come in a stable order, so walk the pages until it isfalse.dateFrom/dateTo(YYYY-MM-DD, inclusive) filter by the date column shown in the table above. Resources without one reject them.integrationIdkeeps the rows of one connected account.- Answers are cached for 30 minutes and the data is synced once a day — see Data sync.
Response format
{
"data": [{ "...": "one object per row, with the columns listed on each endpoint" }],
"meta": {
"page": 1,
"limit": 500,
"hasNextPage": true,
"hasPreviousPage": false
}
}Amounts and large counters (fields with format: decimal or format: int64 in each endpoint schema) come as strings, e.g. "125.50", so no precision is lost. Convert them to a decimal type on your side.