Archer Community

Ilya_Khen · ‎2018-11-02

Hi all,

Statement:

Archer v6.4 SP1 P3.

Platform API.

Question:

If I get it right, platform API is something which is combining both WEB and REST APIs. While old path of using /api and /ws is available, we can do the same requests to /platformapi and Archer would redirect request to relevant nodes based on the request itself?

Also, I did not find documentation on Platform API aside of FFTH.

Anonymous · ‎2018-11-05

Ilya,

Where did you see a FFTH on Platform API? Was it mine on the Content API and BI Tools? If so, I used "Platform API" there to refer to the existing SOAP and REST APIs collectively, and to distinguish them from the new Content API. Platform APIs do platform things in platform speak; Content API does content things in content speak.

I'm not aware of us having released any kind of new smart endpoint that can route requests to REST or SOAP based on the request to the same endpoint.

View solution in original post

Anonymous · ‎2018-11-05

Ilya,

Where did you see a FFTH on Platform API? Was it mine on the Content API and BI Tools? If so, I used "Platform API" there to refer to the existing SOAP and REST APIs collectively, and to distinguish them from the new Content API. Platform APIs do platform things in platform speak; Content API does content things in content speak.

I'm not aware of us having released any kind of new smart endpoint that can route requests to REST or SOAP based on the request to the same endpoint.

Ilya_Khen · ‎2018-11-06

Hi Scott,

I remember this from one of the FFTH we had, when you published new GRC API and PowerBI. And then I noticed that since then several new API points appeared in the RSAarcher web application: api, contentapi, platformapi, ws.

So, I knew how to utilize api, ws and contentapi, but I have no idea how to use platormapi.

I had some back memory that you said, we can now use platformapi instead of separate calls to REST and WEB APIs, but maybe I mixed things up, so wanted to get confirmation

Anonymous · ‎2018-11-06

Ilya,

I believe the /platformapi is a new alias for the REST API. In a future release, we may deprecate /api, leaving you with three clear aliases for the three APIs:

/ws - SOAP API
/platformapi - REST API
/contentapi - Content API

Ilya_Khen · ‎2018-11-06

Hi Scott,

That explains. Thanks! Mind to share the reason for deprecating api? Is it for better clarity and usage purpose?

Anonymous · ‎2018-11-06

That's exactly it. It defines the REST API as being for platform purposes, which is vastly different than the content driven purpose of the Content API.

Ilya_Khen · ‎2018-11-06

Thanks a lot! Much appreciate!

Anonymous · ‎2018-11-06

You're welcome. Happy Archering!

NasimBeg · ‎2018-11-06

Scott, Can you help me understand the difference in REST API(Platform) & Content API?

Ilya_Khen · ‎2018-11-06

You need to look at the FFTH of the Content API. It basically translates metadata and provides better readable output. Scott calls it "human output"

FFTH: Content API, BI Tool Integrations, Tableau Web Data Connector Slides

https://community.rsa.com/docs/DOC-95916