SeverityCodeType ( token )
SeverityCodeType - Type declaration to be used by other schema. This code identifies the severity of an API error. A code indicates whether there is an API-level error or warning that needs to be communicated to the client.
Type that uses SeverityCodeType:
Calls that use one or more values of SeverityCodeType:
AddFixedPriceItem, AddItem, AddItems, AddMemberMessageAAQToPartner, AddMemberMessageRTQ, AddMemberMessagesAAQToBidder, AddOrder, AddSecondChanceItem, AddToItemDescription, AddToWatchList, CompleteSale, ConfirmIdentity, DeleteMyMessages, EndFixedPriceItem, EndItem, EndItems, ExtendSiteHostedPictures, FetchToken, GetAccount, GetAdFormatLeads, GetAllBidders, GetBestOffers, GetBidderList, GetCategories, GetCategoryFeatures, GetCategoryMappings, GetChallengeToken, GetClientAlertsAuthToken, GetDescriptionTemplates, GeteBayDetails, GeteBayOfficialTime, GetFeedback, GetItem, GetItemsAwaitingFeedback, GetItemShipping, GetItemTransactions, GetMemberMessages, GetMessagePreferences, GetMyeBayBuying, GetMyeBaySelling, GetMyMessages, GetNotificationPreferences, GetNotificationsUsage, GetOrders, GetOrderTransactions, GetSellerDashboard, GetSellerEvents, GetSellerList, GetSellerTransactions, GetSessionID, GetShippingDiscountProfiles, GetStore, GetStoreCategoryUpdateStatus, GetSuggestedCategories, GetTaxTable, GetTokenStatus, GetUser, GetUserContactDetails, GetUserPreferences, GetVeROReasonCodeDetails, GetVeROReportStatus, LeaveFeedback, PlaceOffer, RelistFixedPriceItem, RelistItem, RemoveFromWatchList, RespondToBestOffer, RespondToFeedback, ReviseFixedPriceItem, ReviseInventoryStatus, ReviseItem, ReviseMyMessages, ReviseMyMessagesFolders, RevokeToken, SendInvoice, SetMessagePreferences, SetNotificationPreferences, SetShippingDiscountProfiles, SetStoreCategories, SetTaxTable, SetUserNotes, SetUserPreferences, UploadSiteHostedPictures, ValidateChallengeInput, ValidateTestUserRegistration, VerifyAddFixedPriceItem, VerifyAddItem, VerifyAddSecondChanceItem, VerifyRelistItem, VeROReportItems
|CustomCode||Reserved for internal or future use.|
|Error||The request that triggered the error was not processed successfully. When a serious application-level error occurs, the error is returned instead of the business data.
If the source of the problem is within the application (such as a missing required element), change the application before you retry the request.
See the Compatible Application Check section of the eBay Features Guide for more information.
|Warning||The request was processed successfully, but something occurred that may affect your application or the user. For example, eBay may have changed a value the user sent in. In this case, eBay returns a normal, successful response and also returns the warning.
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.