Spectral linting rules defining API design standards and conventions for Interpublic Group.
0 Rules
Authorship not recorded
No authorship marker is recorded for this file. It is not presented as the provider's; it was most likely written by an API Evangelist pass before outputs were stamped.
x-aid: interpublic
x-name: Interpublic Group Rules
description: >-
Validation, governance, and operational rules applied to the Interpublic
Group APIs.json index. Interpublic Group publishes no product REST API and
no OpenAPI at the holding-company level; the OpenAPI documents in openapi/
are a mechanical conversion of the WordPress route-discovery document the
provider serves at https://interpublic.com/wp-json/ (fetched 2026-08-12,
HTTP 200) and are marked method: derived.
x-type: company
x-profile:
- apis.json
x-governance:
source: api-evangelist
steward: Kin Lane
visibility: public
rules:
- id: apisjson-required-fields
description: APIs.json must include aid, name, description, url, created, modified, and maintainers.
severity: error
- id: apisjson-tags-upper-case
description: All tags must use upper-case first letters.
severity: warn
- id: openapi-non-empty
description: OpenAPI specs must reference real, validated endpoints. Stub or empty specs are not permitted.
severity: error
- id: artifact-location
description: All OpenAPI specs live under openapi/{repo}-openapi.yml.
severity: error
- id: holding-company-watch
description: Track Omnicom-IPG merger integration; revisit if a unified developer surface is published under omc.com.
severity: info
Discovery needs no key. Ratings and market analysis are Pro.
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.