It is not – the API is fundamentally required for the application to function at all, so it’s more or less always going to be running if any component is running.
On a separate note, many installations don’t necessarily _expose_ it; the API by default is run so that it’s only accessible to other things on the same computer (technically speaking, served on a port that’s not exposed externally) -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of "Wisner, Melanie" <mmwis...@fas.harvard.edu> Reply-To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Date: Thursday, August 6, 2020 at 2:17 PM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] API Do you all know if the API is governed by an on/off switch in ASpace, like the PUI (and by default set one way or the other), or has to be created? Thanks! Melanie Melanie Wisner (she / her / hers) Accessioning Archivist Houghton Library Harvard University 617-384-7373 | mmwis...@fas.harvard.edu Building an Accessible Future | Houghton Library Renovation<https://houghtonrenovation.library.harvard.edu/>
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
