Head to head · Ad reporting · October 2026 research run

Amazon Ads API vs LinkedIn Marketing APIs

LinkedIn Marketing APIs scores 60.5 (C) on agent readiness against Amazon Ads API's 55.4 (C), and leads in 4 of 7 scored categories. Amazon Ads API leads on schema & documentation and payments & pricing. Both do ad reporting.

Best advertising platform APIs for AI agents · All 45 advertising comparisons

Which one, for what

Amazon Ads API C

Best for Agents managing sponsored ads and Amazon DSP for an advertiser or agency that already has API approval, and teams that want a vendor-run MCP server.

Ahead on

  • Schema & documentation, 76 against 66
  • Payments & pricing, 60 against 45

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Access needs an approved application and an advertiser's consent in a browser

LinkedIn Marketing APIs C

Best for An agent that reports on and manages LinkedIn campaigns for accounts its operator administers, especially read-only reporting, which has no account limit on Development tier.

Ahead on

  • Reliability, 66 against 45
  • Security & auth, 52 against 46

Also in its favour

  • No incidents deducted, where Amazon Ads API loses 3 points for them

Watch for

Standard rate limits are not published. An app sees its limit in the Developer Portal only after calling the endpoint

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability LinkedIn Marketing APIs +21

Amazon Ads API 45

Graded on the REST API with the hosted checklist. status.ads.amazon.com is a script-drawn status page by region and category, per the 8 October check (20). Its history loads from a JSON data file, which this run doesn't read, so the 8 October incident reading from that file is struck and the window from 6 August is unread (5). No numeric rate limit was found. Amazon's own skills in its docs repository say to respect rate limits per endpoint, with no numbers (0). The same skills map 429 TOO_MANY_REQUESTS to waiting with exponential backoff, and every operation in the published OpenAPI files lists a 429 response. No idempotency key was found (10). No SLA found for the API (0). The API is generally available, and the release notes still call the MCP server a beta (10).

LinkedIn Marketing APIs 66

Read with the hosted rubric, grading the public REST API. Statuspage at linkedin-apistatus.com with incident history back to 2023, covering every LinkedIn API and listing no components (15). Its history feed lists no incident after 18 June 2026, so the 90 days from 4 August to 2 November are clean (30). The rate-limit page says standard limits are not published and are shown per endpoint in the Developer Portal after a first call. Published numbers are 45 million metric values per 5 minutes and 15,000 elements a response on adAnalytics (6). 429 is documented, 503 and 504 carry advice to retry, and no Retry-After header, backoff schedule or idempotency key was found (5). No SLA was found in the documentation (0). The Advertising API is generally available on version 202610 (10). 15+30+6+5+0+10 = 66.

Payments & pricing Amazon Ads API +15

Amazon Ads API 60

No x402, MPP or L402 (0). The API product page, re-read on 4 November, says there are no additional fees from Amazon Ads to use the API, with selling account fees and campaign costs billed separately (20). Test accounts serve no ads, so no fees apply (20). A person must create a developer account, apply for access and complete an advertiser's browser consent (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

LinkedIn Marketing APIs 45

No x402, MPP or L402 (0). No fee for API access appears in the developer docs, and no docs page states a price or says the API is free; the API and Marketing API terms on www.linkedin.com weren't readable to us. Ad spend is set by campaign budgets and billed to the ad account (10). A developer application costs nothing and a test ad account needs no card or payment details (20). A person has to create a LinkedIn Page and a developer application, apply for the product and give OAuth consent in a browser (0). 0+10+20+0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation Amazon Ads API +10

Amazon Ads API 76

Amazon's docs repository publishes OpenAPI 3.0.1 files for the Unified API (sponsored products, sponsored brands, SP global and DSP), 97 operations and 1,299 schemas, readable without a login (25). No llms.txt (advertising.amazon.com/llms.txt redirects to a not-found page), and the docs site returns a JavaScript shell to a plain fetch (0). Operation descriptions are short, such as "Create ad extensions", and list the required permissions. When to use an operation is left to the guides (10). Typed inputs with 231 enums, required fields and bounds such as maxResults (14). A 49-value ErrorCode enum and typed 4xx and 429 responses on every operation, with examples in only 4 of 97 operations (12). Versioned resource paths and dated release notes with an RSS feed (15).

LinkedIn Marketing APIs 66

No OpenAPI specification found. The docs link a public Postman workspace, which needs JavaScript and was not read (5). Every docs page we requested with Accept: text/markdown came back as Markdown with front matter. No llms.txt at learn.microsoft.com (8). Reference pages state limits and restrictions per endpoint, with use-case guides and a restricted-uses page (14). Field tables give type, required and enum values, but queries use Rest.li syntax such as List(urn%3Ali%3AsponsoredAccount%3A...) and nested targeting criteria (11). curl and HTTP samples on each method, error tables per endpoint and a structured error schema on three resources (13). Monthly versions selected by header and a dated changelog (15).

Security & auth LinkedIn Marketing APIs +6

Amazon Ads API 46

OAuth 2.0 authorisation code through Login with Amazon. The OpenAPI files declare four scopes, and advertising::campaign_management "grants write access to campaign management" for most requests. Refresh tokens issued from 30 July 2026 expire 365 days after consent, per a release note of 26 May. The MCP server supports OAuth 2.1 (24). Each operation names the permission it needs, such as advertiser_campaign_edit, and test accounts serve no ads and bill nothing. No confirmation step for writes or deletes was found (10). Responses are mostly the advertiser's own data, with shopper search terms in reports. No injection guidance found (7). The 8 October reading of the API integration dashboard (call volume, throttling and errors by hour) came from the docs site's content data file, which this run doesn't read, so it is struck and per-call visibility is unread (0). www.amazon.com now disallows ClaudeBot, Claude-User and Claude-SearchBot, so the 8 October security.txt reading (a HackerOne programme) is struck. advertising.amazon.com has no security.txt, and the docs repository sends security reports to the AWS and Amazon vulnerability reporting page. No SOC 2 or ISO 27001 statement for Amazon Ads was found (5).

