From 8ca0fec260b44c1dc47b66d930b4d48df4a18e34 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Wed, 29 May 2019 20:58:34 -0400 Subject: [PATCH] Updated Development_API (markdown) --- Development_API.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/Development_API.md b/Development_API.md index 8972ebd..4bfd220 100644 --- a/Development_API.md +++ b/Development_API.md @@ -229,11 +229,27 @@ The output will look like: "... etc, ..." - ] + ], + "details": { + "templates": { + ... + }, + "tokens": { + ... + }, + "args": { + ... + }, + "kwargs": { + ... + }, + }, } ``` The idea behind the **details()** function is that it allows developers to pass details back through their program letting their users know what notifications are supported. Thus as this library deprecates and introduces new notification services, calling front end applications (built around the **details()** function) can automatically serve this information back to their user base. +More detailed information about this object can be found [[here|Development_Apprise_Details]]. + ## The Apprise Asset Object The apprise object allows you to customize your alarms by offering it different images, different sources and different themes. Different notification services support different ways of passing images into it (and some don't support images at all). Apprise offers a way of supporting both local and hosted images and looks after passing the correct one to the correct service (when requested).