• feat(notifications): show the reclaim deadline in the recipient's timezone (#4531)latest6Docsf7136632026-10-20 06:31

  Change detail

  6 changes across 6 operations

  AllBreakingWarningInfo

  • DELETE/v1/notification-channels/{id}
    • info

      added the required property data/timezone to the response with the 200 status

  • GET/v1/notification-channels/{id}
    • info

      added the required property data/timezone to the response with the 200 status

  • PATCH/v1/notification-channels/{id}
    • info

      added the required property data/timezone to the response with the 200 status

  • POST/v1/notification-channels/default
    • info

      added the new optional request property data/timezone

  • GET/v1/notification-channels
    • info

      added the required property data/items/timezone to the response with the 200 status

  • POST/v1/notification-channels
    • info

      added the required property data/timezone to the response with the 201 status

• fix(notification-channel): validate the default channel request body (#4372)5Docsed5f75c2026-10-13 16:54

  Change detail

  5 changes across 1 operation

  AllBreakingWarningInfo

  • POST/v1/notification-channels/default
    • info

      added the new optional header request parameter Authorization

    • info

      added the non-success response with the status 400

    • info

      added the non-success response with the status 401

    • info

      added the non-success response with the status 403

    • info

      added the non-success response with the status 500

• fix(deployment): keep blockchain wording out of the public api (#4025)no API changesDocsc52d12d2026-09-24 11:11
• feat(notifications): render call-to-action buttons in transactional emails (#3793)66Docse6329b22026-09-04 12:57

  Change detail

  12 changes across 5 operations

  AllBreakingWarningInfo

  • POST/v1/alerts
    • breaking

      removed subschema #1 subschema #2 from the data request property oneOf list

    • breaking

      added subschema #1 subschema #2 to the data response property oneOf list for the response status 201

    • info

      added subschema #1 subschema #2 to the data request property oneOf list

    • info

      removed subschema #1 subschema #2 from the data response property oneOf list for the response status 201

  • DELETE/v1/alerts/{id}
    • breaking

      added subschema #1 subschema #2 to the data response property oneOf list for the response status 200

    • info

      removed subschema #1 subschema #2 from the data response property oneOf list for the response status 200

  • GET/v1/alerts/{id}
    • breaking

      added subschema #1 subschema #2 to the data response property oneOf list for the response status 200

  View all changes (12)
• 1.0no API changesDocs2026-07-17 12:07
• refactor(api): standardize operationId naming and enforce via lint (#3167)6Docs431ab7e2026-05-12 12:07

  No leveled API changes in this revision.

• feat(dx): introduce @akashnetwork/openapi-sdk and console-api-types (#3146)11Docs371174c2026-05-07 10:32

  Change detail

  2 changes across 1 operation and 1 model

  AllBreakingWarningInfo

  • POST/v1/jobs/notification
    • breaking

      api path removed without deprecation

  • Models
    • info

      removed the schema NotificationJobDto

• feat(notifications): re-generates swagger and sdks51Docsd3aae182025-12-18 12:36
• feat: adds notification on start trial (#1818)117Docs1eb381a2025-08-19 04:28
• feat: adds creation of default notification channel on user login/registration (#1808)6Docsaa53ee62025-08-15 03:32
• feat(alert): implements deployment closed alert management based on chain events610Docscabd46a2025-07-15 07:42
• feat(notifications): improves alerts list and forms UI55Docsaa9223c2025-06-16 15:22
• feat(alert): authorizes deployment alerts by dseq+owner14Docs59d0a7c2025-06-12 12:12
• refactor(notification-channel): renames contact-point to notification-channel and alert statuses17320Docs4b0ef572025-06-09 11:15
• feat(alert): add list ui2Docsf30775c2025-06-09 07:48
• feat(alert): implements deployment alerts58Docs7fc89b32025-06-06 11:26
• feat(contact-point): fetches contact point on the backend for edit9Docs3d1b0e32025-06-02 13:51
• feat(alert): adds alerts name column56Docs5297d9f2025-06-02 13:07
• feat(contact-point): implements list endpoint and auth1220Docs0f111152025-05-22 19:12
• feat(contact-point): implements unleash feature flagging and contact creation ui14633Docs6ad02ce2025-05-20 19:57

Revisions go back to the API's first capture.