LinkedIn Marketing APIs 52

Three-legged OAuth 2.0 only, with scopes per product such as r_ads, r_ads_reporting, rw_ads, rw_dmp_segments and rw_conversions. Access tokens last 60 days, refresh tokens 365, a member can revoke them, and a token introspection endpoint exists. The docs tell developers not to pass tokens in URLs (26). Read scopes are separate from rw_ads, the VIEWER role is read-only even with rw_ads, and Development tier limits edits to five ad accounts. No confirmation step for writes (16). Campaign data is mostly the advertiser's own, lead form responses are written by members, and no prompt-injection guidance was found (5). Entities carry created and last-modified times and the Developer Portal shows usage per endpoint. No audit log API found (5). Security programme unread (0). The 8 October readings of security.txt (a HackerOne programme) and of the data processing agreement (an annual SOC report and an ISO 27001 mapping on request) came from www.linkedin.com, whose robots.txt disallows our crawler on every path, so they're struck; the HackerOne page renders only with JavaScript, and no security or disclosure page was found on the developer docs host. 26+16+5+5+0 = 52.

Score by category

CategoryWeightAmazon Ads APILinkedIn Marketing APIsEdge
Reliability16%4566LinkedIn Marketing APIs +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7666Amazon Ads API +10
Agent ergonomics13%6263LinkedIn Marketing APIs +1
Security & auth14%4652LinkedIn Marketing APIs +6
Payments & pricing10%6045Amazon Ads API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6564Amazon Ads API +1
Transparency & trust7%6669LinkedIn Marketing APIs +3
Negative events≤15-30
TotalC 55.4/100C 60.5/100

Facts side by side

FactAmazon Ads APILinkedIn Marketing APIs
KindHTTP APIHTTP API
VendorAmazonLinkedIn Corporation
Hosted endpointhttps://advertising-api.amazon.comno (local only)
TransportsHTTPHTTP
AuthOAuthOAuth
PricingFreeFree
x402nono
LicenceProprietary service under the Amazon Advertising API Licence Agreement. The Postman collections and samples in amzn/ads-advanced-tools-docs are MIT-0Proprietary service under the LinkedIn API terms of use and the Marketing API terms. The beta Python and JavaScript clients carry LinkedIn's API development software licence
Read-only variant documentednoyes
llms.txtnono
Last release2026-11-022026-10-15
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updated2026-06-30couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularitynone25k npm/wk, 386k PyPI/wk
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

Amazon Ads API

Public OpenAPI files in Amazon's docs repository, test accounts that serve no ads and dated release notes with an RSS feed support agent use. Access needs an approved application and an advertiser's OAuth consent, no numeric rate limits were found, and some behaviour changes were announced the day they took effect. The MCP server is in beta.

LinkedIn Marketing APIs

Monthly API versions are each supported for at least a year, with dated sunsets and a changelog, and a test ad account lets an agent create campaigns that are never served or billed. Access needs LinkedIn's approval and a member's OAuth consent, standard rate limits are not published, and no OpenAPI specification was found.

Before you call either

Amazon Ads API

  1. Send Amazon-Advertising-API-ClientId and a Bearer access token on every call, and Amazon-Advertising-API-Scope with a profile ID on most
  2. Call the host for the advertiser's region. advertising-api.amazon.com is North America, advertising-api-eu Europe and advertising-api-fe Far East
  3. Track the consent date. Refresh tokens issued from 30 July 2026 expire 365 days after consent, and the advertiser must consent again
  4. On 429 TOO_MANY_REQUESTS, back off exponentially. Request an export instead of listing every entity
  5. Rehearse writes in a test account before anything can spend
  6. Read the release notes feed before relying on a field. Some changes took effect on the day they were posted

LinkedIn Marketing APIs

  1. Send Linkedin-Version: YYYYMM and X-Restli-Protocol-Version: 2.0.0 on every call. A missing or sunset version returns an error (426 for a deprecated one)
  2. Create one test ad account with "test": true and build there first. Its creatives are auto-rejected and never billed, and it returns no reporting data
  3. Create campaigns as DRAFT or PAUSED and check servingStatuses before activating. Some validation is postponed until activation
  4. Pass fields= on adAnalytics. Responses stop at 15,000 elements and the endpoint throttles at 45 million metric values per 5 minutes
  5. Set surface (LAN or CTV) when creating publisher lists on version 202611 or later. From 15 December 2026 a campaign using a list of the other placement type fails with 400

Questions

Which is better for AI agents, Amazon Ads API or LinkedIn Marketing APIs?

LinkedIn Marketing APIs scores 60.5 (C) on agent readiness against Amazon Ads API's 55.4 (C), and leads in 4 of 7 scored categories. Amazon Ads API leads on schema & documentation and payments & pricing.

Do Amazon Ads API and LinkedIn Marketing APIs need an API key?

Both use an OAuth sign-in.

Can an agent call Amazon Ads API and LinkedIn Marketing APIs without installing anything?

Amazon Ads API has a hosted endpoint at https://advertising-api.amazon.com. No hosted endpoint is listed for LinkedIn Marketing APIs.

Other comparisons with Amazon Ads API or LinkedIn Marketing APIs

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.