[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Rollbase REST API

  • Thread starter Thread starter Anoop Premachandran
  • Start date Start date
Status
Not open for further replies.
A

Anoop Premachandran

Guest
Hi Filip, Sorry for the delayed response. Thanks for the detailed analysis. As you pointed out, our APIs currently have following issues a. Limited Documentation 1. Samples for many scenarios 2. Error handling 3. Input/Output formats for many field types 4. Supported Field Types b. Consistency 1. selectQuery Vs other APIs 2. Date Fields 3. Binary data (File and Image fields) 4. Arrays 5. Relationship Fields 6. ID Vs Code Vs Display Name 7. JSON Vs REST c. Permission Model - API and UI access control differs in some cases d. Bugs Short Term Plan We are working on improving documentation and fixing bugs and permission model issues. So please file any bug you find through Tech Support - we will prioritize them as early as possible. Long Term Plan The biggest issue is consistency and we are unable to fix them because most if not all of those changes will break backward compatibility. So we are working a new set of APIs - Rollbase REST 2.0 This would adhere to REST principles, will be standards based and support JSON only as data format. This would address all your concerns related to documentation, samples, will have a visual REST testing tool built into the product (something like Chrome POSTMAN). All APIs would be consistent including selectQuery which would be built on standard SQL parser. Hope this helps

Continue reading...
 
Status
Not open for further replies.
Back
Top