Libraries tagged by api logging

Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.

Go to Download

Client PHP fail-open pour l'API d'ingestion Observateur

Go to Download

Laravel package for communicating with Timber (timber.io) logger API

Go to Download

Send global Laravel 13 errors to email using the Brevo API

Go to Download

Ornata: A user-friendly crafted PHP MVC framework, empowering developers to build elegant and powerful web applications.

Go to Download

Moesif Collection/Data Ingestion Middleware for Symfony1.4

Go to Download

Bundle for Moesif Symphony integration

Go to Download

Moesif Collection/Data Ingestion Middleware for Slim Framework

Go to Download

An PHP Light-weight Wechat API

Go to Download

This project extends the Application Insights API surface to support PHP.

Go to Download

A PSR-4 compatible logger for sending messages to Telegram via Bot API.

Go to Download

Enterprise-grade Laravel Package for Lighthouse GraphQL with Sanctum Authentication, Spatie Permissions, Multi-Tenancy, 2FA, and Audit Logging

Go to Download

A comprehensive Laravel starter project with pre-configured packages, interactive setup, and common functionality for rapid application development

Go to Download

Cure your Laravel exception handling headaches. Manage errors, rate limits, and API responses using clean, declarative PHP 8.4 attributes.

Go to Download

Google Cloud Client Library that doesn't conflict against google/apiclient

Go to Download