Athenaeum — Partner API

A small, read-only JSON API exposing the publicly accessible portion of the catalog (members-only titles are never returned). Intended for partner institutions to pull catalog data into their own systems.

Authentication

Every request needs an API key, issued by a library administrator from the back-office API keys screen. Send it as a header:

X-Api-Key: your-key-here

(For quick testing in a browser, ?api_key=your-key-here also works.)

Endpoints

`GET /api/v1/titles.php`

List/search titles.

Param	Description
`q`	Free-text search across title, summary, ISBN, ISSN
`category_id`	Filter by category
`author_id`	Filter by author
`language_id`	Filter by language
`title_type_id`	Filter by title type (book/journal/magazine/periodical)
`page`, `per_page`	Pagination (max 100 per page)

`GET /api/v1/title.php?id=123`

Full record for a single title, including its authors, description, and any other-language editions.

`GET /api/v1/categories.php`

All categories and subcategories, with public title counts.

`GET /api/v1/authors.php`

List/search authors, including their photo if one's been uploaded. Accepts q, page, per_page.

Example

curl "https://your-library.example.com/api/v1/titles.php?q=dune" \
  -H "X-Api-Key: your-key-here"

Notes

All responses are JSON. Errors return a non-200 status with {"error": "..."}.
This API never returns download links to PDF files directly — link to detail_url instead, where a signed-in member (or the public, for open-access titles) can read or download from the site itself.
URLs in responses (like detail_url) follow whatever PRETTY_URLS is set to on the server — either style resolves either way, so partners don't need to handle both.
Rate limiting isn't built in yet; keep partner traffic reasonable or ask the library to issue a dedicated key per integration so usage can be tracked separately.