#2673-Request for Additional List APIs

Aji
OPEN
#1
Aji

 Aji

Dear Ronok,


I hope you are doing well.

We would like to kindly request your consideration for adding a few additional Directory/List APIs to the platform. These APIs would be very helpful for building reliable and scalable integrations with the platform and would allow external applications to dynamically retrieve the required configuration details without depending on manually maintained or hardcoded IDs.

We would appreciate it if the following APIs could be made available:

1. Team Member / Agent List API

An API to retrieve the available team members with details such as:

  • Team Member ID
  • Name
  • Email
  • Role
  • Status
2. Sequence List API

An API to retrieve all available sequences along with:

  • Sequence ID
  • Sequence Name
  • Status
3. Bot Flow List API

An API to retrieve the configured bot flows with:

  • Flow ID
  • Flow Name
  • Status
4. Team Role List API

An API to retrieve available team roles with:

  • Role ID
  • Role Name
  • Status

For example, the API response could provide mappings such as:

Team Member
Aj → 130848

Sequence
Customer Follow-up → 13083

Bot Flow
Appointment Flow → 1552533

Team Role
Sales Agent → 7490

Having these directory APIs would allow an integration to dynamically maintain the relationship between the configuration name and its corresponding ID. This would eliminate the need for developers to manually configure or hardcode IDs and would ensure that integrations continue to work correctly when configurations are added, renamed, or updated within the platform.

We would be very grateful if your team could consider implementing these APIs as part of the platform's API offering, with the appropriate authentication and account-level access controls.


These additions would significantly improve the flexibility, reliability, and maintainability of integrations built on top of the platform.


Thank you very much for considering this request. We really appreciate your continued support and would be grateful if this could be considered for implementation in the upcoming API enhancements.

Related Threads