Idea ID: 2867404

Overhaul of SMAX REST APIs & Documentation

Status : Waiting for Votes
2 months ago

Dear team,

As we continuously SMAX platform, there is a growing demand to achieve SMAX integrations with external systems, for use-case such as - case-exchange, collaboration tools, automation, 3rd party monitoring tools, reporting and data-extraction. For all such cases, practitioners need clear and detailed information on usage of SMAX REST APIs. While the quality of current documentation on APIs (Develop Section) has been steadily improving, but it needs to be much more structured and detailed to be effectively understood and used by field team and practitioners.

Here are some ideas where things can be improved.

  • Proper listing of all the endpoint/resources and supported operations GET/POST/PUT/DELETE with payload example.
  • API versioning can be incorporated to bring in enhancements and notify depreciations.
  • Documentation should contain code samples (for Java, Python, NodeJS, etc) for major entities and their operations
  • Would be excellent to have Swagger style API documentation and testing inside the product itself. The 'EMS Rest API' is very helpful, but needs to be matured further to reduce hit-and-trial approach.

References of few well documented APIs, which can be looked into for ideas.

Thanks,

Abhishek Danej

Parents
  • This will enable the implementation team to exploit the capabilities of SMAX as per the best practices, while specializing in third party integrations as many use cases are dependent on multiple business applications & functions. This will give more power to ESM framework, while reducing the noise on the ground.

Comment
  • This will enable the implementation team to exploit the capabilities of SMAX as per the best practices, while specializing in third party integrations as many use cases are dependent on multiple business applications & functions. This will give more power to ESM framework, while reducing the noise on the ground.

Children
No Data