Summary The Deployment Add Audience API provides the ability add a previously uploaded list of customers to a deployment (See Deployment Audience List FTP for information on uploading a list into the Omail system). Your list must have a unique column containing email addresses. The header for this column must be one of the following (not case […]
Email Deployment Add Audience Read More »
Summary The Clone Deployment Service API provides the ability to post deployment information to Omail. This information is used to clone existing Omail deployment. Deployment information is validated for basic information. An HTTP POST request is used to clone existing deployment. The TrackId of the deployment to clone must be included in the request JSON.
Email Deployment Clone Read More »
Summary The Deployment Service API provides the ability to post/put deployment information to Omail. This information is used to either create a new Omail deployment, or update an existing Omail deployment. Deployment information is validated for basic information. An HTTP POST request is used to create a new deployment. An HTTP PUT request is used
Summary Please contact your Omeda representative for FTP credentials. Deployment List FTP is the means by which deployment lists are made available in the Omail system. Lists are uploaded to a pre-configured, password-protected FTP folder. Lists should be placed in the appropriate brand level folder. FTP Work Flow: 1. User drops the audience list into
Email Deployment Audience List FTP Read More »
Summary The Deployment API allows our clients to send a single Omail email deployment. Please work with your Client Services Manager for the initial setup and access to this API. Base Resource URI For Production: https://ows.omeda.com/webservices/rest/brand/{brandAbbreviation}/omail/deployemails/* For Testing: https://ows.omedastaging.com/webservices/rest/brand/{brandAbbreviation}/omail/deployemails/* brandAbbreviationis the brand identifier for your brand or site Technical Requirements The HTTP header must contain
Email On Demand Send Read More »
Summary This service returns Opt In/Out information stored for a given customer. Base Resource URI Production: https://ows.omeda.com/webservices/rest/brand/{brandAbbreviation}/filter/email/{emailAddress}/* Testing: https://ows.omedastaging.com/webservices/rest/brand/{brandAbbreviation}/filter/email/{emailAddress}/* brandAbbreviation is the abbreviation for the brand emailAddress is the email address you are searching for Technical Requirements The HTTP header must contain the following elements: x-omeda-appid a unique id provided to you by Omeda to
Email Opt In/Out Lookup Read More »
Summary The OptOut Queue API allows our client to OptOut their subscribers or customers to their email deployments at the client, brand, and deployment type level. All 3 OptOut levels can be submitted in one OptOut Queue API call. Base Resource URI For Production, use: https://ows.omeda.com/webservices/rest/client/{clientAbbreviation}/optoutfilterqueue/* For Testing, use: https://ows.omedastaging.com/webservices/rest/client/{clientAbbreviation}/optoutfilterqueue/* clientAbbreviation is the abbreviation for
Email Optout Queue Read More »
Summary The OptIn Queue API allows our client to OptIn their subscribers or customers to their email deployments at the client, brand, and deployment type level. All 3 OptIn levels can be submitted in one OptIn Queue API call. Base Resource URI For Production, use: https://ows.omeda.com/webservices/rest/client/{clientAbbreviation}/optinfilterqueue/* For Testing, use: https://ows.omedastaging.com/webservices/rest/client/{clientAbbreviation}/optinfilterqueue/* clientAbbreviation is the abbreviation for
Overview Our Campaign Tool allows you to perform 4 key functions for your campaigns: A promo code is required in every product order. Promo codes consist of much information such as the promo channel, product and pricing, and the offer details. You can then analyze how the promo channels and pricing affected your sales through
Campaign Tool – Overview Read More »
To create an automated ACS notifications follow these step by step instructions: Identify the correct deployment type – verify in Email Builder defaults that the correct person is selected as the final approver at the deployment type level. Verify the correct testers and seednames in Email Builder defaults at the deployment type level. Client must
Email – Automated ACS Notifications Read More »