Libraries tagged by api validation

Official PHP SDK for the NaprawKSeF API (KSeF XML validation, FA(3) correction builder, webhooks). Zero non-stdlib runtime dependencies; works with Laravel, Symfony and plain PHP.

Go to Download

Symfony bundle for integrating JSON Schema validation with API Platform OpenAPI documentation via dynamic schema aggregation

Go to Download

Official PHP SDK for VerifyKit - Email validation and verification API

Go to Download

Official PHP client for ip-api.io — IP geolocation, email validation, fraud detection and risk scoring API

Go to Download

Advanced validation library with multiple API styles including JSON templates, inline rules, builder pattern, and functional composition. Features 50+ built-in validators, dot notation for nested objects, field reference resolution, and internationalization support. Zero dependencies, fully synchronous, and designed for maximum developer experience with extensible custom rule system.

Go to Download

PHP SDK for the HLR Lookup API - HLR, MNP, and Number Validation lookups

Go to Download

Heureka shopping cart API - Bestfornet fork with Depot API codes and tolerant price validation

Go to Download

A PHP library for integrating with the VAT Sense API in WordPress, providing VAT validation, tax rate information, and currency conversion. Features WordPress transient caching and WP_Error support.

Go to Download

PHP SDK for the Postio API — UK address, email, and phone validation. PAF + Ordnance Survey backed. PSR-18 over Guzzle.

Go to Download

This bundle provides an email validation through 'Bulk Email Checker' api.

Go to Download

API Wrapper for smarty streets address validation services

Go to Download

A Symfony 2 bundle for using HMAC validation tokens for use with API.

Go to Download

Fluent API testing for Symfony with JSON Schema validation, container mocking, and in-memory infrastructure swaps.

Go to Download

## About With the JUMINGO shipping API you can import your shipments into your JUMINGO account from any source. The functionalities of the API include creating and updating shipment drafts, fetching suitable shipment rates for a given shipment and purchasing shipping labels. Furthermore, you can retrieve tracking data and fetch shipping labels and documents for all your purchased shipments. The current main purpose of the API is to connect your account to e-commerce systems and marketplaces. ## General The API is organized around REST. Our API has resource-oriented URLs and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs. All API requests must be made over HTTPS. Calls made over plain HTTP will return errors. Request data is passed to the API as JSON objects and JSON is also returned by all API responses, including errors, although our API SDKs convert requests and responses to appropriate language-specific objects. Best practice usage of the API and business logic is described in the supplementary [integration guide](https://www.jumingo.com/cms/JUMiNGO_API-integration-guide.pdf "JUMiNGO API Integration Guide"). ## Base URL The base URL for all calls is: `https://api.jumingo.com/v1` ## HTTP status codes HTTP response codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error on the client side (e.g. a required parameter is missing). Codes in the `5xx` range indicate an error with our servers. Each error should provide an error code and an error message with further information. HTTP status code | Description ---------------- | ----------- 200, 201, 204 - OK | Everything worked. 400 - Bad Request | The request was unacceptable, often due to missing a required parameter or a validation error. 401 - Unauthorized | No valid API key has been provided or your account is disabled. 403 - Forbidden | You are not allowed to talk to this endpoint. This can either be due to a wrong authentication or when you’re trying to reach an endpoint that your account isn’t allowed to access. 404 - Not Found | The requested resource doesn’t exist. 500, 502, 503, 504 - Server Errors | Something went wrong on our side. Please contact our support if you receive this error. ## Authentication All API requests requires authentication. Unauthorized calls will return errors. Authenticate by including your API key in the `X-AUTH-TOKEN` HTTP header of each API call, e.g.: `X-AUTH-TOKEN: INSERT_YOUR_API_KEY` You can find your API key in your JUMINGO user account. You can get access to the JUMiNGO customer API by enabling it in your [user account](https://www.jumingo.com/de-de/users/connections/create/8). After activation, you will get your personal API key. ## Date/Time Format All values of type `string ` are defined in a specific [RFC 3339](https://tools.ietf.org/html/rfc3339#section-5.6) format and must also be formatted accordingly for requests. The format is: YYYY-MM-DD hh:mm:ss Example: 2018-07-26 15:54:13 All dates and times are specified in UTC (Coordinated Universal Time).

Go to Download

Headless multi-step wizard package for Laravel with FormRequest validation, progress tracking, and frontend-agnostic API

Go to Download