Lotame Solutions

Lotame Solutions is a data collaboration and identity company for digital marketing and advertising. Its Spherical platform lets marketers, agencies, and publishers connect, enrich, and activate first- and third-party audience data, while Panorama ID delivers a privacy-first, cookieless identity for addressability across web, mobile app, and CTV. Lotame exposes a token-based Admin Services REST API (api.lotame.com/2/) for managing first-party data, building audiences, and pulling behavior and audience statistics, plus a server-side Panorama ID resolution API on sid.crwdcntrl.net for web and mobile (MAID) identity lookups. Lotame operates across 24 countries and was acquired by Publicis Groupe.

Lotame Solutions is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Data Management Platform, Identity, Advertising, and Marketing.

Lotame Solutions’ developer surface includes engineering blog, documentation, API reference, support, signup flow, authentication, and 23 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.6/100 thin ▬ flat Agent 8/100 agent aware Front door AI 3/6 light Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessOpen

2 APIs

Company Data Management Platform Identity Advertising Marketing Audience Data Data Collaboration AdTech

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 28.6/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 8.1 / 17

Access Clarity 6.0 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 4.4 / 15

Agent readiness — 8/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lotame-solutions/"><img src="https://apis.io/badge/lotame-solutions/card.svg" alt="Lotame Solutions on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 35.5 — up to +12.9 composite points
Operational Transparency scores 2.6 — up to +12.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lotame-solutions/apis.yml: open an issue on github.com/api-evangelist/lotame-solutions to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Amazon Seller Ecosystem (Selling Partner Appstore, Amazon Ads partners)	standard	54.3	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Lotame Admin Services API

Token-based REST API for managing first-party data, building and editing audience segments, activating audiences, and retrieving behavior and audience analytics on the Lotame Sp...

Panorama ID Server-Side API

Real-time server-side API that returns the assigned Panorama ID for an IP address and user-agent (web) or Mobile Advertiser ID / MAID (mobile app). JSON POST to sid.crwdcntrl.ne...

Lotame Solutions API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Lotame Solutions Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lotame Solutions Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lotame Solutions Authentication

0 schemes

SECURITY

Lotame Solutions Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Components

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

GitHubOrganization

GitHubOrganization

SourceCode

SourceCode

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Compliance

Compliance

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Source (apis.yml)

aid: lotame-solutions
name: Lotame Solutions
description: Lotame Solutions is a data collaboration and identity company for digital marketing and advertising. Its Spherical
  platform lets marketers, agencies, and publishers connect, enrich, and activate first- and third-party audience data, while
  Panorama ID delivers a privacy-first, cookieless identity for addressability across web, mobile app, and CTV. Lotame exposes
  a token-based Admin Services REST API (api.lotame.com/2/) for managing first-party data, building audiences, and pulling
  behavior and audience statistics, plus a server-side Panorama ID resolution API on sid.crwdcntrl.net for web and mobile
  (MAID) identity lookups. Lotame operates across 24 countries and was acquired by Publicis Groupe.
url: https://raw.githubusercontent.com/api-evangelist/lotame-solutions/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: stub
x-tier-reason: portfolio-lead
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 5
  pass: local-v1
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - lotame/api-examples
  open_source: unknown
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
image: https://cdn-ilbibgp.nitrocdn.com/eakWUVxgVLoymIJUurpQZcwTweYHDeju/assets/images/optimized/rev-6d2d189/www.lotame.com/wp-content/uploads/2025/05/lotame-website-favicon-300x300.png
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Data Management Platform
- Identity
- Advertising
- Marketing
- Audience Data
- Data Collaboration
- AdTech
apis:
- name: Lotame Admin Services API
  description: Token-based REST API for managing first-party data, building and editing audience segments, activating audiences,
    and retrieving behavior and audience analytics on the Lotame Spherical platform. JSON over HTTPS with GET/PUT/POST/DELETE,
    versioned under /2/, authenticated with x-lotame-token and x-lotame-access header credentials created in the Spherical
    platform.
  humanURL: https://my.lotame.com/category/administrative-api
  baseURL: https://api.lotame.com/2/
  properties:
  - type: Documentation
    url: https://api.lotame.com/docs/
  - type: APIReference
    url: https://my.lotame.com/t/35h37my/admin-services-api
  - type: Authentication
    url: authentication/lotame-solutions-authentication.yml
  - type: Conventions
    url: conventions/lotame-solutions-conventions.yml
  - type: Lifecycle
    url: lifecycle/lotame-solutions-lifecycle.yml
  - type: X-MCPServerCandidate
    url: mcp/lotame-solutions-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: DataModel
    url: data-model/lotame-solutions-data-model.yml
  - type: RateLimits
    url: rate-limits/lotame-solutions-rate-limits.yml
