GetMyMessages
Use this call to retrieve information about the threaded messages sent to a user's My Messages mailbox.
Depending on the detail level, the response can include message counts and headers, resolution status and flagged status, and message text.
Note:
GetMyMessages requires a DetailLevel in the request. Otherwise, an error is returned.
Note:
Alerts are treated as flagged messages with data returned in the Messages container. For high priority messages, the Flagged field has a
value of true. When the Flagged field is true,
it means the message is displayed with a flag in the seller's My Messages mailbox on eBay.
It is strongly recommended that the seller act on the message by the
specified date (or within 60 days, if not specified).
GetMyMessages returns more types of messages than GetMemberMessages. GetMemberMessages returns more nodes per message than GetMyMessages.
The output of GetMyMessages is available as a notification. See MyMessages Notification.
For maximum efficiency, make sure your application can first call GetMyMessages with
DetailLevel set to ReturnHeaders. Initially, do not specify any message ID. Your application should be able to cache the returned message ID values. Your application also should be able to create new My Messages requests (up to 10 cached message ID values per request).
Usage Details
With a detail level of ReturnHeaders or ReturnMessages, GetMyMessages only accepts 10 unique message ID values, per request.
Controlling the Volume of the Response
Depending on the activity of the user, GetMyMessages can return an overwhelming amount of data. To reduce the volume of the response, you can restrict the number of messages returned by adding different filters to your request:
- Filter by start and end time
- (Optional) Call GetMyMessages with DetailLevel set to
ReturnSummaryto obtain the counts for the new messages. - If total message counts are too high for your application to process (say, above 200), specify StartTime and EndTime values to return messages sent within a specific time range.
- Make additional GetMyMessages calls with different date ranges until you have retrieved all new messages.
- (Optional) Call GetMyMessages with DetailLevel set to
- Filter using detail levels
- (Optional) Call GetMyMessages with DetailLevel set to
ReturnSummaryto obtain the counts for the new messages. - Use a DetailLevel of ReturnHeaders to return MessageID values and cache them for future use.
- Keep calling GetMyMessages with a DetailLevel of ReturnMessages, and 10 MessageID values, until you have retrieved all messages.
For high-volume use, be careful when using ReturnHeaders without specifying MessageID values, because otherwise eBay returns all messages.
- (Optional) Call GetMyMessages with DetailLevel set to
- Filter using folder names
- (Optional) Call GetMyMessages with DetailLevel set to
ReturnSummaryto obtain the counts for the new messages. - If total message counts are too high for your application to process (say, above 200), you can specify a FolderID value to return only messages from the specified folder.
- Make additional GetMyMessages calls with different Folder ID values until you have retrieved all the new messages.
Note that if you set FolderID to
0(indicating the Inbox), the result often contains a large number of messages. If the number of messages is too large for your application to process (say, above 200), filter your the results using an additional method, perhaps another as described above. - (Optional) Call GetMyMessages with DetailLevel set to
See the Samples section for calls that use these filtering mechanisms.
This call returns the text of the messages embedded in HTML code. You can parse the content from the HTML, or you can pass along the code as-is, depending on your needs.
Optimizing Your Calls
To make the most of your GetMyMessages calls, make one call with DetailLevel set to ReturnHeaders, without including MessageID values. This will return a complete list of message headers with their corresponding message ID values. Cache these ID values and use them in a second call to GetMyMessages with DetailLevel set to ReturnMessages. Using this method, you can retrieve details of up to ten specific messages at a time.
Testing GetMyMessages
You can test GetMyMessages in the Sandbox.
Several API calls allow you to replenish your supply of messages in the Sandbox. See Exchange messages for information on adding new messages. You can contact Developer Support to obtain further testing information.
Related Information
See also the reference documentation for this call:
- GetMemberMessages - Retrieves a list of the messages buyers have posted about your active item listings.
Input
See also Samples.
The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).
See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are (or soon will be) non-operational.
The XML prototype does not include requester credentials. This is a documentation limitation only (see Standard Requester Credentials for Making Calls).
<?xml version="1.0" encoding="utf-8"?> <GetMyMessagesRequest xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Input Fields --> <EndTime> dateTime </EndTime> <ExternalMessageIDs> MyMessagesExternalMessageIDArrayType <ExternalMessageID> MyMessagesExternalMessageIDType (string) </ExternalMessageID> <!-- ... more ExternalMessageID values allowed here ... --> </ExternalMessageIDs> <FolderID> long </FolderID> <IncludeHighPriorityMessageOnly> boolean </IncludeHighPriorityMessageOnly> <MessageIDs> MyMessagesMessageIDArrayType <MessageID> MyMessagesMessageIDType (string) </MessageID> <!-- ... more MessageID values allowed here ... --> </MessageIDs> <Pagination> PaginationType <EntriesPerPage> int </EntriesPerPage> <PageNumber> int </PageNumber> </Pagination> <StartTime> dateTime </StartTime> <!-- Standard Input Fields --> <DetailLevel> DetailLevelCodeType </DetailLevel> <!-- ... more DetailLevel values allowed here ... --> <ErrorLanguage> string </ErrorLanguage> <MessageID> string </MessageID> <OutputSelector> string </OutputSelector> <!-- ... more OutputSelector values allowed here ... --> <Version> string </Version> <WarningLevel> WarningLevelCodeType </WarningLevel> </GetMyMessagesRequest>
| Argument | Type | Occurrence | Meaning |
|---|
.ExternalMessageID MyMessagesExternalMessageIDType (string) Optional,
repeatable: [0..*] Currently available on the US site. A message ID that uniquely identifies a message for a given user. If provided at the time of message creation, this ID can be used to retrieve messages, and will take precedence over the message ID. A total of 10 message IDs can be specified.
true, only High Priority messages are returned in the response.
repeatable: [0..*] An ID that uniquely identifies a message for a given user.
The maximum and default values are not the same for all calls. For most Trading API calls, the maximum value is 200 and the default value is 25 entries per page.
Min: 1. Default: 1.
| DetailLevel | DetailLevelCodeType | Required,
repeatable: [1..*] |
Detail levels are instructions that define standard subsets of data to return for particular data components (e.g., each Item, Transaction, or User) within the response payload. For example, a particular detail level might cause the response to include buyer-related data in every result (e.g., for every Item), but no seller-related data. Specifying a detail level is like using a predefined attribute list in the SELECT clause of an SQL query. Use the DetailLevel element to specify the required detail level that the client application needs pertaining to the data components that are applicable to the request. The DetailLevelCodeType defines the global list of available detail levels for all request types. Most request types support certain detail levels or none at all. If you pass a detail level that exists in the schema but that isn't valid for a particular request, eBay ignores it and processes the request without it. For each request type, see the detail level tables in the Input/Output Reference to determine which detail levels are applicable and which elements are returned for each applicable detail level. Note that DetailLevel is required input for GetMyMessages. With GetSellerList and other calls that retrieve large data sets, please avoid using ReturnAll when possible. For example, if you use GetSellerList, use GranularityLevel instead, or use GetSellerEvents. If you do use 'ReturnAll' with GetSellerList, use a small Pagination.EntriesPerPage value and a narrow EndTimeFrom/EndTimeTo date range for better performance. Applicable values: If you do not include MessageIDs, this detail level returns header information for Alerts and Messages as follows:
Note: Even when restricted by this detail level to return only header information, GetMyMessages may return a high volume of data. (Not all values in DetailLevelCodeType apply to this field.) |
||||||||||||||||||||||||||||||||||||||||
| ErrorLanguage | string | Optional |
Use ErrorLanguage to return error strings for the call in a different language from the language commonly associated with the site that the requesting user is registered with. Below are some examples from different countries.
|
||||||||||||||||||||||||||||||||||||||||
| MessageID | string | Optional |
Most Trading API calls support a MessageID element in the request and a CorrelationID element in the response. If you pass in a MessageID in a request, the same value will be returned in the CorrelationID field in the response. Pairing these values can help you track and confirm that a response is returned for every request and to match specific responses to specific requests. If you do not pass a MessageID value in the request, CorrelationID is not returned. Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable. |
||||||||||||||||||||||||||||||||||||||||
| OutputSelector | string | Optional,
repeatable: [0..*] |
You can use the OutputSelector field to restrict the data returned by a call. This field can make the call response easier to manage, especially when a large payload is returned. If you use the OutputSelector field, the output data will only include the field(s) you specified in the request, as well as all of its child fields (if a field is a container) and its parent fields (if any). Note that it is possible that a field included through an OutputSelector field may still not be returned if it is not applicable, or if it is not found based on other criteria set up in the request payload. For example, if you are using GetItem and you only want to retrieve the URL of the View Item page (emitted in ViewItemURL field) and the item's Buy It Now price (emitted in BuyItNowPrice field), you would include two separate OutputSelector fields and set the value for each one as ViewItemURL and BuyItNowPrice as in the following example: If the following output selectors are used: See OutputSelector. |
||||||||||||||||||||||||||||||||||||||||
| Version | string | Conditional |
The version number of the API code that you are programming against (e.g., 1149). The version you specify for a call has these basic effects:
For the SOAP API: If you are using the SOAP API, this field is required. Specify the version of the WSDL your application is using. For the XML API: If you are using the XML API, this field has no effect. Instead, specify the version in the X-EBAY-API-COMPATIBILITY-LEVEL HTTP header. (If you specify Version in the body of an XML API request and it is different from the value in the HTTP header, eBay returns an informational warning that the value in the HTTP header was used instead.) See:
|
||||||||||||||||||||||||||||||||||||||||
| WarningLevel | WarningLevelCodeType | Optional |
Controls whether or not to return warnings when the application passes unrecognized or deprecated elements in a request. An unrecognized element is one that is not defined in any supported version of the schema. Schema element names are case-sensitive, so using WarningLevel can also help you remove any potential hidden bugs within your application due to incorrect case or spelling in field names before you put your application into the Production environment. WarningLevel only validates elements; it doesn't validate XML attributes. It also doesn't control warnings related to user-entered strings or numbers, or warnings for logical errors. We recommend that you only use this during development and debugging. Do not use this in requests performed in the Production environment. Applicable values: High if the user wishes to receive warnings when the application passes unrecognized or deprecated elements in an API call request. Setting the WarningLevel value to High is not recommended in a production environment. Instead, it should only be used during the development/debugging stage.Low if the user does not wish to receive warnings when the application passes unrecognized or deprecated elements in an API call request. This is the default value if WarningLevel is not specified in the call request.See Warning Level. |
Output
See also Samples.
The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).
See also the Deprecated Objects link above. Fields presented in this color are deprecated, and fields presented in this color are not returned (or soon will not be returned) or are not operational (or soon will be non-operational).
<?xml version="1.0" encoding="utf-8"?> <GetMyMessagesResponse xmlns="urn:ebay:apis:eBLBaseComponents"> <!-- Call-specific Output Fields --> <Messages> MyMessagesMessageArrayType <Message> MyMessagesMessageType <Content> string </Content> <ExpirationDate> dateTime </ExpirationDate> <ExternalMessageID> string </ExternalMessageID> <Flagged> boolean </Flagged> <Folder> MyMessagesFolderType <FolderID> long </FolderID> </Folder> <HighPriority> boolean </HighPriority> <ItemEndTime> dateTime </ItemEndTime> <ItemID> ItemIDType (string) </ItemID> <ItemTitle> string </ItemTitle> <ListingStatus> ListingStatusCodeType </ListingStatus> <MessageID> MyMessagesMessageIDType (string) </MessageID> <MessageMedia> MessageMediaType <MediaName> string </MediaName> <MediaURL> anyURI </MediaURL> </MessageMedia> <!-- ... more MessageMedia nodes allowed here ... --> <MessageType> MessageTypeCodeType </MessageType> <QuestionType> QuestionTypeCodeType </QuestionType> <Read> boolean </Read> <ReceiveDate> dateTime </ReceiveDate> <RecipientUserID> string </RecipientUserID> <Replied> boolean </Replied> <ResponseDetails> MyMessagesResponseDetailsType <ResponseEnabled> boolean </ResponseEnabled> <ResponseURL> anyURI </ResponseURL> </ResponseDetails> <Sender> string </Sender> <SendToName> string </SendToName> <Subject> string </Subject> <Text> string </Text> </Message> <!-- ... more Message nodes allowed here ... --> </Messages> <Summary> MyMessagesSummaryType <FlaggedMessageCount> int </FlaggedMessageCount> <FolderSummary> MyMessagesFolderSummaryType <FolderID> long </FolderID> <FolderName> string </FolderName> <NewHighPriorityCount> int </NewHighPriorityCount> <NewMessageCount> int </NewMessageCount> <TotalHighPriorityCount> int </TotalHighPriorityCount> <TotalMessageCount> int </TotalMessageCount> </FolderSummary> <!-- ... more FolderSummary nodes allowed here ... --> <NewHighPriorityCount> int </NewHighPriorityCount> <NewMessageCount> int </NewMessageCount> <TotalHighPriorityCount> int </TotalHighPriorityCount> <TotalMessageCount> int </TotalMessageCount> </Summary> <!-- Standard Output Fields --> <Ack> AckCodeType </Ack> <Build> string </Build> <CorrelationID> string </CorrelationID> <Errors> ErrorType <ErrorClassification> ErrorClassificationCodeType </ErrorClassification> <ErrorCode> token </ErrorCode> <ErrorParameters ParamID="string"> ErrorParameterType <Value> string </Value> </ErrorParameters> <!-- ... more ErrorParameters nodes allowed here ... --> <LongMessage> string </LongMessage> <SeverityCode> SeverityCodeType </SeverityCode> <ShortMessage> string </ShortMessage> </Errors> <!-- ... more Errors nodes allowed here ... --> <HardExpirationWarning> string </HardExpirationWarning> <Timestamp> dateTime </Timestamp> <Version> string </Version> </GetMyMessagesResponse>
| Return Value | Type | Occurrence | Meaning |
|---|
DetailLevel: ReturnHeaders, ReturnMessages.
repeatable: [0..*] A Message container is returned for each message that matches the input criteria in the call request. Each Message container consists of detailed information on a message. The amount of information that is returned in each Message container is partially dependent on the value that is set in the required DetailLevel field.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnMessages.
.ExpirationDate dateTime Conditionally Date and time at which a message expires.
DetailLevel: ReturnHeaders, ReturnMessages.
.ExternalMessageID string Conditionally ID used by an external application to uniquely identify a message. Returned only when specified by the external application on message creation.
This value is equivalent to the value used for MessageID in GetMemberMessages.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnHeaders, ReturnMessages.
.FolderID long Conditionally An ID that uniquely identifies a My Messages folder.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnHeaders.
Note: For GetMyMessages, the listing status reflects the status of the listing at the time the question was created. The listing status for this call must not match the listing status returned by other calls (such as GetItemTransactions). This is returned only if Messages.Message.MessageType is AskSellerQuestion. This tag is no longer returned in the Sandbox environment.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
This value is not the same as the value used for the GetMemberMessages MessageID. Use the GetMemberMessages value (used as the GetMyMessages ExternalID) instead.
DetailLevel: ReturnHeaders, ReturnMessages.
repeatable: [0..*] Media details stored as part of the message.
DetailLevel: ReturnHeaders, ReturnMessages.
.MediaName string Conditionally The name of the image. This will be displayed on the flimstrip.
Max length: 100.
.MediaURL anyURI Conditionally URL of an image to be included in a message. The image must be uploaded to EPS (eBay Picture Services) using a separate API call or the web flow. This URL will be validated and if it doesn't exist, the request will fail.
Max length: 200.
Applicable values: See MessageType.
Code so that your app gracefully handles any future changes to this list.
Applicable values: See QuestionType.
Code so that your app gracefully handles any future changes to this list.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnHeaders, ReturnMessages.
.RecipientUserID string Conditionally Displayable user ID of the recipient.
Note: Effective September 26, 2025, select developers will no longer receive username data for U.S. users through this field. Instead, an immutable user ID will be returned in its place. For more information, please refer to Data Handling Compliance.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnHeaders, ReturnMessages.
.ResponseDetails MyMessagesResponseDetailsType Conditionally Details relating to the response to a message.
DetailLevel: ReturnHeaders, ReturnMessages.
.ResponseDetails
.ResponseEnabled boolean Conditionally Whether a message can be responded to. To respond to a message, use the URL in ResponseURL. You may need to log into the eBay Web site to complete the response.
DetailLevel: ReturnHeaders, ReturnMessages.
.ResponseDetails.ResponseURL anyURI Conditionally A URL that the recipient must visit to respond to a message. Responding may require logging into the eBay Web site.
DetailLevel: ReturnHeaders, ReturnMessages.
Note: Effective September 26, 2025, select developers will no longer receive username data for U.S. users through this field. Instead, an immutable user ID will be returned in its place. For more information, please refer to Data Handling Compliance.
DetailLevel: ReturnHeaders, ReturnMessages.
Note: Effective September 26, 2025, select developers will no longer receive username data for U.S. users through this field. Instead, an immutable user ID will be returned in its place. For more information, please refer to Data Handling Compliance.
DetailLevel: ReturnHeaders, ReturnMessages.
DetailLevel: ReturnHeaders, ReturnMessages.
Max length: 2 megabytes in size.
DetailLevel: ReturnMessages.
DetailLevel: ReturnSummary.
DetailLevel: ReturnSummary.
repeatable: [0..*] Folder summary for each folder. Always returned for detail level ReturnSummary.
DetailLevel: ReturnSummary.
DetailLevel: ReturnSummary.
.FolderName string Conditionally The name of a specified My Messages folder. For GetMyMessages, Inbox (FolderID = 0) and Sent (FolderID = 1) are not returned.
DetailLevel: ReturnSummary.
.NewHighPriorityCount int Conditionally The total number of new high priority messages that a given user has.
DetailLevel: ReturnSummary.
.NewMessageCount int Conditionally The number of new messages in a given folder. Always returned for detail level ReturnSummary.
DetailLevel: ReturnSummary.
.TotalHighPriorityCount int Conditionally The total number of high priority messages that a given user has.
DetailLevel: ReturnSummary.
.TotalMessageCount int Conditionally The total number of messages in a given folder. Always returned for detail level ReturnSummary.
DetailLevel: ReturnSummary.
DetailLevel: ReturnSummary.
DetailLevel: ReturnSummary.
DetailLevel: ReturnSummary.
DetailLevel: ReturnSummary.
Applicable values:
(Not all values in AckCodeType apply to this field.)
Code so that your app gracefully handles any future changes to this list.
Note: GetCategories is designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, the MessageID and CorrelationID fields aren't applicable. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, MessageID and CorrelationID are applicable.
repeatable: [0..*] A list of application-level errors (if any) that occurred when eBay processed the request.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
See Errors By Number.
repeatable: [0..*] This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
[ attribute ParamID ] string Conditionally This optional element carries a list of context-specific error variables that indicate details about the error condition. These are useful when multiple instances of ErrorType are returned.
Applicable values:
If the source of the problem is within the application (such as a missing required element), change the application before you retry the request.
- If the problem is due to end-user input data, please alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, you can attempt to re-send the request to eBay.
- If the source of the problem is on eBay's side, An application can retry the request as-is a reasonable number of times (eBay recommends twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, the request may be resent in its original form.
See the Error handling section of the Making a Trading API call guide for more information.
When a warning occurs, the error is returned in addition to the business data. In this case, you do not need to retry the request (as the original request was successful). However, depending on the cause or nature of the warning, you might need to contact either the end user or eBay to effect a long term solution to the problem to prevent it from reoccurring in the future.
Code so that your app gracefully handles any future changes to this list.
Note: GetCategories and other Trading API calls are designed to retrieve very large sets of metadata that change once a day or less often. To improve performance, these calls return cached responses when you request all available data (with no filters). When this occurs, this time value reflects the time the cached response was created. Thus, this value is not necessarily when the request was processed. However, if you specify an input filter to reduce the amount of data returned, the calls retrieve the latest data (not cached). When this occurs, this time value does reflect when the request was processed.
Detail Controls
DetailLevel
The DetailLevel input field influences which call-specific fields may be returned. (All standard output fields are returned regardless of DetailLevel.)
The none column indicates the fields that are returned when you do not specify a DetailLevel.
Samples
New to making API calls? Please see Making a Call.
Note: Some item IDs, user IDs, or other data in these samples might no longer be active on eBay. If necessary, you can substitute current eBay data in your requests.
Available samples:
- Basic Call ↓ - Retrieves Message headers for the authenticated user.
- Specific Message IDs ↓ - Retrieves specific Messages, according to the provided message ID values.
- Message Folders ↓ - Retrieves message headers for the specified folder.
Retrieves Message headers for the authenticated user.
Description
This sample shows how to retrieve the headers for messages. Once retrieved, you can cache the MessageID values, which you can use to get more details on specific messages with another GetMyMessages call.
Input
XML format.
<?xml version="1.0" encoding="utf-8"?>
<GetMyMessagesRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<RequesterCredentials>
<eBayAuthToken>A*******3</eBayAuthToken>
</RequesterCredentials>
<WarningLevel>High</WarningLevel>
<DetailLevel>ReturnHeaders</DetailLevel>
</GetMyMessagesRequest>
Output
XML format.
<GetMyMessagesResponse xmlns="urn:ebay:apis:eBLBaseComponents">
<Timestamp>2019年11月04日T22:17:05.891Z</Timestamp>
<Ack>Success</Ack>
<Version>1127</Version>
<Build>E1127_CORE_APIMSG_19083139_R1</Build>
<Alerts/>
<Messages>
<Message>
<Sender>b***r</Sender>
<RecipientUserID>m***************r</RecipientUserID>
<Subject>b******r has sent a question about item #1**********2,
ending on Oct-18-19 18:52:35 PST - Acura : CL</Subject>
<MessageID>1*****0</MessageID>
<Flagged>false</Flagged>
<Read>false</Read>
<ReceiveDate>2019年10月18日T02:54:32.000Z</ReceiveDate>
<ExpirationDate>2020年02月12日T02:54:31.000Z</ExpirationDate>
<ItemID>1**********2</ItemID>
<ResponseDetails>
<ResponseEnabled>true</ResponseEnabled>
<ResponseURL>http://contact.sandbox.ebay.com/ws/eBayISAPI.dll?M2MContact&
item=1**********2&requested=b******r&qid=7****0&redirect=0&messageid=m1*****0</ResponseURL>
</ResponseDetails>
<Folder>
<FolderID>***</FolderID>
</Folder>
<Replied>false</Replied>
</Message>
<Message>
<Sender>b************r</Sender>
<RecipientUserID>m***************r</RecipientUserID>
<Subject>b************r has sent a question about :Question about book Edition for item #1**********5,
ending on Oct-16-19 15:45:13 PST - Harry Potter and the Philosopher's Stone</Subject>
<MessageID>1*****0</MessageID>
<Flagged>false</Flagged>
<Read>false</Read>
<ReceiveDate>2019年10月16日T18:03:43.000Z</ReceiveDate>
<ExpirationDate>2020年02月10日T18:03:43.000Z</ExpirationDate>
<ItemID>1**********5</ItemID>
<ResponseDetails>
<ResponseEnabled>true</ResponseEnabled>
<ResponseURL>http://contact.sandbox.ebay.com/ws/eBayISAPI.dll?M2MContact&
item=1**********5&requested=b************r&qid=7****2&redirect=0&messageid=m1*****0</ResponseURL>
<UserResponseDate>2018年10月17日T18:51:33.000Z</UserResponseDate>
</ResponseDetails>
<Folder>
<FolderID>***</FolderID>
</Folder>
<Replied>true</Replied>
</Message>
</Messages>
</GetMyMessagesResponse>
Retrieves specific Messages, according to the provided message ID values.
Description
Retrieve a summary of your messages by calling GetMyMessages with DetailLevel set to ReturnHeaders. Make a second call to GetMyMessages with DetailLevel set to ReturnMessages, and specify the message IDs of the messages you want to review. This returns detailed information for each specified message.
Input
You can specify up to to 10 MessageID values per request.
XML format.
<?xml version="1.0" encoding="utf-8"?>
<GetMyMessagesRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<DetailLevel>ReturnMessages</DetailLevel>
<RequesterCredentials>
<eBayAuthToken>1*******C</eBayAuthToken>
</RequesterCredentials>
<MessageIDs>
<MessageID>1**********0</MessageID>
</MessageIDs>
</GetMyMessagesRequest>
Output
Notice that the response contains HTML within the Text node.
XML format.
<?xml version="1.0" encoding="UTF-8"?>
<GetMyMessagesResponse
xmlns="urn:ebay:apis:eBLBaseComponents">
<Timestamp>2019年11月04日T22:17:05.891Z</Timestamp>
<Ack>Success</Ack>
<Version>1127</Version>
<Build>E1127_CORE_APIMSG_19083139_R1</Build>
<Messages>
<Message>
<Sender>e**y</Sender>
<RecipientUserID>r***9</RecipientUserID>
<Subject>?? You have a new offer: 12ドル.00 for Jonathon Byron Float... (1**********0)</Subject>
<MessageID>1**********0</MessageID>
<Text>Good news, R***l! You\x92ve received an offer for Jonathon Byron Float. The buyer is waiting - let them know your response before Oct-26 11:10:10 PDT.</Text>
<Flagged>false</Flagged>
<Read>true</Read>
<ReceiveDate>2019年10月24日T18:10:13.000Z</ReceiveDate>
<ExpirationDate>2020年10月24日T18:10:13.000Z</ExpirationDate>
<ItemID>1**********0</ItemID>
<ResponseDetails>
<ResponseEnabled>false</ResponseEnabled>
</ResponseDetails>
<Folder>
<FolderID>***</FolderID>
</Folder>
<Replied>false</Replied>
<ItemEndTime>2019年10月26日T18:28:54.000Z</ItemEndTime>
<ItemTitle>Jonathon Byron Floating Swans 3-D Hand-Painted Porcelain Collector Plate</ItemTitle>
</Message>
</Messages>
</GetMyMessagesResponse>
Retrieves message headers for the specified folder.
Description
If you get too much data when retrieving only message headers, you can further restrict the amount of data returned by specifying a FolderID in the request. Doing so returns only the message headers from the specified folder.
Retrieve the FolderID values for the My Messages folders by calling GetMyMessages with a DetailLevel of ReturnSummary. Note that the FolderID for the Inbox is 0.
Input
This example uses a FolderID of 2.
XML format.
<?xml version="1.0" encoding="utf-8"?>
<GetMyMessagesRequest xmlns="urn:ebay:apis:eBLBaseComponents">
<DetailLevel>ReturnMessages</DetailLevel>
<RequesterCredentials>
<eBayAuthToken>1*******C</eBayAuthToken>
</RequesterCredentials>
<FolderID>***</FolderID>
</GetMyMessagesRequest>
Output
The following sample shows the results from this call. Notice that the message is from FolderID 2.
XML format.
<?xml version="1.0" encoding="utf-8"?>
<GetMyMessagesResponse xmlns="urn:ebay:apis:eBLBaseComponents">
<Timestamp>2019年11月04日T22:17:05.891Z</Timestamp>
<Ack>Success</Ack>
<Version>1127</Version>
<Build>E1127_CORE_APIMSG_19083139_R1</Build>
<Messages>
<Message>
<Sender>e**y</Sender>
<RecipientUserID>s********r</RecipientUserID>
<Subject>eBay Second Chance Offer for Item #3**********9: Auction Title</Subject>
<MessageID>2*****9</MessageID>
<Flagged>false</Flagged>
<Read>false</Read>
<ReceiveDate>2019年10月20日T23:34:37.000Z</ReceiveDate>
<ExpirationDate>2019年11月20日T23:34:30.000Z</ExpirationDate>
<ResponseDetails>
<ResponseEnabled>true</ResponseEnabled>
<ResponseURL>http://*************.com</ResponseURL>
</ResponseDetails>
<Folder>
<FolderID>***</FolderID>
</Folder>
</Message>
</Messages>
</GetMyMessagesResponse>
Change History
| Change Date | Description |
|---|---|
| 743 2011年10月12日 |
|
| 677 2010年07月07日 |
|
| 661 2010年03月17日 |
|
| 657 2010年02月17日 |
|
| 635 2009年09月16日 |
|
| 583 2008年09月17日 |
|
| 573 2008年07月09日 |
|
| 479 2006年09月20日 |
|
| 445 2006年1月25日 |
|
| 439 2005年12月28日 |
|