Reminders | Billomat Accounting API - Create Online Invoices

List all payment reminders

GET /api/reminders

&lt;!--?xml version="1.0" encoding="UTF-8"?--&gt;
&lt;reminders type="array" page="1" per_page="100" total="2"&gt;
    &lt;reminder&gt;
        ...
    &lt;/reminder&gt;
    &lt;reminder&gt;
        ...
    &lt;/reminder&gt;
&lt;/reminders&gt;

You can filter the result by parameters:

GET /api/reminders?invoice_number=RE123

Lists all reminders with “RE123” in the invoice number. Upper and lower case are ignored.
The following filter parameters are available:

Parameter	Description
client_id	ID of the client
contact_id	ID of the contact
invoice_number	Number of the related invoice
status	Status (DRAFT, OPEN, PAID, OVERDUE, CANCELED). More than one statuses could be given as a comma separated list. Theses statuses will be logically OR-connected.
from	Only show invoices since this date (format YYYY-MM-DD)
to	Only show invoices up to this date (format YYYY-MM-DD)
subject	Free text search in subject
label	Free text search in label text
intro	Free text search in introductory text
note	Free text search in explanatory notes
tags	Comma separated list of tags
article_id	ID of an article

Get a single reminder

GET /api/reminders/{id}

&lt;!--?xml version="1.0" encoding="UTF-8"?--&gt;
&lt;reminder&gt;
    &lt;id type="integer"&gt;1&lt;/id&gt;
    &lt;created type="datetime"&gt;2007-12-13T12:12:00+01:00&lt;/created&gt;
    &lt;status&gt;OPEN&lt;/status&gt;
    &lt;invoice_id&gt;7&lt;/invoice_id&gt;
    &lt;contact_id type="integer"&gt;&lt;/contact_id&gt;
    &lt;reminder_text_id type="integer"&gt;123&lt;/reminder_text_id&gt;
    &lt;reminder_level type="integer"&gt;1&lt;/reminder_level&gt;
    &lt;reminder_level_name&gt;Erste Stufe&lt;/reminder_level_name&gt;
    &lt;date type="date"&gt;2009-10-01&lt;/date&gt;
    &lt;label&gt;project 123&lt;/label&gt;
    &lt;subject&gt;Friendly reminder&lt;/subject&gt;
    &lt;intro&gt;Surely you've only forgotten to pay...&lt;/intro&gt;
    &lt;note&gt;Please pay to....&lt;/note&gt;
    &lt;due_date type="date"&gt;2009-10-31&lt;/due_date&gt;
    &lt;due_days&gt;30&lt;/due_days&gt;
    &lt;total_gross type="float"&gt;119&lt;/total_gross&gt;
    &lt;paid_amount type="float"&gt;0&lt;/paid_amount&gt;
    &lt;open_amount type="float"&gt;119&lt;/open_amount&gt;
    &lt;is_old&gt;0&lt;/is_old&gt;
    &lt;customerportal_url&gt;https://mybillomatid.billomat.net/customerportal/reminders/show/entityId/123?hash=123456789aabbcc&lt;/customerportal_url&gt;
    &lt;template_id&gt;&lt;/template_id&gt;
&lt;/reminder&gt;

status can have the following values::
– DRAFT
– OPEN
– OVERDUE
– PAID
– CANCELED
Reminder items can be accessed separately.

Create reminder

POST /api/reminders

XML element	Description	Type	Default value	Mandatory
invoice_id	ID of the overdue invoice	INT		yes
contact_id	ID of the contact	INT
address	the address	ALNUM	Address from invoice
date	Date of the reminder	DATE	today
due_date	Due date of the reminder	DATE	date + due days taken from the settings
subject	Subject	ALNUM	Subject of the next dunning level (if available)
label	Label text to describe the project	ALNUM
intro	Introductory text	ALNUM	Introductory text of the next dunning level (if available)
note	Explanatory notes	ALNUM	Explanatory notes of the next dunning level (if available)
template_id	The ID of the template to be used to complete the reminder.	INT	ID of the default template

