Global Email V3:Request: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 103: | Line 103: | ||
|- | |- | ||
|Premium||Also known as real time mode. Perform real time, live validation of email addresses. | |Premium||Also known as real time mode. Perform real time, live validation of email addresses. | ||
|} | |} | ||
Revision as of 15:16, 21 September 2016
A request consists of a protocol to make a call to the service, detailing desired elements. The minimum required elements in a request are your Customer ID and at least one input email address.
Global Email supports JSON, JSONP, REST, SOAP, and XML protocols.
Field Names
This is a list of the request field names and their protocol naming conventions.
Field Name | Level | REST Abbreviation | JSON |
---|---|---|---|
Transmission Reference | Request | t | TransmissionReference |
Customer ID | Request | id | CustomerID |
Options | Request | opt | Options |
Record ID | Record | RecordID | |
Record | |||
Format | Request | format | Format |
Request Elements
The following elements set the basic options for each request. These apply to the entire request, not the individual records.
Transmission Reference
- Optional.
- This is a string value that serves as a unique identifier for this set of records. It is returned as sent.
Protocol Syntax JSON, JSONP “TransmissionReference”:”string" REST ?t = {string} SOAP <urn:TransmissionReference>?</urn:TransmissionReference> XML <TransmissionReference>string</TransmissionReference>
Customer ID
- Required.
- This is a string value containing the identification number issued to the customer by Melissa Data for Global Email.
- If this element is absent, the Web Service will return an error. To receive a customer ID, please contact your Melissa Data sales representative at 1-800-MELISSA.
Protocol Syntax JSON, JSONP "CustomerID”:”string” REST &id = {string} SOAP <urn:CustomerID>?</urn:CustomerID> XML <CustomerID>string</CustomerID>
Options
- Optional.
- This is a string value containing the options set by the user.
Protocol Syntax JSON, JSONP "Options”:”string” REST ?opt = {string} SOAP <urn:Options>?</urn:Options> XML <Options>string</Options>
- List options in the following format, with multiple options delimited with a ",".
<OptionName>:<Parameter>,<OptionName>:<Parameter>
VerifyMailBox
- VerifyMailBox validates email mailbox.
Option Name Parameter Description VerifyMailBox Express Default. Also known as fast mode. Quickly validates against database of known email addresses. Premium Also known as real time mode. Perform real time, live validation of email addresses.
DomainCorrection
- DomainCorrection turns on fuzzy correction on suspected email domains typos.
Option Name Parameter Description DomainCorrection On Default. Activates fuzzy email domain correction if the domain is a suspected typo. Off No email domain correction.
Request Record Elements
JSON will only contain the Records element.
Protocol | Definition |
---|---|
JSON, JSONP | Each email will be contained within [{}] under the Records element. |
REST | The REST interface only allows a single record per request. |
SOAP | |
XML |
RecordID
- Optional.
- This is a string value containing a unique identifier for the current record. Use this to match the record submitted with the record returned. It will return what is inputted.
Protocol Syntax JSON “RecordID”:”string” SOAP <urn:RecordID>?</urn:RecordID> XML <RecordID>string</RecordID>
- Required.
- The email to be verified
Protocol Syntax JSON, JSONP “Email”:”string” REST &email = {string} SOAP <urn:Email>?</urn:Email> XML <Email>string</Email>
Format
- Optional.
- The desired format of the response.
Protocol Syntax JSON, JSONP “Format”:”string” REST &format = {string} SOAP <urn:Format>?</urn:Format> XML <Format>string</Format>