TD Bank

TD Bank Notifications API

Notifications API — retrieves alerts about significant changes on the TD/Akoya network, including planned/unplanned maintenance outages and consent events (revoked or modified consumer consents). Lets data recipients react to consent revocations and platform incidents in near real time.

TD Bank Notifications API is one of 14 APIs that TD Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 machine-runnable capability that can be deployed as REST, MCP, or Agent Skill surfaces via Naftiko.

Tagged areas include Notifications, Akoya, and Open Banking. The published artifact set on APIs.io includes API documentation, an OpenAPI specification, and 1 Naftiko capability spec.

GitHub OpenAPI

Documentation

📖
Documentation
https://docs.pat.openbanking.amcb.developer.td.com/guides/about-our-apis-hdi

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/td-bank/refs/heads/main/openapi/td-bank-notifications-api-openapi.yml

Other Resources

🔗
NaftikoCapability
https://raw.githubusercontent.com/api-evangelist/td-bank/refs/heads/main/capabilities/notifications-notifications.yaml

OpenAPI Specification

td-bank-notifications-api-openapi.yml Raw ↑ 
openapi: 3.1.0
info:
  title: TD Bank Notifications API
  description: >-
    Notifications API. Retrieves alerts about significant changes on the
    TD/Akoya network — planned and unplanned maintenance outages, plus
    consent events covering revoked or modified consumer consents. Lets
    data recipients react to consent revocations and platform incidents
    in near real time.
  version: '1.0.0'
  contact:
    name: TD Open Banking Developer Support
    url: https://developer.td.com
externalDocs:
  description: TD Open Banking — About Our APIs
  url: https://docs.pat.openbanking.amcb.developer.td.com/guides/about-our-apis-hdi
servers:
  - url: https://api.openbanking.amcb.developer.td.com/notifications/v1
    description: Production
tags:
  - name: Notifications
security:
  - serviceToken: []
paths:
  /notifications:
    get:
      operationId: listNotifications
      summary: List Notifications
      tags: [Notifications]
      parameters:
        - name: category
          in: query
          required: false
          schema:
            type: string
            enum: [maintenance, consent_revoked, consent_changed]
        - name: since
          in: query
          required: false
          schema: { type: string, format: date-time }
      responses:
        '200':
          description: Notifications
          content:
            application/json:
              schema:
                type: object
                properties:
                  notifications:
                    type: array
                    items: { $ref: '#/components/schemas/Notification' }
  /notifications/{notificationId}:
    get:
      operationId: getNotification
      summary: Get Notification
      tags: [Notifications]
      parameters:
        - name: notificationId
          in: path
          required: true
          schema: { type: string }
      responses:
        '200':
          description: Notification detail
components:
  securitySchemes:
    serviceToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
  schemas:
    Notification:
      type: object
      required: [notificationId, category]
      properties:
        notificationId: { type: string }
        category: { type: string }
        severity: { type: string }
        title: { type: string }
        description: { type: string }
        affectedResources:
          type: array
          items: { type: string }
        consentId: { type: string }
        createdAt: { type: string, format: date-time }