CONTENTS

• Overview
• Authentication
• Errors
• Versioning
• Common Parameters
• Triggers

RESOURCES

• /feedback
• /items
• /itemLocations
• /listings
• /locations
• /messages
• /orders
• /orderItems
• /settings
• /settlements
• /transactions
• /triggers
• /venues
• /whoami

MACROS

• Macros Overview
• doSendToFBA

VERBS

• Verbs Overview
• searchCatalogs
• fbaCreateInboundShipmentPlan

REPORTS

• Reports Overview
• itemsOrderedByPeriod
• skusOrderedOnDate

API Versions

As developers, we understand the need to maintain a consistent interface. We also like to add features and data to continue to improve our products. We such, we have the following policies regarding changes to the SellerLabs API:

Non-Breaking Changes

We consider the following changes to be "Non-Breaking". Your application should work in such a way that it is not dependent on these items which may be changed:

• Adding new API resources.
• Adding new optional request parameters to existing API methods.
• Adding new properties to existing API responses.
• Changing the order of properties in existing API responses.
• Changing the length or format of object IDs or other opaque strings.
• Adding new event types.

On object IDs:

This includes adding or removing fixed prefixes (such as 'az_' on order_is). You can safely assume object IDs we generate will never exceed 255 characters, but you should be able to handle IDs of up to that length. If for example you.re using MySQL, you should store IDs in a VARCHAR(255) COLLATE utf8_bin column (the COLLATE configuration ensures case-sensitivity in lookups).