nordlet / sdk
Nordlet PHP Library
Requires
- php: ^8.1
- ext-json: *
- php-http/discovery: ^1.0
- php-http/multipart-stream-builder: ^1.0
- psr/http-client: ^1.0
- psr/http-client-implementation: ^1.0
- psr/http-factory: ^1.0
- psr/http-factory-implementation: ^1.0
- psr/http-message: ^1.1 || ^2.0
Requires (Dev)
- friendsofphp/php-cs-fixer: 3.5.0
- guzzlehttp/guzzle: ^7.4
- phpstan/phpstan: ^1.12
- phpunit/phpunit: ^12.5.22
This package is not auto-updated.
Last update: 2026-08-01 10:10:06 UTC
README
The Nordlet PHP library provides convenient access to the Nordlet APIs from PHP.
Table of Contents
Requirements
This SDK requires PHP ^8.1.
Installation
composer require nordlet/nordlet
Usage
Instantiate and use the client with the following:
<?php namespace Example; use Nordlet\NordletClient; use Nordlet\Reference\Requests\PostV1ReferenceExchangeRatesSyncRequest; $client = new NordletClient( token: '<token>', ); $client->reference->postV1ReferenceExchangeRatesSync( new PostV1ReferenceExchangeRatesSyncRequest([]), );
Environments
This SDK allows you to configure different environments for API requests.
The SDK defaults to the `Production` environment. To use a different environment, pass it to the client constructor: ```php use Nordlet\NordletClient; use Nordlet\Environments; $client = new NordletClient( token: '<YOUR_TOKEN>', options: [ 'baseUrl' => Environments::Staging->value ] );
Available environments:
Environments::Production
## Exception Handling
When the API returns a non-success status code (4xx or 5xx response), an exception will be thrown.
```php
use Nordlet\Exceptions\NordletApiException;
use Nordlet\Exceptions\NordletException;
try {
$response = $client->reference->postV1ReferenceExchangeRatesSync(...);
} catch (NordletApiException $e) {
echo 'API Exception occurred: ' . $e->getMessage() . "\n";
echo 'Status Code: ' . $e->getCode() . "\n";
echo 'Response Body: ' . $e->getBody() . "\n";
// Optionally, rethrow the exception or handle accordingly.
}
Advanced
Custom Client
This SDK is built to work with any HTTP client that implements the PSR-18 ClientInterface.
By default, if no client is provided, the SDK will use php-http/discovery to find an installed HTTP client.
However, you can pass your own client that adheres to ClientInterface:
use Nordlet\NordletClient; // Pass any PSR-18 compatible HTTP client implementation. // For example, using Guzzle: $customClient = new \GuzzleHttp\Client([ 'timeout' => 5.0, ]); $client = new NordletClient(options: [ 'client' => $customClient ]); // Or using Symfony HttpClient: // $customClient = (new \Symfony\Component\HttpClient\Psr18Client()) // ->withOptions(['timeout' => 5.0]); // // $client = new NordletClient(options: [ // 'client' => $customClient // ]);
Retries
The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).
A request is deemed retryable when any of the following HTTP status codes is returned:
The retryStatusCodes configuration controls which 5XX status codes are retried:
legacy(default): Retries408,429, and all>= 500recommended: Retries408,429,502,503,504only (excludes500 Internal Server Errorto avoid retrying non-idempotent failures)
Use the maxRetries request option to configure this behavior.
$response = $client->reference->postV1ReferenceExchangeRatesSync( ..., options: [ 'maxRetries' => 0 // Override maxRetries at the request level ] );
Timeouts
The SDK defaults to a 30 second timeout. Use the timeout option to configure this behavior.
$response = $client->reference->postV1ReferenceExchangeRatesSync( ..., options: [ 'timeout' => 3.0 // Override timeout at the request level ] );
Contributing
While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!
On the other hand, contributions to the README are always very welcome!