status at creation is always DRAFT.
Reminder items (reminder-items) can be specified directly at creation. Please find a documentation of the XML elements at Create reminder items, but the XML element reminder_id need not be specified with.

&lt;reminder&gt;
    &lt;invoice_id&gt;56610&lt;/invoice_id&gt;
    &lt;reminder_level type="integer"&gt;1&lt;/reminder_level&gt;
    &lt;date type="date"&gt;2009-10-14&lt;/date&gt;
    &lt;subject&gt;Friendly reminder&lt;/subject&gt;
    &lt;intro&gt;Surely you've only forgotten to pay...&lt;/intro&gt;
    &lt;note&gt;Please pay to....&lt;/note&gt;
    &lt;due_date type="date"&gt;2011-04-12&lt;/due_date&gt;
    &lt;reminder-items&gt;
         &lt;reminder-item&gt;
            &lt;unit&gt;&lt;/unit&gt;
            &lt;unit_price&gt;2&lt;/unit_price&gt;
            &lt;quantity&gt;1&lt;/quantity&gt;
            &lt;title&gt;Late payment interest&lt;/title&gt;
        &lt;/reminder-item&gt;
        &lt;reminder-item&gt;
            &lt;unit&gt;&lt;/unit&gt;
            &lt;unit_price&gt;10&lt;/unit_price&gt;
            &lt;quantity&gt;1&lt;/quantity&gt;
            &lt;title&gt;Overdue fines&lt;/title&gt;
        &lt;/reminder-item&gt;
    &lt;/reminder-items&gt;
&lt;/reminder&gt;

&lt;reminder&gt;
&lt;id type="integer"&gt;9&lt;/id&gt;
&lt;created type="datetime"&gt;2011-02-11T11:33:05+01:00&lt;/created&gt;
&lt;status&gt;DRAFT&lt;/status&gt;
&lt;invoice_id type="integer"&gt;56610&lt;/invoice_id&gt;
&lt;reminder_text_id type="integer"&gt;
&lt;reminder_level type="integer"&gt;1&lt;/reminder_level&gt;
&lt;reminder_level_name&gt;
&lt;date type="date"&gt;2009-10-14&lt;/date&gt;
&lt;subject&gt;Friendly reminder&lt;/subject&gt;
...
&lt;/reminder_level_name&gt;&lt;/reminder_text_id&gt;&lt;/reminder&gt;

Edit reminder

PUT /api/reminders/{id}

A reminder can basically be edited in draft status (DRAFT) only.
Reminder items could not be edited at the reminder. Please use the appropriate resource instead.

&lt;reminder&gt;
    &lt;date&gt;2009-10-13&lt;/date&gt;
&lt;/reminder&gt;

Delete reminder

DELETE /api/reminders/{id}

Deletes a reminder with all documents (PDFs) and items.

Complete reminder

PUT /api/reminders/{id}/complete

Completes a reminder in the draft status (DRAFT). Here, the status of open (OPEN) or overdue (OVERDUE) is set and a PDF is generated and stored in the file system.

The optional parameter template_id determines which template is used to create a pdf.

If this parameter is not specified, the template specified at the reminder or the default template is used.

&lt;complete&gt;
    &lt;template_id&gt;123&lt;/template_id&gt;
&lt;/complete&gt;

Open pdf of a reminder

GET /api/reminders/{id}/pdf

At this point, the parameter format=pdf can also be used to open the PDF directly with MIME type “application/pdf”.
With the optional parameter type=print you can request the PDF without background. Note that the setting print_version must have been activated.

