...
Any development work on an integration must be performed in the sandbox environment
A production integration should never use a staff user account. Any suspicious activity performed by a user will result in that account being locked.
High volume calls cannot be performed during peak hours
Any program that performs create or update activities must use business logic end points
Deletes are highly discouraged
An external integration should not be used to replicate available functionality
Example: The Bulk Edit module can assign or clear a temporary location from an item. Users seeking to make batch changes to temporary item locations should use Bulk Edit rather than use an external integration to make batch changes to item temporary locations
Exceptions will be made if the API is more reliable or more stable
Any program that causes stability issues, data integrity issues, performance issues, or performs a function not included in the initial request will be disabled without notice.
Users may not use the program’s username / password to access the FOLIO UI
Non-API integrations
There three sets of endpoints designed for a more secure access to certain types of data. These have lower impact on performance and pose a lower security risk, but may have additional complications.
FOLIO also includes:
OAI-PMH Edge API
Z39.50 Server
RTAC Edge API
...