Hi!

I don't know why not all micro services are documented this way.

My recommendation is to directly read code (controllers of each micro
service),
this is the most up to date documentation.
Also playing around with Postman scripts (and creating your own) gives
one a good understanding of what the system is about and what is the
sequence the API calls need to be executed.

Postman scripts can be found here:
https://github.com/apache/fineract-cn-docker-compose#provisioning-the-micro-services-using-postman
(these scripts can be used with or without running dockerized micro
services )

Regards
Juhan Aasaru


Kontakt Aad Nales | Almende (<[email protected]>) kirjutas kuupƤeval R, 5.
juuni 2020 kell 09:43:

> Hi All,
>
> Currently i am trying to figure out what is in Fineract CN and what is not
> for a project that we are starting. I have started with going through the
> online documentation and i found that the list with all the project
> structure describes a number of API's that currently seem to be missing
> from the API reference.
>
> project structure:
> https://cwiki.apache.org/confluence/display/FINERACT/Fineract+CN+Project+Structure
>
> reference:
> https://cwiki.apache.org/confluence/display/FINERACT/Apache+Fineract+CN+API+Documentation
>
> The ones that seem to be missing are:
>
> Provisioner
> Rhythm
> Portfolio
> Cheques and
> Notification
>
> Is there any reason for this?
>
> TIA,
> Aad Nales
>
> --
>
> ---
>
> Website <http://www.almende.org>
> E-mail <[email protected]>
> Aad Nales
> Partner
>
> Almende B.V.
> Groot Handelsgebouw
> Stationsplein 45  | 3011 AK Rotterdam
>
> +31 10 404 94 44
> +31 6 54207340 (mob)
>
>
>

Reply via email to