PHP CrossRef Client

This is a library for the Crossref REST API written in PHP.

Table of contents

• Introduction
• Installing
• Usage
  • Singletons
  • Determine existence of a singleton
  • Lists
• Configuration
  • Caching results
  • Identifying your script
  • Tying to a specific major version
  • Rate limits
• Handling errors

Introduction

This is NOT an official library! The intent of this library is to provide an easy way to make requests to the CrossRef's REST API. You SHOULD read this documentation in conjunction with the official documentation.

Highlighted features:

• You don't need to worry about making HTTP requests;
• Proper exceptions are thrown if an HTTP error occurs;
• You receive responses as-is, without overlay;
• Filter and facet parameters are encoded if needed;
• You can cache responses easily;
• You can identify yourself, then you can benefit better service;
• You can tie to a specific major version of the API;
• Your application complies with the rate limit (it works better if cache is configured).

Library's summary:

Installing

Usage

Singletons

Singletons are single results. Retrieving metadata for a specific identifier (e.g. DOI, ISSN, funder_identifier) typically returns in a singleton result.

See: https://github.com/CrossRef/rest-api-doc#singletons

The above example will output:

Determine existence of a singleton

(...) [You can] determine "existence" of a singleton. The advantage of this technique is that it is very fast because it does not return any metadata (...)

See: https://github.com/CrossRef/rest-api-doc#headers-only

The above example will output:

Lists

Lists results can contain multiple entries. Searching or filtering typically returns a list result.

A list has two parts: Summary; and Items. Normally, an API list result will return both.

See: https://github.com/CrossRef/rest-api-doc#lists

Configuration

Caching results

Cache data so you don't request the same data over and over again.

See: https://github.com/CrossRef/rest-api-doc#etiquette

The above example uses voku/simple-cache as cache implementation, but you can use any PSR-16 implementation because setCache() accept Psr\SimpleCache\CacheInterface as argument.

Identifying your script

As of September 18th 2017 any API queries that use HTTPS and have appropriate contact information will be directed to a special pool of API machines that are reserved for polite users.

See: https://github.com/CrossRef/rest-api-doc#good-manners--more-reliable-service

The above example makes all subsequent requests attach the contact information given.

Tying to a specific major version

If you need to tie your implementation to a specific major version of the API, you can do so by using version-specific routes. The default route redirects to the most recent version of the API.

See: https://github.com/CrossRef/rest-api-doc#how-to-manage-api-versions

The above example tie all subsequent requests to the API version v55.

Rate limits

By default, this library conforms to the rate limit imposed by the API for the current execution.

If you want to keep this behavior across multiple executions, you must configure the cache, as mentioned above.

Handling errors

As this library uses guzzlehttp/guzzle internally. Please refer to the Guzzle Exceptions documentation to see how to handle exceptions properly.