bradleyhodges/api-manager

A powerful, robust, secure, and compliant API manager for PHP-based APIs

4.1.0 2024-08-26 10:48 UTC

This package is auto-updated.

Last update: 2024-11-07 06:21:11 UTC


README

APIManager is a robust PHP package that simplifies API development by providing compliant, secure utilities for handling CORS, managing API responses, implementing rate limiting, making HTTP requests, sanitizing input, and much more.

Features ๐ŸŽฏ

  • ๐ŸŒ Powerful HTTP Client: Send any HTTP request quickly with support for browser impersonation, Happy Eyeballs, DNS caching, HTTP/1, 2, and 3*, and more.
  • ๐Ÿ” CORS Management: Easily configure Cross-Origin Resource Sharing (CORS) rules.
  • ๐Ÿ“Š Rate Limiting: Implement rate limiting with customizable policies.
  • ๐Ÿ—„๏ธ Response Management: Structure your API responses and handle errors consistently.
  • ๐Ÿงน Input Sanitization: Clean and sanitize user input.
  • ๐Ÿ”„ Custom Headers: Add or remove custom headers in your API responses.
  • ๐Ÿ“‹ CSRF Protection: Secure your forms with CSRF token management.
  • ๐Ÿ›ก๏ธ Security Headers: Apply essential security headers to safeguard your API.

Installation ๐Ÿ› ๏ธ

This package is published to Packagist. Recommended installation is via Composer:

composer require bradleyhodges/api-manager

If you prefer to go cowboy and always have the latest version, you can also manually add it to your composer.json:

