Ocrolus API

Ocrolus API Documentation

Welcome to the Ocrolus API Documentation. You'll find comprehensive guides and documentation here to help you get started with the Ocrolus API. Let's jump right in!

Retry Strategies

To save resources, consider adapting to error conditions when polling Query Endpoints such as Book Status, or with long running Download Endpoints such as Analytics (JSON) and Analytics (Excel).

This strategy mitigates the kind of transient network fluctuations that can cause HTTP Status Code errors. These intermittent interruptions are often the result of minor network hiccups. Although the interruptions are most likely small, they can still cause disruptions to your integration components.

To guarantee data extraction, wrap all invocations in the appropriate error handler, and implement a retry strategy for your HTTP calls with a reasonable back-off period. This ensures a high rate of successful API calls, and this strategy works consistently because the system usually fixes itself within a couple of retries.

Updated about a year ago

Retry Strategies


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.