Summary This API provides capabilities to create many Behaviors defined for a given brand to multiple customers. For example, TODO. General Technical Requirements The following technical requirements apply to all requests for this API. HTTP Headers The HTTP header must contain the following elements: x-omeda-appid a unique id provided to you by Omeda to access […]
Assign Behavior Bulk Read More »
Summary The Transaction Lookup service is used to check on the submission status of a particular POST submission from DataQueue. Please note that the data submitted to the queue will not necessarily be kept available indefinitely. Base Resource URI In Production, use: https://ows.omeda.com/webservices/rest/brand/{brandAbbreviation}/transaction/{transactionId}/* In Testing, use: https://ows.omedastaging.com/webservices/rest/brand/{brandAbbreviation}/transaction/{transactionId}/* brandAbbreviationidentifies the brand, typically a short alphanumeric codetransactionIdthe
Transaction Lookup Read More »
Summary This API provides the ability to post a complete set of customer identity, contact, and demographic information along with order (paid or controlled) information for data processing (insert/update). Note that this service deposits data into a queue, it does not process data immediately. Back end processing of the data happens through a decoupled processing layer
Save Customer and Order Paid Read More »
Summary This API provides the ability to post a complete set of customer identity, contact, and demographic information along with order information for data processing (insert/update). Note that this service deposits data into a queue, it does not process data immediately. Back end processing of the data happens through a decoupled processing layer and depends on
Save Customer and Order Read More »
Summary This API provides capabilities to retrieve the merge history for the requested Customer Id. If the customer has been merged into another customer or deactivated an error message will be returned. (Please see failure section for more details) General Technical Requirements The following technical requirements apply to all requests for this API. Base Resource
Customer Merge History Lookup Read More »
Summary This API provides the ability look up customers using First Name (or initial), Last Name, Country and an Optional Postal Code. The response will include a list of customer records including the Customer Id(s) and the Customer Lookup URL(s). General Technical Requirements The following technical requirements apply to all requests for this API. Base
Customer Lookup By Name and Country Read More »
Summary This API provides the ability look up a Customer’s External Ids by the Customer Id. General Technical Requirements The following technical requirements apply to all requests for this API. Base Resource URI Production: https://ows.omeda.com/webservices/rest/brand/{brandAbbreviation}/customer/{customerId}/externalid/* Testing: https://ows.omedastaging.com/webservices/rest/brand/{brandAbbreviation}/customer/{customerId}/externalid/* brandAbbreviation is the abbreviation for the brand customerId is the internal customer id (encrypted customer id may also be
External ID Lookup By Customer Id Read More »
Summary This service returns all subscription information stored for all customers with the given Email Address and optional Product Id. Note, this includes both current subscription and deactivated subscriptions (see below to determine the differences). Note General Technical Requirements The following technical requirements apply to all requests for this API. Base Resource URI The following lookup
Subscription Lookup By Email Read More »
Summary This service returns all available subscription information stored for a given Customer Id and optional Product Id. Note, this includes both current subscription and deactivated subscriptions (see below to determine the differences). Note This service only returns Product types that create a Subscription. Currently only Magazine (productType=1) and Newsletter (productType=2) type products create Customer Subscriptions
Subscription Lookup By Customer Id Read More »
Summary This service returns all available customer demographics stored for a given customer by using the Customer ID. General Technical Requirements The following technical requirements apply to all requests for this API. Base Resource URI Production: https://ows.omeda.com/webservices/rest/brand/{brandAbbreviation}/customer/{customerId}/demographic/* Testing: https://ows.omedastaging.com/webservices/rest/brand/{brandAbbreviation}/customer/{customerId}/demographic/* brandAbbreviation is the abbreviation for the brand customerId is the internal customer id (encrypted customer id may
Demographic Lookup By Customer Id Read More »