{
    "repositories": [
      {
        "type": "vcs",
        "url": "https://github.com/bradleyhodges/api-manager.git"
      }
    ],
    "require": {
        "bradleyhodges/api-manager": "dev-main"
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

Usage ๐Ÿ“

Basic Setup

use APIManager\APIManager;

// Initialize the APIManager
$apiManager = new APIManager();

PHPDocs

Full documentation is available at https://bradleyhodges.github.io/api-manager. Alternatively, some common usage examples have been included below. I'll probably get around to uploading some examples at some point, but for now, this is the jazz.

HTTP Client Usage ๐ŸŒ

The HTTP class provides a powerful HTTP client built on top of Guzzle, with support for Happy Eyeballs, DNS caching, HTTP/1, 2, and 3, retry logic, and more.

Some really neat features and enhancements are enabled by default, including:

  • Happy Eyeballs Algorithm: This optimizes connection speed by attempting to connect to both IPv4 and IPv6 addresses simultaneously, selecting the one that responds the quickest. This ensures minimal latency, especially in environments where network configurations might favor one protocol over the other.

  • Content-Type Detection: Automatically detects the correct content type for requests and formats content accordingly.

  • Browser Impersonation: Sends requests that mimic browser behavior, including handling cookies and redirects.

  • DNS Caching: DNS responses are cached for faster subsequent requests, reducing the overhead of repeated DNS lookups. This is especially useful for APIs with high traffic, as it cuts down on repeated DNS resolution time and improves response times.

  • HTTP/3 Fallback: By default, the client attempts to use HTTP/3 for faster and more reliable connections. If HTTP/3 is unavailable, it automatically falls back to HTTP/2 or HTTP/1.1, ensuring compatibility with a wide range of server configurations.

  • Automatic Retry with Exponential Backoff: The client can be configured to automatically retry failed requests (such as network timeouts or server errors). The retry logic includes exponential backoff with jitter, minimizing the chances of overloading the server with repeated requests in rapid succession.

  • TLS Enforcement: For security, the client enforces a minimum TLS version of 1.2, ensuring that all connections are secure and compliant with modern security standards (can be overriden using $http->useMinTlsVersion(false);).

  • Customizable DNS Resolver: By default, the client uses Cloudflare's 1.1.1.1 DNS resolver for faster and more secure DNS lookups. This can be toggled off if the system's default DNS resolver is preferred.

  • Cookie Management: The client includes a CookieJar by default, allowing for stateful HTTP requests with cookie management across multiple requests. This is useful for interacting with APIs that require session management.

These features are highly configurable and can be enabled or disabled based on your specific needs, giving you full control over how your HTTP requests are handled.

Here's a basic usage example:

use APIManager\APIManager;

// Initialize the APIManager
$apiManager = new APIManager();

// Initialize the HTTP client
$http = $apiManager->useHTTP();

// Send a GET request
$response = $http->get('https://google.com');

// Get the response body
$body = $response->getBody()->getContents();

// Get the response code and reason phrase
$responseCode = $response->getStatusCode(); // 200
$responseReason = $response->getReasonPhrase(); // OK

// More methods and examples at https://docs.guzzlephp.org/en/stable/quickstart.html#using-responses
// Just replace `$client` with `$http` to use them

If you only need HTTP, you can initialise it with shorthand:

$http = (new APIManager())->useHTTP();

or, even simpler:

use APIManager\HTTP;

$http = new HTTP();

You can also configure advanced options such as retries, DNS caching, and HTTP version fallback:

$http->useRetry(true)
     ->useDnsCache(true)
     ->useHttpVersionFallback(true);

// Send a POST request with a Bearer token
$http->setBearerToken('your-token-here');
$response = $http->post('/submit', ['json' => ['key' => 'value']]);

Because the HTTP Class is built on top of Guzzle, you can optionally pass your custom Guzzle config:

use APIManager\HTTP;

$http = new HTTP([
    // Base URI is used with relative requests
    'base_uri' => 'http://httpbin.org',
    // You can set any number of default request options.
    'timeout'  => 2.0,
]);

If you'd prefer to access Guzzle's methods directly, you can use the getClient method to access the Guzzle client instance and call it's methods as usual:

use APIManager\HTTP;

// Initialize the HTTP client
$http = new HTTP();

// Access the Guzzle client instance
$client = $http->getClient();

// Send an asynchronous request using Guzzle's magic methods:
$promise = $client->getAsync('http://httpbin.org/get');

CORS Configuration ๐ŸŒ

The CORS implementation is RFC 6454 compliant and "just works" with minimal configuration. Simply specify the allowed origins, and the rest is handled for you. If you need more control, you can optionally configure other aspects like allowed methods, headers, and credentials:

$apiManager->useCORS([
  'allowedOrigins' => ['https://example.com'],
  'allowCredentials' => true,
  'allowedMethods' => ['GET', 'POST', 'OPTIONS'],
  'allowedHeaders' => ['Content-Type', 'Authorization'],
  'exposedHeaders' => ['X-Custom-Header'],
  'maxAge' => 3600,
]);
$apiManager->useCORS([
  'allowedOrigins' => ['https://example.com'],
]);

API Response Management ๐Ÿ“‹

APIManager implements the JSON:API (v1.1) specification for response formats, ensuring that your API responses follow a standardized format. This makes it easier to integrate with other services and clients that expect JSON:API-compliant responses:

$responseManager = $apiManager->responseManager();

// Add a message to the response
$responseManager->addMessage('Hello, world!');

// Add an error to the response
$responseManager->addError([
  'status' => "422",
  'source' => ['pointer' => '/data/attributes/first-name'],
  'title' => 'Invalid Attribute',
  'detail' => 'First name must contain at least three characters.',
]);

// Respond with data
$responseManager->respond(true, ['some key' => 'some value']); // Successful response

// Respond with an error
$responseManager->respond(false, [], 400); // Error response with optional status code

Rate Limiting ๐Ÿ“Š

Rate limiting works out of the box with no configuration needed. Simply calling useRateLimiter() will automatically protect your pages from excessive requests. You can customize the configuration if needed, but the default settings are designed to work without any additional setup:

$apiManager->useRateLimiter();
$apiManager->useRateLimiter([
  'id' => 'api_limit',
  'policy' => 'sliding_window',
  'limit' => 100,
  'interval' => '1 minute',
]);

CSRF Protection ๐Ÿ›ก๏ธ

$apiManager->useCsrfManager();

Automatic Security Headers and Header Customisation ๐Ÿ›ก๏ธ

// Adding a custom header
$apiManager->addHeader('X-Custom-Header', 'CustomValue');

// Removing or preventing a header
$apiManager->removeHeader('X-Frame-Options');

Input Sanitization ๐Ÿงน

echo $apiManager->sanitizeInput('some input');

Public Methods Overview ๐Ÿ“–

APIManager

  • useCORS(array $config): Configure CORS settings for your API.
  • responseManager(): Get the instance of ApiResponseManager to manage responses.
  • useRateLimiter(array $config): Set up rate limiting for your API.
  • useCsrfManager(): Initialize CSRF protection.
  • useSecurityHeaders(array $headers): Apply security headers to API responses.
  • addHeader(string $name, string $value): Add a custom header to the response.
  • removeHeader(string $name): Remove or prevent a header from being sent in the response.
  • sanitizeInput(string $input, int $maxLength = null): Sanitize and clean input data.

ApiResponseManager

  • addMessage(string $message): Add a message to the response.
  • addError(array $error): Add an error to the response.
  • respond(bool $success, array $data = [], int $statusCode = 200): Send the response to the client with the provided data and status code.

ErrorLogger

  • logError(string $message, array $context = []): Log an error with detailed information.
  • logCritical(string|Throwable $error): Log a critical error or exception.
  • logInfo(string $message): Log an informational message.

HTTP

  • request(string $method, string $uri, array $options = []): Send an HTTP request to the specified URI using the given method with optional configuration. Supports Happy Eyeballs and idempotency key generation for POST and PATCH requests. See Guzzle 7 docs for available configuration.
  • requestAsync(string $method, string $uri, array $options = [], ?LoopInterface $loop = null): The asynchronous version of the request method, returning a promise to be run in an event loop. Supports Happy Eyeballs.
  • get(string $uri, mixed $headers = [], mixed $queryParams = [], mixed $options = []): Send an HTTP GET request with optional headers, query parameters, and options. Logs a warning and discards the body if content is provided.
  • post(string $uri, mixed $body = null, array $headers = [], array $queryParams = [], array $options = []): Send an HTTP POST request with optional body data, headers, query parameters, and options. Automatically detects and formats content type.
  • put(string $uri, mixed $body = null, array $headers = [], array $queryParams = [], array $options = []): Send an HTTP PUT request. Automatically detects content type and adds an idempotency key.
  • delete(string $uri, mixed $headers = [], mixed $queryParams = [], mixed $options = []): Send an HTTP DELETE request. Logs a warning and discards the body if content is provided.
  • patch(string $uri, mixed $body = null, array $headers = [], array $queryParams = [], array $options = []): Send an HTTP PATCH request with automatic content type detection and idempotency key generation.
  • impersonateBrowser(string $method, string $uri, mixed $body = null, array $headers = [], array $queryParams = [], array $options = []): Send an HTTP request that mimics a browser's behavior, including headers, cookies, and redirects. Supported methods include GET, POST, PUT, PATCH, and DELETE.
  • setDefaultHeaders(array $headers): Set default headers to be used for all requests.
  • setBearerToken(string $token): Set a Bearer token for authorization.
  • setBasicAuth(string $username, string $password): Set Basic Authentication credentials with secure password handling.
  • addQueryParameters(array $params): Add global query parameters for all requests.
  • cookieJar(): CookieJar: Retrieve the CookieJar instance for managing cookies.
  • resolveHost(string $host): array: Resolve both IPv4 and IPv6 addresses for the given host using either system DNS or Cloudflare's DNS-over-HTTPS service, depending on configuration.

The following feature flags allow you to customize the behavior of the HTTP client. Some of these features are enabled by default:

  • useHappyEyeballs(bool $enabled): Enable or disable the Happy Eyeballs algorithm for faster connections. (Enabled by default)
  • useRetry(bool $enabled): Enable or disable the retry mechanism with exponential backoff.
  • useDnsCache(bool $enabled): Enable or disable DNS caching.
  • useHttpVersionFallback(bool $enabled): Enable or disable HTTP version fallback (HTTP/3 -> HTTP/2 -> HTTP/1.1). (Enabled by default)
  • useMinTlsVersion(bool $enabled): Enable or disable the enforcement of minimum TLS version 1.2. (Enabled by default)
  • useCloudflareDns(bool $enabled): Enable or disable the use of Cloudflare's DNS resolver.
  • useCookieJar(bool $enabled): Enable or disable the use of a CookieJar for managing cookies. (Enabled by default)
  • useDefaultConfig(bool $enabled): Enable or disable the use of the default APIManager\HTTP Guzzle configuration. (Enabled by default)
  • useEvaluateRequestIntention(bool $evaluate): Enable or disable evaluation of request intention (e.g., to prevent body data on GET or DELETE requests). (Enabled by default)

License ๐Ÿ“„

This package is open-source and available under the Apache 2.0 License.

Contributions ๐Ÿค

Contributions are welcome! Feel free to submit issues and pull requests.

Contact ๐Ÿ’ฌ

For any questions or support, please raise an Issue.

Happy Coding! ๐Ÿ˜„