There is conflicting information being circulated about whether there will be an entirely new API with OAS specification to meet the SPoA policy change, or whether the existing API suite is going to be used (perhaps with updates?).
Could someone please confirm whether third parties will be migrating to a new system before the policy change, or would we still use A044 (for example), the current endpoint to initiate A&G.
Many thanks
Sam
We will be releasing new API specifications in due course to support the new A&G service initially, with SPOA support to follow (timing to be confirmed).
These releases will introduce new endpoints for A&G. The existing endpoints will remain backwards compatible; however, the new endpoints may be preferable for suppliers and their customers, as they are expected to support additional functionality over time that is not available in the current suite. Once the specifications are published, suppliers and customers will be able to decide which endpoints best align with their development plans.
At present, we do not have information regarding the deprecation of the current endpoints.
Also, if you’ve examples of conflicting info - that would be useful for the teams to consume and help clarify on future communications.