Search the Omeda Knowledge Base

< All Topics

Email Deployment Unschedule


The Deployment Unschedule API provides the ability to unschedule a deployment, perhaps to allow further editing. A deployment can be unscheduled anytime before the user-defined deployment date. A deployment that is unscheduled will not be sent until a new Deployment Schedule Api call is made.

The Deployment Unschedule API should not be confused with the Deployment Cancel Api. A Deployment Cancel Api call cancels a deployment and prevents any further editing of the deployment.

An HTTP POST request is used when scheduling a deployment to send.

Base Resource URI

For Production, use:{brandAbbreviation}/omail/deployment/unschedule/*

For Testing, use:{brandAbbreviation}/omail/deployment/unschedule/*

brandAbbreviation is the abbreviation for the brand to which the data is being posted.

Technical Requirements

The HTTP header must contain the following elements: x-omeda-appid a unique id provided to you by Omeda to access your data. The request will fail without a valid id. content-type a content type supported by this resource. See Supported Content Types for more details. If omitted, the default content type is application/json.

Supported Content Types

If omitted, the default content type is application/json. JSON application/json

JSON is the preferred data exchange format, because it is lightweight and, in most cases, faster to process and utilizes less bandwidth. There are many available open-source JSON libraries available. See for details.

Supported HTTP Methods

There is one HTTP method supported: POST See W3C’s POST specs for details.

POST method is used when assigning a list to a deployment split that does not have an existing list attached.

Field Definition

The following tables describe the hierarchical data elements.

List Elements

Attribute NameRequired?Data TypeDescription
UserIdrequiredstringUserId of the omail account authorized for this deployment. This is generally the ‘OwnerUserId’ specified in the Deployment Api
TrackIdrequiredstringTrackId is the unique identifier for the deployment.

POST JSON Request Example: When unscheduling a deployment

    "UserId" : "omailAccount1",
    "TrackId": "FOO0102003002"


Response Examples

Responses possible: a successful POST (200 OK Status) or a failed POST (400 Bad Request/403 Forbidden/404 Not Found/405 Method Not Allowed Statuses). See W3C’s Status Codes.

Successful Submission

A successful submission will unschedule the deployment. The deployment will no longer be queued to send and can be edited further.

JSON Example

      "SubmissionId" : "C95AE90C-BEC6-41F2-91E2-2BA9168D1D1E",

Failed Submission

Potential errors:

The value '{stringField}' for field '{fieldName}' exceeded a max length of {maximumAllowed}.
The field '{fieldName}' is required.
Deployment '{trackId}' is not currently scheduled.
Deployment '{trackId}' was sent on {sendDate}.
Deployment '{trackId}' has been previously cancelled.
User '{userName}' is not authorized to unchedule this deployment.

A failed request will return a unique submissionId that can be used as needed. A failed submission may be due to several factors:

400 Bad RequestTypically, this error occurs when the request does not follow the specifications.
403 ForbiddenTypically, this error occurs when the credentials are erroneous. Potentially, an incorrect x-omeda-appid or a UserId that is not authorized to edit the specified deployment.
404 Not FoundTypically, this error occurs with a malformed URL or the resource that is searched for is not found. This can occur if a TrackId submitted is not found in our system.
405 Method Not AllowedTypically, this error occurs when the resource accessed is not allowed by the HTTP Method utilized. Make sure you employ the appropriate HTTP Method (POST) for this request.

This is not an exhaustive list of errors, but common ones. If an error occurs repeatedly, please contact your Omeda representative.

JSON Example

  "Errors" : [
      Error": "'TrackId' is a required field." 
      "Error": "User 'omailaccount1' is not authorized to edit this deployment."
  "SubmissionId" : "C95AE90C-BEC6-41F2-91E2-2BA9168D1D1F"
Table of Contents
Scroll to Top