Can you elaborate please.
Have they created a Web API?
Are you wanting to consume that API into Access to do what?

No I know very little about API.  My database of course is Access. I understand that the managing authority of New Zealand Freemasonry  is planning to use API as their Communication Portal  for the storage of membership data.  Right now my database hold all data tables, forms. queries and reports.  Basically a stand alone system.  There are individuals at Division who see my database as a very promising Back end for the individual lodges scattered all over New Zealand.  Everything now is grunt work, mostly done paper and email from each lodge.   They seem to have made a decision to use Web API.   The would hold the Data about each mason, lodge secretaries would acquire that data via a website implementing API.  My question is.  I see on the web that Rest API can work with Access.  Not sure how effective it is nor how difficult to connect.  They want to be the holder of all member data.

You could host your data on SQL Server, in the cloud, and pull that data to your db locally, but also create a website with a user login system and build the forms/reports to show each division.

Access Online

Access SQL Server Online

Active Server Pages