- name: Panorama ID Server-Side API
  description: Real-time server-side API that returns the assigned Panorama ID for an IP address and user-agent (web) or Mobile
    Advertiser ID / MAID (mobile app). JSON POST to sid.crwdcntrl.net/sid, identified by a Lotame-assigned static client_id,
    with IAB TCF v2 or Lotame consent signaling required per request.
  humanURL: https://my.lotame.com/category/panorama-id-apis
  baseURL: https://sid.crwdcntrl.net/sid
  properties:
  - type: Documentation
    url: https://my.lotame.com/t/60ykhkw/server-side-panorama-id-api-for-web
  - type: APIReference
    url: https://my.lotame.com/t/x2yf3d0/server-side-panorama-id-api-for-mobile-app-maids
  - type: ErrorCatalog
    url: errors/lotame-solutions-problem-types.yml
common:
- url: https://www.lotame.com/resources/
  type: Blog
- url: https://www.lotame.com/feed/
  type: BlogRSS
- type: Website
  url: https://www.lotame.com/
- type: DeveloperPortal
  url: https://my.lotame.com/
- type: Documentation
  url: https://api.lotame.com/docs/
- type: APIReference
  url: https://my.lotame.com/category/administrative-api
- type: Support
  url: https://www.cognitoforms.com/LotameSolutionsInc/SupportTicketForm
- type: SignUp
  url: https://my.lotame.com/signup
- type: Login
  url: https://platform.lotame.com/
- type: Blog
  url: https://www.lotame.com/resources
- type: TermsOfService
  url: https://www.lotame.com/legal/
- type: PrivacyPolicy
  url: https://www.lotame.com/privacy
- type: Authentication
  url: authentication/lotame-solutions-authentication.yml
- type: Conventions
  url: conventions/lotame-solutions-conventions.yml
- type: ErrorCatalog
  url: errors/lotame-solutions-problem-types.yml
- type: Lifecycle
  url: lifecycle/lotame-solutions-lifecycle.yml
- type: Conformance
  url: conformance/lotame-solutions-conformance.yml
- type: DomainSecurity
  url: security/lotame-solutions-domain-security.yml
- type: X-MCPServerCandidate
  url: mcp/lotame-solutions-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/lotame-solutions-llms.txt
- type: Packages
  url: packages/lotame-solutions-packages.yml
- type: SDKs
  url: packages/lotame-solutions-packages.yml
- type: Components
  url: components/lotame-solutions-components.yml
- type: DataModel
  url: data-model/lotame-solutions-data-model.yml
- type: Plans
  url: plans/lotame-solutions-plans-pricing.yml
- type: RateLimits
  url: rate-limits/lotame-solutions-rate-limits.yml
- type: Compliance
  url: https://www.lotame.com/legal/eu-privacy-consent-policy
- type: GitHubOrganization
  url: https://github.com/Lotame
- type: SourceCode
  url: https://github.com/Lotame/api-examples
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io

Lotame Solutions API — frequently asked questions

Does Lotame Solutions have an API?

Yes. APIs.io lists 2 APIs from Lotame Solutions, including Lotame Admin Services API and Panorama ID Server-Side API.

How do I authenticate with the Lotame Solutions API?

Lotame Solutions uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Lotame Solutions Authentication.

Is the Lotame Solutions API ready for AI agents?

Lotame Solutions has a Kin Score of 28.6 out of 100 (thin) and an Agent Readiness score of 7.9 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lotame-solutions"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lotame-solutions/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lotame-solutions/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.