AbeBooks is focused on the health and safety of our employees, and based on regional regulations and social distancing requirements this has resulted in longer than usual response times from Customer Support. Please be patient.
If you have a specific question about an order, we recommend contacting the seller directly. This is often the fastest way to obtain order information. View instructions.
Due to Covid-19, delivery times may be longer than normal in your area. Learn more
Many other questions can be answered by visiting our help center.
AbeBooks Help Center
Search Bookseller Help
Order processing options for large volume sellers
AbeBooks supports a variety of order processing options suitable for large volume sellers. These include:
- Asynchronous Multi-Order Processing (AMoP) via FTPS
- Application Programming Interface (API) order processing
› Click here for inventory management options
Asynchronous Multi-Order Processing (AMoP) via FTPS
AMoP is a file-based order processing system designed for high-volume sellers who have some technical ability. Booksellers can use AMoP to exchange text files with AbeBooks via FTPS to process orders and returns in bulk.
A standard FTPS program can be used to connect and transfer files, but most AMoP sellers use specialized third-party software (such as Indaba, Monsoon, or Basil) or integrate AMoP’s functionality into their own custom software.
Please note all AMoP FTPS connections require TLS 1.2 protocol support.
› Download the order processing AMoP documentation (.pdf)
Order Update Application Programming Interface (API)
The AbeBooks Order Update API allows booksellers to use custom order processing applications that meet their particular business requirements. Order Update API is best-suited to sellers with advanced technical ability who plan to send frequent, small updates.
AbeBooks has specified a standardized format for passing order information to and from the Order Update API, as well as a set of commands and statuses that the bookseller’s client software can use. Data and commands are formatted using XML, an industry-standard markup language.
Communication is via the HTTPS protocol. Client software to access the server and process orders can be built using a number of popular programming languages such as Java, C, Perl, ASP.NET, etc.
To begin using the AbeBooks Order Update API, you will need:
- An active bookseller account with AbeBooks
- The Order Update API documentation, available free from AbeBooks (download link below).
- Client software (written by Bookseller)
You will access the server using your Bookseller (vendor) Userid and unique API Key. This information must be included in each call to the server.
› Learn more about the unique API Key
› Download the Order Update API documentation (.pdf)
Comparison Guide
| AMoP | API |
| Connect via FTPS | Connect via HTTPS with custom script |
| Knowledge of a scripting language or XML not essential | Knowledge of a scripting language and XML essential |
| Slower – order files created and processed hourly | Faster – get and update orders instantly |
| Order data sent in plain text documents | Order data sent via XML requests |
| Supports credit card payment only | Supports seller direct payment options |
| Tracking can only be added when order is processed | Update tracking while processing order or after processing |
| Returns can be processed in bulk | Returns cannot be processed via API |