API Overview

Authentication

API accesses must be authentified

There are two ways to manage authentication :

• Token based
• Session based

Authentication using token

A token contains all information relative to a user session, including user, folder and share context identifications.

Authentication tokens are managed by administrator using administration interfaces.

Tokens are under customer control and could expire or be revoked.

Token must be set in the Authorization http header of requests in bearer format.

Tip : When token are used, a silent authentication process is performed

Authentication using session cookies

Session cookies are set when a user connects to an Application.

To use session cookies your application must act behind a user and manage user connection prior to execute API requests.

See $connect API to manage user connection

Data oriented APIs

Data oriented APIs let you access the Application data.

Data oriented APIs don't require using DSM and can be use on any classes of the Application

Tip : In the context of FRP 1000, data means objects and doesnt' mean SQL database data. There are no API to access raw SQL Data.

SDATA REST API

SDATA API is a REST API which could be uses to query data, execute CRUD operations, BATCH operations and calling classes and objects methods.

SDATA REST API supports XML and Json format.

$connect API

$connect API is an API to manage user authentication.

This API can be use :

• To authenticate a user using a single call to $connect
• To build a login form using a set of API calls.

Build in feeds

Build in feeds are data feeds and services which are exposed under the SDATA API.

Build In feed let you access administration and exploitation information.

Tip : The user, behind the API call, must have administration role to use accesses some of these feeds

Service oriented APIs

Service oriented APIs are APIs based on service packages and may require to use the development platform (DSM) to extend the application model.

Tip : Some package services may be part of the Application standard model

Service package may expose json methods which can be call in a remote call paradigm.

A json method is a method receiving a json request and returning a json response.

Typical signature of a json method is :

  procedure myServicePackage.myJsonMethod(req:TJson; var resp:TJson);

Tip : FRP 1000 language supports Json using TJson class which allows to dynamically explore and build json structure.

Legacy APIs

Legacy APIs are API which are still supported but which must not be used for new developments.

SOAP API

SOAP API requires using the application development platform (DSM) to add SOAP service packages.

SOAP may be use in both client and server scenarii.

• In client scenario you import a WSDL service definition as a SOAP client package.
• In server scenario you build a SOAP Server package to expose services as SOAP functions and entities.