Libraries tagged by Best-Practices
mohamedhekal/laravel-vulnerability-audit
0 Downloads
A comprehensive security audit package for Laravel applications that scans for vulnerabilities, weak configurations, and security best practices.
me12free/laravel-mpesa-stkpush-sandbox
1 Downloads
A free Laravel package for integrating M-Pesa STK Push (sandbox/testing) with best practices.
mbox/back-core
21 Downloads
A powerful and modular backend core to kickstart your projects with essential functionalities. Includes authentication, role management, database utilities, and more, all designed to save development time and ensure best practices.
mazatian/phpstan-strict-rules
2 Downloads
A set of additional rules for PHPStan based on best practices followed at TheCodingMachine
maplephp/maplephp
3 Downloads
MaplePHP is a high performance PHP framework built on PSR standards and modern best practices.
lochmueller/portal
1 Downloads
Easy to use portal framework with many best practices. Ready to use portal/intranet for TYPO3!
lmendes/symfony-skeleton
2 Downloads
A production-ready Symfony skeleton with Docker, CI/CD, and best practices
kruegge82/jumingo
31 Downloads
## 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).
kanopi/saplings-launch
581 Downloads
Configures best practices for launching modern Drupal.
justintime50/styles
3303 Downloads
A collection of style guides and best practices used for my projects and teams.
jnbn/composer-json-fixer
27 Downloads
A tool for fixing and cleaning up `composer.json` file according to its schema and best practices.
jeffpascal/php-bootstrap
0 Downloads
Starting point if you want to bootstrap a project in PHP following best practices.
insideapps/ddd-iacontext
181 Downloads
Provides SDD context for AI models.Guidelines, best practices for Symfony projects Hexagonal
insideapps/application
15 Downloads
Symfony6 structure for DDD,IA rules,best practices, user management, notifications and more...
hotash/filastkit
0 Downloads
A modern Filament Laravel starter kit with best practices and developer tools.