Information payload on the XML

The following information from the extended RSS tags looking for the Acast namespace (xmlns:acast="https://schema.acast.com/1.0/") :

XML tags

<acast:signature>

At the channel level, contains the information to decrypt the payloads of the rest of the values:

<acast:signature key="EXAMPLE" algorithm="aes-256-cbc">
<![CDATA[ quRO51a5m/mAho8azGcwFw== ]]>
</acast:signature>

key = corresponds to the public key that matches the private secret used as a passphrase on the encryption.

algorithm - the algorithm used for encrypting the data (should support any algorithm supported by node crypt functions).

The payload of the signature object is a base64 representation of the binary initialization vector. It’s both used as a IV for the aes encryption and used as a salt to prime the secret passphrase for encoding/decoding.

<acast:settings>

This can be both at the channel level and the item level. It’s encoded as base64 utf-8 string, either of a json stringified or the json string encrypted with the information provided in the signature object.

<acast:settings>
<![CDATA[
YK3SZFrO9R7G31pqjHL9wvTu79QnCIImLtbDiCi5sPac/5CuUkGVC3ZUIvgnTzwByScZVL1wehUMVnrW4RZEuKwNEgOiR6H2Qh+AfFLPxA/MdbcskWexMTTUbaB1vzMlgQMcD5YqtSzApXqXcVT3z0iKu8HEXGbAvRm6r4vxld1FhhYXaS6DKTCBaVMP+mt+HGENxrTF1EwN4zVhEcDaNds8L9oQR9QHBAaL1HAIBnSQkAEheNuD1D6wI34X2ztfExfPGgtgLyjw/2ELVe71A2bKPENRQCYlx5pipP3IPziUX5UGDPdOVwM/yBMkoXHQ2hagpcrT8t+1bvf7xFLgId+eNOLpFjJEi3v5vOsKR1CPluQyO0bqvj9NcPrxv6uF6fY/SWClbXHxLiRCCST1Kzm/DxiLI9jMziPVPE6txSiRVCH8WTP5l2GZelOH0tb41UFU7nDOPJaG2fIF3xk9ZAX+wHta0V61rLZHdSKdQsNgTXkUa3R+npBsiKDOOR2DYSAlSsF9w24h5E/UTVvuDMzicM8e4svmBqPE8Fjp26UNW9R81rONMSP3GTyBkFXXobRu68rQ63LgIMCrp+JDVFNs78t8cjRxyTuxbAPT80veGwNMiQuJgEwtcepsxeDlD6irfd1v3kzQ2lEyAFOOxWNN4keS8sXFImPaWVER5eh1VUrpzD2/ydSR+2UwMTLCTmKx/mLT+vpaIN6jjw4N60M7p77aicqoeJ0PwwdMzeyMJvdofpM69ZRR+oTvn3ZhPu1M8bLJpUxCqgEA5E/VYWZ6PKn3xLX6rtQs1M+/JSHoVG3/2H8LL6w0cxE5vP8TGeuAlb+YjNfTXsG4P4n0VgsR8I/wXXM+W4WosrbEW+2+kK2qi+STcad5oroFCSFdbVkQYmhyM7V611xeUU+ARfxwX1SheA6x+C8NQdO53rykxZsuZzzizi0qoST2IUdxZfaD8XojqpPzQjgZ6jLWeghCTc5WnwmgJAvOLKvRw4cqSVMbF/BeOwEdRHUhUUGhxdE1/8G2x5HMNV2rQUsBNmMLAX/riH7Gp7JxcMYdxUgbeElHxy7brDWxOx4+vkbi86N5sLhHWAQtFXqJIrhhqhjWEz6Pm/zNiSHTM78rTrSA9jFKeIfunVQMxqK4vsFG+92+bWeAlrF4vEZyp3V206kKC+GFLaBgiaL6x699SD0=]]>
</acast:settings>



<acast:settings> at the Channel level (Show data)

At the channel (show) level, the settings object contains the base information for the show ad targeting, plus some default data for the episodes. Once decrypted and decoded, we expect the information to look like this (all values are optional):

{
defaults: {
"intro": "", // Optional intro audio to attach to the start of the episodes
"outro": "", // Optional outro audio to attach to the end of the episodes
"adInSound": "", // URL of an ad break in sting
"adOutSound": "", // URL of an ad break out sting
}
},

<acast:settings> at the Item level (Episode data)

At the item (episode) level, it contains the episode-level information: The ad positions and number of ads, plus the source URL (for non-Flex content).

{
mediaUrl: [url], // URL of the source of the episode, optional if using flex-prepend
intro: 'mp3_url', // Optional intro audio to attach to the start of the episode
outro: 'mp3_url', // Optional outro audio to attach to the end of the episode
adSettings: {
slots: [
{
type: 'spons', // 'spons' or 'ads'
placement: 'midroll', // ‘preroll’ or ‘midroll’ or ‘postroll’
start: 312, // Position of the slot in seconds
duration: 60, // Recommended duration per item to add to this slot
count: 3, // Max number of ads to insert in the slot
}
],...
}
}

Did this answer your question?