Considerations for Commonly-Used Documoto SOAP APIs

In this article, we outline considerations and recommendations for utilizing Documoto's most commonly-used SOAP APIs. If you are looking for more general information on Documoto's available APIs, please refer to: User Guide to Documoto Web Services (APIs).

Article Topics

• Using the supersedePart API
• Using the uploadFileToBePublished API
• Using Update APIs (updateParts, updateMedia, updatePagePartTags, etc.)

Using the supersedePart API

1. Send a single request at a time
2. Wait until receiving a response before sending next request
3. Re-send failed requests up-to 3 times before logging for troubleshooting. Sometimes it will go through on a subsequent try due to system constraints at the time the request was sent.

Using the uploadFileToBePublished API

1. Can submit up-to 10 files in a single request
2. Try not to have 5 simultaneous requests out waiting for a response
• Can slow down publishing times/cause indexing delays

Using Update APIs (updateParts, updateMedia, updatePagePartTags, etc.)

1. Try to batch your updates in single request
2. Set the timeout to wait for response from Documoto to 10 minutes to ensure there are no dropped connections
3. Batch size max of 50 items
4. Send up to 10 batches at once, and wait until each finishes to start the next batch