Deichman Bjørvika in Oslo seen from above: an open library space over several floors with shelves, escalators and visitors

PLAS API

A shared API for the library of the future

PLAS — the Public Library API Specification — makes library data and functions available in the same way across systems. The aim is more connected digital services for patrons and staff, and vendors who know what to expect from the data.

What can PLAS be used for?

  • As a requirement in a tender“Must support PLAS version X” instead of a set of API requirements the library has to write itself.
  • On top of what the library hasNo library has to change systems to benefit from the standard.
  • The same access across systemsPLAS makes access to data and functionality the same across systems.

From fragmented integrations to one shared standard

Today, access to library data and functions often runs through SIP2, NCIP, local APIs and separate, vendor-specific integrations. PLAS brings it together behind one open standard.

The aim: more freedom of choice for libraries, and services that work together — whoever the vendor.

Two entry points, one shared specification

PLAS has two entry points — one for each direction between the service and the source.

  • Illustration of a window showing the word API, connected to a cloud and a gear
    Calls from the service

    Provider API

    The source of data. The Provider API describes how the source makes its data and functions available. Search and Content are profiles of Provider that can also be implemented on their own.

  • Illustration of two layered windows, the front one showing a code symbol and lines of text
    Calls to the service

    Vendor API

    The other direction. The Vendor API describes what the service makes available back to the source — for example so the source can send events and return the patron after a single sign-on login.

An open industry initiative

PLAS is meant as an open industry initiative that belongs to the sector, not to one vendor, and the standard grows with the needs and input of libraries and vendors. The formal model for its governance is not yet in place.

A standard grows strong when many develop and use it. Needs, proposals and questions are welcome — from libraries, vendors and developers.

  • Libraries Can contribute needs, use cases and requirements.
  • Library systems Can implement the standard and help shape it.
  • Data providers Can make data and functions available.
  • Developers Can build new services and propose improvements.