Hey Bhuwan,
Experimental API endpoints can change at any time without notice. I wouldn't rely on them for a Marketplace add-on if you have other options because of the distinct possibility that the endpoint could change or be removed in a future release without warning to you.
Since you're working with Server, you do have the advantage that the API methods won't change in the current releases. For instance if the API hasn't changed between 7.6 and 7.12, you could mark your plugin as compatible for those versions. When the next version is released, you'll need to check the API documents to see if there were any changes (because the development team may or may not actually post a notice that they've made changes to an experimental endpoint).
Worst-case scenario, you build your plugin around the endpoint and have to mark it as incompatible with future versions. This happens - sometimes plugins can't be used past a specific version. If there are just changes to the endpoint and not a complete removal, you can publish a new version of the plugin with the correct API changes that you can mark as compatible with those versions going forward.
So my advice in a nutshell is:
- Use another currently-supported method for storing data if one is readily available, and if you can't:
- Check each version of the API docs to make sure there weren't changes between 7.6, 7.7, 7.8, etc.
- Mark your plugin as compatible for the versions you've checked
- Be prepared to publish a new version of the plugin using a modified API that isn't backwards-compatible if the API endpoint changes before coming out of Experimental status
Good luck with your plugin! Looking forward to seeing what you're building.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.