Later Marketer Notifications API

The MarketerNotifications API from Later — 2 operation(s) for marketernotifications.

Operations 2

PUT /v1/notification-groups #
PUT /v1/notification-preferences/{actionGroupId} #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/later-marketernotifications-api"
All apis
curl "https://apis.io/api/v1/apis?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.

OpenAPI Specification

later-marketernotifications-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: 1.0.0
  description: Identify your most influential customers and activate them to drive more conversions on social.
  title: MAVRCK.IO Marketer Notifications API
servers:
- url: http://app.splashscore.com/v1
- url: https://app.splashscore.com/v1
security:
- apiKey: []
tags:
- name: MarketerNotifications
paths:
  /v1/notification-groups:
    put:
      operationId: updateNotificationGroups
      responses:
        '200':
          description: OK
        '400':
          description: Missing Parameter
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidateErrorJSON'
        '500':
          description: Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServerError'
      tags:
      - MarketerNotifications
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateNotificationBodyDefinition'
        required: true
  /v1/notification-preferences/{actionGroupId}:
    put:
      operationId: setNotificationPreferences
      responses:
        '200':
          description: OK
        '400':
          description: Missing Parameter
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidateErrorJSON'
        '500':
          description: Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServerError'
      tags:
      - MarketerNotifications
      parameters:
      - in: path
        name: actionGroupId
        required: true
        schema:
          type: number
          format: double
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SetNotificationPreferenceBodyDefinition'
        required: true
components:
  schemas:
    ServerError:
      properties:
        message:
          type: string
          enum:
          - Server Error
        details:
          properties: {}
          additionalProperties:
            additionalProperties: true
          type: object
      required:
      - message
      - details
      type: object
      additionalProperties: false
    NotificationQueryFields:
      properties:
        notificationTypes:
          items:
            $ref: '#/components/schemas/NotificationType'
          type: array
        actionGroupId:
          type: number
          format: double
        notificationGroupId:
          type: string
      type: object
    SetNotificationPreferenceBodyDefinition:
      properties:
        actionGroupId:
          type: string
        data:
          $ref: '#/components/schemas/NotificationPreferenceFlags'
      required:
      - actionGroupId
      - data
      type: object
    NotificationPreferenceFlags:
      properties:
        emailTimeframe:
          $ref: '#/components/schemas/EmailNotificationTimeframe'
        emailConceptNotifications:
          type: boolean
        emailFailedPaymentNotifications:
          type: boolean
        emailDraftNotifications:
          type: boolean
        emailApplicationNotifications:
          type: boolean
        emailConfirmationNotifications:
          type: boolean
        emailContentNotifications:
          type: boolean
        emailMessageNotifications:
          type: boolean
        showConceptNotifications:
          type: boolean
        showFailedPaymentNotifications:
          type: boolean
        showDraftNotifications:
          type: boolean
        showApplicationNotifications:
          type: boolean
        showConfirmationNotifications:
          type: boolean
        showContentNotifications:
          type: boolean
        showMessageNotifications:
          type: boolean
      required:
      - emailTimeframe
      - emailFailedPaymentNotifications
      - emailDraftNotifications
      - emailApplicationNotifications
      - emailConfirmationNotifications
      - emailContentNotifications
      - emailMessageNotifications
      - showFailedPaymentNotifications
      - showDraftNotifications
      - showApplicationNotifications
      - showConfirmationNotifications
      - showContentNotifications
      - showMessageNotifications
      type: object
      description: 'tsoa derives request validation from this type, so a non-optional property is a **required** body

        field and a client that omits it gets a 400 `ValidateError`.


        That is why the two concept flags are optional and the other twelve are not: later-influence sends

        a fixed payload built from its own defaults object, so making these required would reject every

        preference save from any client older than CMP-1542 — and sapi and later-influence deploy on

        independent cadences. Leaving them out is well defined rather than lossy: the columns are nullable

        with defaults, and `NotificationPreferencesService.upsert` spreads this object into the statement,

        so an absent key keeps the column''s default on insert and its current value on update. An old

        client cannot clobber a preference it does not know about.


        Do not make these required until every client sends them.'
    ValidateErrorJSON:
      properties:
        message:
          type: string
          enum:
          - Validation failed
        details:
          properties: {}
          additionalProperties:
            additionalProperties: true
          type: object
      required:
      - message
      - details
      type: object
      additionalProperties: false
    UpdateNotificationBodyDefinition:
      properties:
        data:
          $ref: '#/components/schemas/NotificationUpdateFields'
        params:
          $ref: '#/components/schemas/NotificationQueryFields'
      required:
      - data
      - params
      type: object
    NotificationType:
      enum:
      - MESSAGE
      - DRAFT
      - CONTENT
      - APPLICATION
      - CONFIRMATION
      - FAILED_PAYMENT
      type: string
    NotificationUpdateFields:
      properties:
        windowIsClosed:
          type: boolean
        isUnread:
          type: boolean
      type: object
    EmailNotificationTimeframe:
      enum:
      - TWO_H
      - FOUR_H
      - DAILY
      type: string
  securitySchemes:
    apiKey:
      type: apiKey
      name: api-key
      in: header