Download the PHP package andy87/php-client-avito without Composer

PHP Client for Avito Public API

Russian documentation

Typed PHP client for the Avito Public API. The package provides a main ApiClientAvito entry point, generated provider sections, request prompt DTOs, response DTOs, and schema classes.

The client is built on top of andy87/php-client-sdk and targets PHP 8.1 or newer.

Requirements

• PHP 8.1 or newer
• Composer
• Avito application credentials: client ID and client secret

Installation

Install the package with Composer:

Release v0.9.2 is published on Packagist as andy87/php-client-avito.

Compatibility

Version v0.9.2 targets PHP 8.1 or newer and requires andy87/php-client-sdk:v0.7.0. Composer resolves the SDK dependency automatically when the package is installed.

Quick Start

Create a client from an array and call a generated API method:

ApiClientAvito exposes provider sections lazily through properties such as user, item, messenger, autoload, deliverySandbox, and others generated from the Avito OpenAPI specifications.

Additional Documentation

• Integration service example - framework-agnostic AvitoService, constructor injection, ApiClientAvito setup, client credentials authorization, and token cache configuration.

Working with Prompts

Generated prompt DTOs are filled through public properties. Create a prompt object first, then assign request values directly to its fields.

Do not pass request data as a constructor array:

For API methods without parameters, create an empty prompt and pass it to the provider method:

Configuration

You can pass configuration as an array:

If you need to compose the API URL from parts, use protocol, host and prefix. An explicit baseUrl still has priority:

You can also use environment variables:

By default, AvitoConfig::fromEnv() reads:

• AVITO_CLIENT_ID
• AVITO_CLIENT_SECRET

For multiple credential sets, pass a suffix:

This reads AVITO_CLIENT_ID_CURIES and AVITO_CLIENT_SECRET_CURIES.

Responsibility Boundaries

The package handles the technical Avito API client layer:

• requesting an access token for client_credentials;
• adding the Authorization: Bearer ... header;
• caching the token in the current PHP process;
• connecting an external token cache through CacheInterface;
• refreshing authorization and retrying the original request after 401;
• replacing the authorization strategy through SDK interfaces.

The application usually owns the integration layer around the client:

• storing clientId and clientSecret in environment variables, a secret manager, or framework configuration;
• registering ApiClientAvito and an application service in DI/container;
• choosing an external token cache for production workloads;
• implementing business methods over generated providers;
• handling authorization_code flows, including redirect, code, refresh token, and per-user token storage.

OAuth Token

ApiClientAvito uses client credentials automatically for authorized generated API calls. You do not need to call /token manually before each regular API request.

Manual token endpoint calls are useful for diagnostics, credential checks, or specific OAuth scenarios:

Events and Headers

ApiClientAvito supports shared runtime options from andy87/php-client-sdk: default request headers and event listeners. Runtime state is stored once on the client and is shared with all provider sections, including providers that were already created lazily.

If you use the default HTTP transport, pass runtime options as the second constructor argument:

If you pass a custom transport as the second argument, pass runtime options as the fourth argument:

You can also change headers and attach listeners after client creation:

Available events:

• ApiClientAvito::EVENT_AFTER_INIT - fires after client initialization. Event object: AfterInitEvent with $client.
• ApiClientAvito::EVENT_BEFORE_REQUEST - fires before transport sends the request. Event object: BeforeRequestEvent with $provider, $prompt, and mutable $request.
• ApiClientAvito::EVENT_AFTER_REQUEST - fires after the raw HTTP response is converted to the typed response DTO. Event object: AfterRequestEvent with $provider, $prompt, $request, $httpResponse, and $response.
• ApiClientAvito::EVENT_REQUEST_EXCEPTION - fires when transport, response JSON parsing, or response DTO construction throws. Event object: RequestExceptionEvent with $provider, $prompt, nullable $request, and $exception.

Each event option accepts either one callable or a list of callables:

Header names are merged case-insensitively. The request starts with Accept: application/json, then client headers are applied, then authorization headers are applied. Authorization headers override default client headers, and EVENT_BEFORE_REQUEST listeners can mutate the final HttpRequest before it is sent.

HTTP responses with status 400 or higher are still converted into response DTOs and dispatch EVENT_AFTER_REQUEST. EVENT_REQUEST_EXCEPTION is only for thrown exceptions.

Authorization and Diagnostics Options

ClientCredentialsAuthorizationStrategy refreshes the token and retries the original API request once after 401 by default. You can override or disable refresh statuses:

Pass an SDK CacheInterface through options when the default OAuth strategy must store tokens in an external TTL store. This keeps the Avito client independent from Redis, Yii2, Symfony or any other framework:

For Redis, file cache, DB cache or framework cache, use any object implementing and_y87\PhpClientSdk\Contracts\Cache\CacheInterface, or the SDK adapter when the storage is PSR-16/simple-cache compatible.

Use authorizationResolver when a generated prompt needs a different auth strategy:

Enable TraceableTransport with traceableTransport => true to inspect requests and responses:

Mock Testing

Generated prompts can be mocked by class through andy87/php-client-sdk. This keeps tests independent from generated URL grouping:

Providers and Generated API

The root namespace is:

Main classes:

• and_y87\php_client_avito\ApiClientAvito - main client with lazy provider access.
• and_y87\php_client_avito\AvitoConfig - connection configuration.
• and_y87\php_client_avito\BaseAvitoProvider - base provider for generated API sections.

Generated classes are placed under:

• and_y87\php_client_avito\Generated\Provider
• and_y87\php_client_avito\Generated\Prompt
• and_y87\php_client_avito\Generated\Response
• and_y87\php_client_avito\Generated\Schema

You can inspect available top-level provider names at runtime:

You can access a provider either by property or by name:

Errors and Exceptions

The client and generated methods may throw:

• InvalidArgumentException when required configuration or prompt data is missing or invalid.
• RuntimeException when authorization or an HTTP request fails.
• UnexpectedValueException when required successful response fields are missing.
• OutOfBoundsException when an unknown provider or operation group is requested.

License

MIT. See composer.json for the package license declaration.