Simon Data · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Simon Data Audience API

5 actions 5 updates documentation extends openapi/simon-data-audience-api-openapi.yml
Derived by API Evangelist Built from the contracts Simon Data publishes. Simon Data did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

inx-apievangelist-notex-apievangelist-enrichedx-apievangelist-sourcebearerAuthtagsx-apievangelist-rate-limit

Targets 5

$.info
$.paths['/contacts'].get.parameters[?(@.name=='identity')]
$.paths['/contacts'].get.parameters[?(@.name=='fields')]
$.components.securitySchemes
$.paths['/contacts'].get

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Simon Data Audience API
  version: 1.0.0
extends: openapi/simon-data-audience-api-openapi.yml
x-generated: '2026-08-13'
x-method: generated
x-source: >-
  Records what API Evangelist changed relative to Simon Data's own published definition, preserved verbatim at
  openapi/_original/simon-data-readme-get-a-contact-openapi.json. Two corrections, both grounded in Simon Data's own
  documentation: the provider's definition declares identity and fields as path parameters, but the Getting Started
  page's curl example passes them as query parameters
  (GET /audience/v2/contacts?identity=email:<address>); and the provider's definition carries a placeholder oauth2
  scheme with an empty flows object, while the same page documents bearer-token authentication.
actions:
- target: $.info
  update:
    x-apievangelist-enriched: '2026-08-13'
    x-apievangelist-source: https://docs.simondata.com/reference/get-a-contact.md
- target: "$.paths['/contacts'].get.parameters[?(@.name=='identity')]"
  update:
    in: query
    x-apievangelist-note: >-
      Corrected from `in: path` to `in: query`; the provider's own curl example passes it as a query string parameter.
- target: "$.paths['/contacts'].get.parameters[?(@.name=='fields')]"
  update:
    in: query
    x-apievangelist-note: >-
      Corrected from `in: path` to `in: query`, per the provider's Getting Started example.
- target: $.components.securitySchemes
  update:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Bearer token issued by a Simon Data Client Solutions Manager. Replaces the provider definition's placeholder
        `sec0` oauth2 scheme, which declares an empty flows object.
- target: "$.paths['/contacts'].get"
  update:
    tags: [Contacts]
    x-apievangelist-rate-limit: 50 requests/second per organisation, aggregated across all bearer tokens

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay
curl "https://apis.io/api/v1/overlays/simon-data-audience-api-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

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.

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