Benötigen Sie Hilfe?
-
Maileon Anleitungen
-
-
- Bald verfügbar
-
- Bald verfügbar
-
-
-
-
- Bald verfügbar
-
- Bald verfügbar
-
- Bald verfügbar
-
-
-
- Bald verfügbar
-
- Bald verfügbar
-
- Bald verfügbar
-
-
-
-
- Bald verfügbar
-
-
-
FAQs
-
-
- Ich kann mir meine Export-Datei nicht wie gewünscht darstellen lassen. Was kann ich dagegen tun?
- Ich will Kontakte über die Schnittstelle hinzufügen aber der Kontakt taucht nicht in Maileon auf.
- Kann man gelöschte Abmelder wiederherstellen?
- Was ist eine „Permission“ und welche Permissionsarten gibt es?
- Wie kann ich Kontakt nach erfolgter Abmeldung wieder dem Kundenbestand hinzufügen?
- Wie lange darf ein Anbieter darauf warten, bis der Newsletter-Interessent seine eingetragene E-Mail-Adresse per Link-Klick bestätigt (Double Opt-In)?
- Wie lange dürfen unbestätigte Newsletter-Anmelder in meinem Kontaktbestand gespeichert werden?
- Wie werden Kundendaten in Maileon gesichert/ verschlüsselt?
- Wieso werden mir nicht alle Abmelder meines Kontos angezeigt?
- Wo kann ich die Abmelder meiner Newsletter einsehen?
- Wo kann ich einstellen, wie lange ich Abmelder sehe?
- Wo kann ich weitere Benutzer anlegen?
-
- Ich finde es mühsam feste Elemente, wie das Impressum, im Template immer in allen Mailings einzeln anzupassen. Gibt es eine bessere Möglichkeit?
- Kann ich auch eigene Schriftarten verwenden?
- Kann ich einen Countdown in meinen Newsletter einbauen?
- Warum zeigt mein Reporting bei Öffner und Klicker fast identische Zahlen an?
- Wie hinterlege ich einen Ref-Code?
-
- Kann man Absender/Antwort E-Mails schon vorher anlegen und diese immer verwenden?
- Kann man beim Versand aus den ausgewählten Verteilern noch manuell Personen für diesen Versand ausschließen?
- Kann man einen geplanten Versand noch einmal bearbeiten?
- Was ist das Einzelnutzer-Tracking und welche Tracking-Methoden gibt es?
- Was ist der Unterschied zwischen Absender-Alias und Empfänger-Alias?
- Was ist die Werbedruckkontrolle und wo kann ich diese anpassen?
- Wie verwende ich BIMI in meinen E-Mailings?
- Wieso ist meine 1. Welle in der Versandstreckung immer die Größte?
- Wo erscheint der Vorschautext?
-
-
- Bietet Maileon Rabatt für Non Profit Organisationen?
- Gibt es Ansprechpartner für Vertriebsfragen?
- Kann ich Maileon testen, bevor ich mich für das Tool entscheide?
- Muss ich direkt meine Zahlungsdaten hinterlegen?
- Was passiert, wenn ich die Limits meines Paketes überschreite?
- Welche Zahlungsmöglichkeiten werden angeboten?
- Wie gestaltet sich die Vertragslaufzeit?
- Wie hoch ist die Einrichtungsgebühr?
- Wie kann ich mein Maileon-Paket ändern?
-
- Bald verfügbar
-
-
Grundlagen
-
Für Entwickler
-
-
- Adding Unsubscription Reason to Already Unsubscribed Contact
- Contacts
- Count Active Contacts By Filter ID
- Count Contacts By Filter ID
- Create Contact
- Create Contact (JSON)
- Create Contact by External ID
- Create Contact by External ID (JSON)
- Create Contact Preference
- Create Contact Preference Category
- Create Custom Field
- Custom Contact Fields
- Delete All Contacts
- Delete Contact By Maileon ID
- Delete Contact Preference
- Delete Contact Preference Category
- Delete Contacts By Email
- Delete Contacts By External ID
- Delete Custom Field
- Delete Custom Field Values
- Delete Standard Field Values
- Delete Unsubscription-Marker
- Get Blocked Contacts
- Get Contact By Email
- Get Contact By Maileon ID
- Get Contact Preference
- Get Contact Preference Categories
- Get Contact Preference Category by Name
- Get Contacts
- Get Contacts By Email
- Get Contacts By External Id
- Get Contacts By Filter Id
- Get Count Contacts
- Get Custom Fields
- Get Preferences of Contact Preferences Category
- Get Unsubscription-Marker
- Rename Custom Field
- Set Unsubscription-Marker
- Standard Contact Fields
- Synchronize Contacts
- Synchronize Contacts Error Codes
- Unsubscribe Contact By Maileon Id
- Unsubscribe Contacts By Email
- Unsubscribe Contacts by External Id
- Update Contact By Email
- Update Contact By External ID
- Update Contact By Maileon ID
- Update Contact Preference
- Update Contact Preference Category
- Alle Artikel anzeigen ( 34 ) Artikel zusammenklappen
-
- Add Mailing Blacklist to Mailing
- Copy Mailing
- Create Dispatching
- Create Mailing
- Delete Mailing
- Delete Mailing Blacklist from Mailing
- Delete Trigger
- Get CMS2 Mailing As Zip
- Get Dispatching
- Get limit on number of contacts
- Get Mailing Archive URL
- Get Mailing Blacklists for Mailing
- Get Mailing ID By Name
- Get Mailing Report URL
- Get Mailings By Creator Name
- Get Mailings By Keywords
- Get Mailings By Schedule Time
- Get Mailings By States
- Get Mailings By Subject
- Get Mailings By Types
- Get Preview Text
- Get Template
- Get Templates for CMS2
- Get The Reply-To Address
- Mailing – Add Attachment
- Mailing – Add Custom Mailing Properties
- Mailing – Copy Attachments
- Mailing – Create Schedule
- Mailing – Delete Attachment
- Mailing – Delete Attachments
- Mailing – Delete Schedule
- Mailing – Disable QoS Checks
- Mailing – Enable Target Group Update
- Mailing – Fill RSS SmartMailing Tags
- Mailing – Get “Ignore Permission” State
- Mailing – Get “Post Sendout Cleanup” State
- Mailing – Get Archival Duration
- Mailing – Get Attachment
- Mailing – Get Attachments
- Mailing – Get Count Attachments
- Mailing – Get DOI Mailing Key
- Mailing – Get HTML
- Mailing – Get List of Custom Mailing Properties
- Mailing – Get Locale
- Mailing – Get Mailing Domain
- Mailing – Get Max Attachment Size
- Mailing – Get Max Content Size
- Mailing – Get Name
- Mailing – Get Recipient Alias
- Mailing – Get result for Link Quality Check
- Mailing – Get result for Message Size Quality Check
- Mailing – Get result for Personalization Quality Check
- Mailing – Get result for Spam Quality Check
- Mailing – Get results for Approval Sendout Quality Check
- Mailing – Get results for Attention Quality Check
- Mailing – Get results for Bounce Quality Check
- Mailing – Get results for Display Quality Check
- Mailing – Get results for Image Quality Check
- Mailing – Get results for Test Mail Sendout
- Mailing – Get Schedule
- Mailing – Get Sender Address
- Mailing – Get Sender Alias
- Mailing – Get Speed Level
- Mailing – Get State
- Mailing – Get Subject
- Mailing – Get Tags
- Mailing – Get Target Group Id
- Mailing – Get Target Group Update status
- Mailing – Get Text
- Mailing – Get Tracking Duration
- Mailing – Get Tracking Strategy
- Mailing – Get Type
- Mailing – Is Sealed
- Mailing – Remove Custom Mailing Property
- Mailing – Send Approval Mail to Targetgroup
- Mailing – Send Now
- Mailing – Send Testmail to Single Emailaddress
- Mailing – Send Testmail to Targetgroup
- Mailing – Set “Ignore Permission” State
- Mailing – Set “Post Sendout Cleanup” State
- Mailing – Set DOI Mailing Key
- Mailing – Set Html
- Mailing – Set Locale
- Mailing – Set Name
- Mailing – Set Recipient Alias
- Mailing – Set Sender Address
- Mailing – Set Sender Alias
- Mailing – Set Speed Level
- Mailing – Set Subject
- Mailing – Set Tags
- Mailing – Set Target Group Id
- Mailing – Set Text
- Mailing – Set Tracking Strategy
- Mailing – Start Attention Quality Check
- Mailing – Start Bounce Quality Check
- Mailing – Start Image Quality Check
- Mailing – Start Link Quality Check
- Mailing – Start Message Size Quality Check
- Mailing – Start Personalization Quality Check
- Mailing – Start Quality Check
- Mailing – Update Custom Mailing Property
- Mailing – Update Schedule
- Reset Contents to Template
- Save CMS2 Mailing to Media Library
- Set limit on number of contacts before sending mailing
- Set Preview Text
- Set Template
- Set Template for CMS2 Mailing
- Set The Reply-To Address
- Alle Artikel anzeigen ( 94 ) Artikel zusammenklappen
Update Transaction Type
Sie sind hier:
Updates an existing transaction type with the given ID in the account.
Currently you can:
Currently you can:
- Add new attributes
- Change the name
- Change the description
- Change archival duration
The XML definition is identical to creating a transaction type: https://support.maileon.com/support/create-transaction-type/.
Please be aware: due to backwards compatibility of the types with regard to mailings or filters, you cannot change existing attributes or delete them. This means the definition in the update must at least contain all attributes of the original transaction type but might contain 0..n new attributes. However, regarding old attributes, only the name is evaluated, all other attributes are ignored and not prcessed or even updated.
Request
PUT https://api.maileon.com/1.0/transactions/types/:transactionTypeId
Media type: application/vnd.maileon.api+xml
XML specification
A transaction type definition contains a set of basic settings for the transaction type and a set of attributes which will contain the data later on. The following table defines the attributes for the transaction type itself:
Attribute | Required | Default | Description |
name | yes | The name of the transaction type. The name must start with a alphabetic character and may contain alphanumerical characters as well as “_” but no space. A name can be hierarchical, i.e. the different levels can be separated by a “.”, for example: “product.image.url”. The names between the “.”, i.e. the names on the different levels, may be up to 32 characters and the overall name may be up to 255 characters long. | |
description | no | If set, this value will be submitted as description for the transaction type. The length is limited to 1000 characters. | |
archivingDuration | no | not set (=infinite) | If set, this parameter specifies the number in days a transaction event will be saved in Maileon before being deleted. Please be aware that evaluations on transaction events are not possible after they have been deleted and for mailings containing content from the transaction events, rescue links will not render properly after deleting the events. |
attributes | yes | The list of attributes of the transaction type. The list may be empty. |
Any number of attributes can be specified. The following table explains the child elements of <attribute>:
Attribute | Required | Default | Description |
name | yes | The path of the JSON element that contains the attribute value. A dot („.“) is used as path separator. In the above example, the transaction content of an actual transaction might look like this:
{ "customer" : { "firstname" : "John", "Lastname" : "Doe" } ... } In this case, the firstname attribute would have to be called Note: the name itself is limited to 255 characters. |
|
description | no | IIf set, this value will be submitted as description for the attribute. The length is limited to 1000 characters. | |
type | yes | Defines the type of the attribute. Valid types are string (maximum length 1000 characters), double , float , integer , boolean , timestamp and json . A valid timestamp is a UNIX epoch timestamp represented as a long integer or a string that contains an iso-formatted date (e.g "2014-02-08" or "2014-02-08 14:34:20" ). json is a free-form JSON list element (“[...] “) that contains arbitrary JSON data and is up to 64000 bytes long. |
|
required | no | false | If this is set to true, any transactions that do not contain this attribute will be rejected by the method Create Transactions. |
<transaction_type> <name>Order</name> <archivingduration>7</archivingduration> <description>An order transaction</description> <attributes> <attribute> <name>customer.firstname</name> <description>The first name of the customer</description> <type>string</type> <required>true</required> </attribute> <attribute> <name>customer.lastname</name> <description>The last name of the customer</description> <type>string</type> <required>true</required> </attribute> <attribute> <name>date_valid</name> <type>timestamp</type> <required>true</required> </attribute> <attribute> <name>total</name> <type>double</type> <required>true</required> </attribute> <attribute> <name>discount</name> <type>float</type> <required>false</required> </attribute> <attribute> <name>num_products</name> <type>integer</type> <required>false</required> </attribute> <attribute> <name>order_content</name> <type>json</type> <required>true</required> </attribute> </attributes> </transaction_type>
Response
HTTP status code | Body Content | Description |
200 Ok | / <transaction_type_id>258</transaction_type_id> | transaction type successfully created |
400 Bad Request | If there was an error in the submitted body. In this case, an XML-form error message that explains the problem is produced. |
Inhaltsverzeichnis