Weave Code
Core Laravel Package
apimatic/core
Core library for APIMatic-generated PHP SDKs. It supplies shared request construction, query/header/form/body parameter handling, and common utilities so generated clients stay consistent. Supports PHP 7.2 through 8.4; install with composer require apimatic/core.
Core logic and the utilities for the APIMatic's PHP SDKs
Frequently asked questions about Core
- Do I need to install apimatic/core directly in my Laravel app?
- Usually no. It is the runtime substrate that APIMatic-generated PHP SDKs compile against, so it normally arrives as a transitive dependency when you require a vendor's generated SDK. Install it directly only if you are building your own SDK generation pipeline on APIMatic's toolchain. Hand-authoring application code against it is not the intended use case.
- Which PHP and Laravel versions does apimatic/core support?
- The package lists PHP 7.2, 7.4, and 8.0 through 8.4 as supported, which comfortably covers Laravel 8 through Laravel 12 runtimes. The library itself is framework-agnostic and does not require Laravel. Check the constraints of the generated SDK you are consuming as well, because it may pin a narrower range than the runtime does.
- How do I install apimatic/core with Composer?
- Run composer require "apimatic/core" and Composer will add the dependency to your composer.json. It is MIT licensed and PSR-4 autoloaded, so no service provider or extra bootstrap is needed. Because the package is still on 0.x releases, prefer an explicit version constraint rather than an unconstrained require.
- Does apimatic/core work with Laravel's HTTP client, Http::fake(), and middleware?
- No. The package owns its own transport, request and response objects, and error model, so it does not compose with Laravel's Http facade, middleware, Http::retry(), or the event system. Every integration becomes an adapter problem. If you need Laravel-native faking and middleware, keep that surface behind the Http facade and treat the generated SDK as an isolated boundary you wrap.
- How should I pin apimatic/core versions in composer.json?
- Under semver, 0.x releases may introduce breaking changes in minor bumps, so avoid loose constraints. Pin an exact version or a tilde constraint and put a review gate on every bump. Also reconcile the package metadata against the changelog before assuming the dependency is actively maintained.
- Can apimatic/core mask sensitive headers like Authorization in logs?
- Yes, and this is one of its most underrated features. The logging layer ships ApiLogger, LoggingConfiguration, RequestConfiguration, ResponseConfiguration, and LoggerConstants::NON_SENSITIVE_HEADERS, so request and response logging with sensitive-header masking is built in rather than hand-rolled. Still review your configuration explicitly before enabling logging in production, since masking depends on the header list you supply.
- How do I write contract tests for an APIMatic-generated SDK in CI?
- Use the bundled CoreTestCase base class along with the body matchers (RawBodyMatcher, KeysAndValuesBodyMatcher, KeysBodyMatcher, NativeBodyMatcher), HeadersMatcher, and StatusCodeMatcher. These let you pin the exact request shape and status expectations a generated SDK produces, which is useful for catching drift when a vendor ships a new SDK version. They test the SDK's wire behaviour, not your own controllers, so keep them in a separate test suite.
- Is apimatic/core actively maintained, and what if I hit a bug?
- It is a single-vendor project maintained by APIMatic, and public adoption signals are thin because its real consumers are generated SDKs rather than repositories that require it publicly. That means fewer community answers and more time reading source when something breaks. Recent fixes have targeted narrow correctness edges like date deserialization, multipart boolean quoting, and query URL validation, so budget for occasional patching or a pinned fork of your own.
- What are the alternatives to apimatic/core for PHP API integrations?
- If you are not consuming an APIMatic-generated SDK, this is the wrong tool. Use Laravel's Http facade, Guzzle directly, or a wrapper such as Saloon for hand-written integrations. apimatic/core is a generator runtime, not a general-purpose HTTP client, and adopting it outside that context means inheriting an incompatible transport and error model.
- Does apimatic/core handle multipart, query, and date deserialization edge cases correctly?
- It covers the parameter surface well, with discrete classes for query, header, form, body, template, and additional params, plus response handlers and deserializers. The historical bug surface has been in fiddly areas like simple-date parsing, negative RFC3339 timezone offsets, multipart boolean quoting, and query URL validation after global params. Treat those edges as things to verify with contract tests rather than assume.
Weaver
How can I help you explore Laravel packages today?