Hi Djeeraj
Thanks for your alertness in raising this issue.
The Payment Methods API published version is rather old, and it's currently being revised (work still in progress). Perhaps
@Dominic Oyeniran, who leads this API, can give an idea and relate to the planning.
As a general rule, recently published APIs are being generated so that the swagger and the user guide (new name for the spec) come from the same source and there should be no discrepancy.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Feb 18, 2021 09:39
From: Dheeraj dheeraj.joshi@nokia.com
Subject: Disparity with related party field in TMF670 API
Hi
In TMF670 Payment method management API document resource model is depicts related party with 0 or 1 relation. However in the swagger json it is depicted as array.
Why a related party should be array?
Resource model for payment method management
In the above diagram related party could be either 0 or 1.
But in swagger json it is array. tmforum-apis/TMF670_PaymentMethods (Line number 45) it is an array, Should it be one abject or array of object?
------------------------------
~Dheeraj Joshi
Nokia
dheeraj.joshi@nokia.com
------------------------------