Thanks, Bharath,

> What's the difference between these instances  *https://mobile.mifos.io/
<https://mobile.mifos.io/>* and *https://demo.fineract.dev/
<https://demo.fineract.dev/>, *are they equivalent in terms of
functionality?

> Do we have some wiki/docs where all the business-related terms are
explained. For instance, users, clients, groups, Centers, etc, and related
terms.


On Mon, Nov 23, 2020 at 8:40 PM Bharath Gowda <bgo...@mifos.org> wrote:

> Hi Saksham,
>
> All routes behind /self are the self-service APIs built for the opensource
> android application as rightly mentioned by Oluwalana, However, it can be
> accessed through Postman with self-service enabled user credentials
>
> Self-service users can be created by following  This
> <https://docs.google.com/document/d/1sxt2Ou7-TjGnk9azKhw7AtcSWY8mKubP1lWfqXx9pL8/edit>
>  document.
>
> You can also refer to the instance https://mobile.mifos.io/ which has
> self-service user already created
>
> Credentials are
> User:299devansh
> Password:password
>
>
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Sun, Nov 22, 2020 at 8:12 PM Saksham Handu <academic.ra...@gmail.com>
> wrote:
>
>> I planning to use *https://demo.fineract.dev <https://demo.fineract.dev>
>> *in the self-service mobile app. Currently, *https://mobile.mifos.io/
>> <https://mobile.mifos.io/> *is used in the self-service mobile
>> application.
>>
>> > As per the documentation, I see *mifos:password* creds only. I guess
>> then it will not be for functional for self-service API, right?
>>
>> > I see since DB is wiped off once every week. Do we have some creds for
>> self-service available, I'm not able to find it in any docs which I
>> referred to? [image: image.png]
>> > Another thing, I would like to ask, what all possible *tenant *values
>> are possible and which one is preferred when and why. I'm not able to find
>> much info on it also in the docs while reading them.
>>
>>
>> On Sun, Nov 22, 2020 at 6:44 PM Oluwalana Olasubomi <
>> subomioluwalan...@gmail.com> wrote:
>>
>>> I don't think there's any way you can correct it.
>>>
>>> It's working by design. The initial request responds correctly. What I
>>> think you want is; you have a particular use case for some of the
>>> self-service APIs.
>>>
>>> If yes? You might to state that use case and ask how to achieve that
>>> without depending on the self-service APIs.
>>>
>>> Cheers
>>>
>>> On Sun, 22 Nov 2020 at 1:39 PM, Saksham Handu <academic.ra...@gmail.com>
>>> wrote:
>>>
>>>> Thanks, Oluwalana for your inputs
>>>>
>>>> As per the API docs, I don't see any difference between the two. Can
>>>> you please elaborate, so that I can correct my postman request (attached in
>>>> previous mail's attachment) in a similar manner?
>>>>
>>>> On Sun, Nov 22, 2020 at 5:08 PM Oluwalana Olasubomi <
>>>> subomioluwalan...@gmail.com> wrote:
>>>>
>>>>> Hi Saksham,
>>>>>
>>>>> All routes behind /self are the self service APIs built for the
>>>>> opensource android application whereas other APIs like /client was built 
>>>>> to
>>>>> interact with your backend system.
>>>>>
>>>>> The two APIs have different authentication mechanisms that explains
>>>>> the 401.
>>>>>
>>>>>
>>>>> On Sun, 22 Nov 2020 at 10:44 AM, Saksham Handu <
>>>>> academic.ra...@gmail.com> wrote:
>>>>>
>>>>>> Hello Community,
>>>>>>
>>>>>> I'm new to Fineract API, and I was trying Fineract API from the
>>>>>> postman to get some understanding of its underlying APIs.
>>>>>>
>>>>>> I think we have an issue with */self/clients* endpoint. Refer ss 1
>>>>>> in attachment, it was not successful. I was getting 401
>>>>>>
>>>>>> Whereas I used */clients* endpoint, with the same Authorization
>>>>>> Header, it was a success 200. Refer to ss 2 in the attachments.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Saksham Handu
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Saksham Handu
>>>>
>>>
>>
>> --
>> Regards,
>> Saksham Handu
>>
>

-- 
Regards,
Saksham Handu

Reply via email to