Important to know about VertexFX API and its usage
Posted by BahaaAldeen Al Momani on 15 May 2020 01:26 PM
Dear Valued Customer/Partner,
Below is known information about API but thought it's good to highlight them in an easy way.
Q1: Does VertexFX has API?
A: Yes, but needs a separate ISV agreement to be signed in order to use it, for more information Click Here.
Q2: Can I develop anything after getting API?
A: Technically YES, legally NO. You can NOT use it to copy, compromise, or compete VertexFX system or any of its modules for example. If you did, one day we will stop it and may put penalty for API abusing or stop dealing with you completely. VertexFX API is our system's main source code intellectual proprietary and must be used in a very careful manner. Be cautious.
Q3: Is API Enabled by default on my VertexFX System?
A: Some times Yes, but still you should not use it if you did not get authorization to use it as per our ISV terms. You may use it through other ACTIVE Authorized ISV partner IF he has authority to run his plugins to other (distribution right). Most ISV agreements are of limited use to a specific system and specific projects. If the ISV party stop, you have to replace him by signing ISV agreement and may pay its cost.
Q4: Can API stop?
A: our security measurements let us reduce its functionality and add limitations or stop it if we witnessed any potential risk as per ISV agreement or API abuse. We have the right to change API functionality any time as we decide according to business or security needs.
Q5: Can I run third-party plugins?
A: Third-party licensed plugins are in vstore.co, if you run any external ones or developing your own, you will be responsible for its behavior not to breach the ISV agreement. Licensed plugins are trusted and easily can be run.
Q6: Can a licensed plugin stop?
A: if its developer did not renew his ISV agreement, he can not offer his plugins anymore. He still can support old clients but they need to have API themselves by signing ISV agreement and may pay the cost themselves instead of the developer. Else, possible API suspension may take place as the plugin can not keep running without one active ISV by developer or system owner.