CONTENTS
Recommendations and Data Limits
OData and REST APIs are intended for lower volume integrations. Lower volumes are roughly defined as requests not exceeding 500K per 30 seconds.
When using 3E APIs to build integrations, please keep in mind that data ingress (i.e., POST) and egress (i.e., GET) calls are limited to ensure 3E Cloud maintains availability and resiliency. Data ingress and egress and request limits are shown below:
Note: For 3E Cloud, whether it is ingress or egress, throttling will kick in when the number of calls are exceeded.
Limit 60 calls per minute for OData
Limit 5k per page/call for OData
Note: This limit is for the request response for GET and for the Body of POST & PUT API calls and any calls where a body is sent as part of the request. The response will always just return a maximum of 5,000 rows. A link returning the next page of results will be provided if the response exceeds 5,000 rows.
Limit 30 calls per minute for REST
Note: The above data limits are for 3E Cloud only. Firms using 3E On-premises determine the call limitation for their instances.
Note: 3E Cloud now offers 3E Change Stream, an integration pattern that supports the need to extract volumes of detailed 3E financial data from the cloud. 3E integrators can now provide a webhook to subscribe to 3E data changes. Please visit the Elite Knowledge Base and see article E-20980 for more information.