Skip to end of banner
Go to start of banner

HTTP API Guidelines

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

This guide is intended to provide guidance of how HTTP APIs in FOLIO are intended to behave.

Collections of Records

Many of the APIs in FOLIO are intended for maintaining collections of records.

Root Path

The endpoints that make up the API for a collection of records are grouped together by a common root path e.g. /circulation/loans.

This path should include the type of records e.g. loan and some context to differentiate them from other record types with the same name e.g. /circulation/loans or /circulation-storage/loans.

This helps to reduce the potential for path conflicts in the system.

Endpoints

MethodSub PathPurposeExpectations
POST/Create a new record
GET/Fetch a (sub)set of records
GET/{id}Fetch an individual record

If the record exists, the server must respond with a 200 status code and a JSON representation of the record

If the record does not exist, the server must respond with a 404 status code

PUT

/{id}

Create or replace an individual record
DELETE/{id}Delete an individual record
  • No labels