Module beeswax::resource

A collection of resources to use with the api

Re-exports

pub use account_alert::AccountAlert;

pub use advertiser::Advertiser;

pub use authenticate::Authenticate;

pub use campaign::Campaign;

pub use creative::Creative;

pub use creative_line_item::CreativeLineItem;

pub use line_item::LineItem;

pub use view::View;

pub use view_list::ViewList;

Modules

account_alert	Determine which emails or Slack channels to forward to when receiving an Alert
advertiser	Every Campaign, Line Item, and Creatives belongs to an Advertiser. Advertisers are typically the entity paying the bills for the ads that run. See: Advertisers, Campaigns, Line_Items, Creatives.
authenticate	The authenticate API method allows you to login to Buzz, change your password and logout
campaign	A Campaign object defines the overall budget and timing for one or more Line Items. Campaigns belong to a single Advertisers.
common
creative	A Creative object defines the payload to be delivered to the end user. Creatives belong to Advertisers and are associated with Line Items. The Creative object has interactions with Creative Templates and Creative Assets / Video Assets as described in Creatives, Creative Assets, Templates, Rules.
creative_line_item	A Creative Line Item object associates a Creative with a Line Item. A Line Item cannot be active until it has one or more active Creatives associated through this method.
line_item	A Line Item object defines the objectives, budget and timing for a portion of a Campaign. Line Items belong to a single Campaign, may be associated with one or more Creatives using the Creative Line Item Association, and are associated with a single Targeting Template.
view	The View API method allows you to flexibly GET data from the Buzz system. It is especially useful for querying static tables to discover ad types. acceptable mime types, or other lookup fields. Views must be created by the Buzz administrator. Only GET requests are supported.
view_list	The View List API method allows you to GET metadata about how a View and the fields within that View should be displayed in a UI. There is no write API for this data, it must be manually populated in SQL by an administrator. The primary use case for this API call is to display the data from a view in a user interface. Only GET requests are supported.

Structs

Id
ResponseId
ResponseResource

Enums

AnyResource

Traits

Create
Delete
FromAnyResource
Read
Resource