LinkedIn Ads

Overview

LinkedIn Ads data synced to V4MOS.AI, through the integration's own endpoints

The V4MOS.AI LinkedIn Ads API gives you the raw records synced from the LinkedIn Ads accounts connected to your organization: ad accounts, campaign groups, campaigns, creatives and their daily analytics. 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/linkedin-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.

  1. Connect LinkedIn Ads in app.v4mos.ai (Connected accounts) and wait for the first sync.
  2. Call any endpoint below with your organizationId, for example GET /v1/linkedin-ads/ad-accounts?organizationId=….
  3. Every row carries integration_id and integration_name: the connected account it came from. To read a single account, pass that value as integrationId.

Available endpoints

Resources

EndpointWhat one row isdateFrom / dateTo filter
GET /v1/linkedin-ads/ad-accountsOne row per ad account: name, currency, type and status.—
GET /v1/linkedin-ads/campaign-groupsOne row per campaign group: account, status, allowed campaign types and schedule.—
GET /v1/linkedin-ads/campaignsOne row per campaign: group, type, cost type, optimization target, budget and schedule.—
GET /v1/linkedin-ads/creativesOne row per creative (ad): campaign, status and serving flags. created_at and last_modified_at are epoch milliseconds.—
GET /v1/linkedin-ads/campaign-analyticsOne row per campaign per day: impressions, clicks, engagement, spend in the account currency, leads, conversions and video metrics.date
GET /v1/linkedin-ads/creative-analyticsOne row per creative per day: impressions, clicks, engagement, spend in the account currency, leads, conversions and video metrics.date

Pagination and filters

  • page (default 1) and limit (default 500, max 5000). meta.hasNextPage says whether another page exists; rows come in a stable order, so walk the pages until it is false.
  • dateFrom / dateTo (YYYY-MM-DD, inclusive) filter by the date column shown in the table above. Resources without one reject them.
  • integrationId keeps 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.

On this page