The End Point Library provides tools for the writing, testing, organisation and deployment of your end points.
They are often used to provide an interface between the forms a user interacts with and the systems that the rest of your solution connects to.
- They are created and maintained within their own content section of iCM
- The ability to create and edit end points is controlled by a user's iCM Privileges (users without access to create/edit end points can still call them in their own forms etc)
- They are stored in the iCM database and subject to iCM version history policies
- They can be imported and exported from one iCM to another
- They are deployed to one or more of the four End Point Library Workers , which allow you to set up a range of security options, including open to AJAX requests, secured to an API key, or internal
- They can be flagged as internal, preventing anything other than internal requests from end points deployed to the same worker from accessing them
- Each can also have a request parameter and return schema defined for additional validation