Lynx · Schema

ClientOrgNotificationConfigurationData

CompanyHealthcareFintechPaymentsBenefitsHealth Savings AccountsEmbedded FinanceCard IssuingInsurance

Properties

Name Type Description
clientOrg object
notificationId string Unique id for the notification.
name string Unique name within a client org that identifies the notification
subject string The subject line seen by the member before clicking into the notification
body string The body of the notification message seen by the member upon selection
trigger string Indicates if the notification is triggered by a date or an event via webhook.
triggerDate string Setting the date that the notification will be triggered. Date must be a future date
recipientType string Defines the population parameters for the notification
frequency string Determines if the notification will only be sent one time, or if the notification can be sent each time the trigger occurs
accountType string Specifies the account types receiving the notification when ‘Recipient Type’ is ‘Account Type’.
eventName string Specifies the Lynx event initiating the notification
channel string
imageUrl string
deepLinkUrl string
ttlSeconds integer
requiresApproval boolean
View JSON Schema on GitHub

JSON Schema

lynx-client-org-notification-configuration-data-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/lynx/main/json-schema/lynx-client-org-notification-configuration-data-schema.json",
  "title": "ClientOrgNotificationConfigurationData",
  "x-generated": "2026-10-14",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/lynx-external-notification-api-openapi.yml#/components/schemas/ClientOrgNotificationConfigurationData",
  "type": "object",
  "properties": {
    "clientOrg": {
      "$ref": "#/$defs/ClientOrgDto"
    },
    "notificationId": {
      "type": "string",
      "description": "Unique id for the notification."
    },
    "name": {
      "type": "string",
      "description": "Unique name within a client org that identifies the notification"
    },
    "subject": {
      "type": "string",
      "description": "The subject line seen by the member before clicking into the notification"
    },
    "body": {
      "type": "string",
      "description": "The body of the notification message seen by the member upon selection"
    },
    "trigger": {
      "type": "string",
      "description": "Indicates if the notification is triggered by a date or an event via webhook."
    },
    "triggerDate": {
      "type": "string",
      "description": "Setting the date that the notification will be triggered. Date must be a future date"
    },
    "recipientType": {
      "type": "string",
      "description": "Defines the population parameters for the notification"
    },
    "frequency": {
      "type": "string",
      "description": "Determines if the notification will only be sent one time, or if the notification can be sent each time the trigger occurs"
    },
    "accountType": {
      "type": "string",
      "description": "Specifies the account types receiving the notification when ‘Recipient Type’ is ‘Account Type’."
    },
    "eventName": {
      "type": "string",
      "description": "Specifies the Lynx event initiating the notification"
    },
    "channel": {
      "type": "string"
    },
    "imageUrl": {
      "type": "string"
    },
    "deepLinkUrl": {
      "type": "string"
    },
    "ttlSeconds": {
      "type": "integer",
      "format": "int32"
    },
    "requiresApproval": {
      "type": "boolean"
    }
  },
  "required": [
    "clientOrg",
    "notificationId"
  ],
  "$defs": {
    "ClientOrgDto": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "The name of the client organization"
        }
      },
      "required": [
        "name"
      ]
    }
  }
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/lynx-client-org-notification-configuration-data"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

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.

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