&lt;pdf&gt;
    &lt;id type="integer"&gt;4882&lt;/id&gt;
    &lt;created type="datetime"&gt;2009-09-02T12:04:15+02:00&lt;/created&gt;
    &lt;reminder_id type="integer"&gt;240&lt;/reminder_id&gt;
    &lt;filename&gt;reminder_123.pdf&lt;/filename&gt;
    &lt;mimetype&gt;application/pdf&lt;/mimetype&gt;
    &lt;filesize&gt;70137&lt;/filesize&gt;
    &lt;base64file&gt;{base64 encoded PDF}&lt;/base64file&gt;
&lt;/pdf&gt;

Updoad a digital signature for a given reminder

PUT /api/reminders/{id}/upload-signature

Updoads a digital signature for a given invoice.
The status of the reminder may not be DRAFT.

XML element	Description	Type	Default value	Mandatory
base64file	Base64 encoded PDF with digital signature	BASE64FILE		ja

Note: A (qualitfied) digital signature can NOT be created by the billomat[API] directly. We recommend that you use this function directly on the PixelLetter interface or another service

&lt;signature&gt;
    &lt;base64file&gt;{base64 encoded PDF}&lt;/base64file&gt;
&lt;/signature&gt;

Send reminder by e-mail

POST /api/reminders/{id}/email

XML element	Description	Type	Default value	Mandatory
email_template_id	ID of the e-mail template	INT
from	Sender	EMAIL	Default email from the settings
recipients	Recipients of the e-mail. There must be at least one xml node for “to”, “cc” and/or “bcc”.	XML node/EMAIL		ja
subject	Subject of the e-mail (may include placeholders)	ALNUM	Value taken from the (default) e-mail template
body	Text of the e-mail (may include placeholders)	ALNUM	Value taken from the (default) e-mail template
filename	Name of the PDF file (without .pdf)	ALNUM	invoice_{id}
attachments	Further files. Attachments can contain as many nodes on the “attachment” with the elements “filename”, “mimetype” and “base64file”.	XML node

&lt;email&gt;
    &lt;from&gt;info@billomat.com&lt;/from&gt;
    &lt;recipients&gt;
        &lt;to&gt;info@billomat.com&lt;/to&gt;
        &lt;cc&gt;mail@example.com&lt;/cc&gt;
    &lt;/recipients&gt;
    &lt;subject&gt;Reminder!&lt;/subject&gt;
    Dear sir or madam, ....
    &lt;filename&gt;reminder&lt;/filename&gt;
    &lt;attachments&gt;
        &lt;attachment&gt;
            &lt;filename&gt;drawing.pdf&lt;/filename&gt;
            &lt;mimetype&gt;application/pdf&lt;/mimetype&gt;
            &lt;base64file&gt;{base64 encoded file}&lt;/base64file&gt;
        &lt;/attachment&gt;
    &lt;/attachments&gt;
&lt;/email&gt;

Send reminder by mail

POST /api/reminders/{id}/mail

Sends a reminder by mail. Pixelletter has to be configured as add on for usage.

XML element	Description	Type	Default value
color	Determines whether to use color printing.	BOOL	0
duplex	Determines whether to use duplex printing.	BOOL	1
paper_weight	Determines the paper weight in grams. Possible values are 80 or 90.	INT	90
attachments	Further PDF files. Attachments can contain as many nodes on the “attachment” with the elements “filename”, “mimetype” and “base64file”.	XML node

&lt;mail&gt;
    &lt;color&gt;0&lt;/color&gt;
    &lt;duplex&gt;1&lt;/duplex&gt;
    &lt;paper_weight&gt;90&lt;/paper_weight&gt;
    &lt;attachments&gt;
        &lt;attachment&gt;
            &lt;filename&gt;drawing.pdf&lt;/filename&gt;
            &lt;mimetype&gt;application/pdf&lt;/mimetype&gt;
            &lt;base64file&gt;{base64 encoded file}&lt;/base64file&gt;
        &lt;/attachment&gt;
    &lt;/attachments&gt;
&lt;/mail&gt;

Cancel reminder

PUT /api/reminders/{id}/cancel

Undo cancellation

PUT /api/reminders/{id}/uncancel