Libraries tagged by deleted

Use sdstichtingsd/soft-deleteable-extension-bundle with binary ids

Go to Download

Laravel Cascade Soft Delete & Restore

Go to Download

Media manager for Laravel - browse / create / rename / delete files and folders.

Go to Download

This is a simple cURL library to dispatch HTTP GET, POST, PUT and DELETE request, easily.

Go to Download

This will allow you to quickly move something to cache and then to get it again at a later time if needed. This will purely be done on the disk. It will delete the files use on exit or again on start up of the program. This is mean to quickly store something out of memory and obtain it later again.

Go to Download

The shakib53626/laravel-repository-maker package provides a simple and efficient way to implement the Repository Design Pattern in Laravel projects. With a custom Artisan command (make:repository), developers can automatically generate repository classes with pre-defined methods like index, store, update, and delete. This tool is designed to enhance modularity, promote clean architecture, and save development time.

Go to Download

Get all new files in a specific path, just for see or select them into delete

Go to Download

The SessionForge library is designed to provide developers with a flexible and efficient tool for managing sessions using file manipulation. With SessionForge, you can easily create, read, update, and delete session data stored in files, enabling seamless integration of session management functionality into your applications.

Go to Download

PHP Trait that enables create Read Update Delete operations on PHP classes

Go to Download

Memcached implemented method set|get|delete

Go to Download

PHP RESTful API for mySql supports POST, GET, PUT, DELETE and HEAD, TRACE methods

Go to Download

SmyORM is a PHP Object-relational mapping (ORM) that allows developers to write code in simple programming languages of their choice instead of using SQL to access, add, update, and delete data and schemas in the respective database.

Go to Download

**API Version**: 1.7 **Date**: 9th July, 2024 ## 📄 Getting Started This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. Every API call is established on which specific request type (GET, POST, PUT, DELETE) will be used. The API must not be abused and should be used within acceptable limits. To start using this API, you will need not create or access an existing Segnivo account to obtain your API key ([retrievable from your account settings](https://messaging.segnivo.com/account/api)). - You must use a valid API Key to send requests to the API endpoints. - The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources. - The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key or with details in the message key. ### 🔖 **Need some help?** In case you have questions or need clarity with interacting with some endpoints feel free to create a support ticket on your account or you can send an email ([[email protected]](https://mailto:[email protected])) directly and we would be happy to help. --- ## Authentication As noted earlier, this API uses API keys for authentication. You can generate a Segnivo API key in the [API](https://messaging.segnivo.com/account/api) section of your account settings. You must include an API key in each request to this API with the `X-API-KEY` request header. ### Authentication error response If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code. ## Rate and usage limits API access rate limits apply on a per-API endpoint basis in unit time. The limit is 10k requests per hour for most endpoints and 1m requests per hour for transactional/relay email-sending endpoints. Also, depending on your plan, you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code or HTTP 403 if sending credits have been exhausted. ### 503 response An HTTP `503` response from our servers may indicate there is an unexpected spike in API access traffic, while this rarely happens, we ensure the server is usually operational within the next two to five minutes. If the outage persists or you receive any other form of an HTTP `5XX` error, contact support ([[email protected]](https://mailto:[email protected])). ### Request headers To make a successful request, some or all of the following headers must be passed with the request. | **Header** | **Description** | | --- | --- | | Content-Type | Required and should be `application/json` in most cases. | | Accept | Required and should be `application/json` in most cases | | Content-Length | Required for `POST`, `PATCH`, and `PUT` requests containing a request body. The value must be the number of bytes rather than the number of characters in the request body. | | X-API-KEY | Required. Specifies the API key used for authorization. | ##### 🔖 Note with example requests and code snippets If/when you use the code snippets used as example requests, remember to calculate and add the `Content-Length` header. Some request libraries, frameworks, and tools automatically add this header for you while a few do not. Kindly check and ensure yours does or add it yourself.

Go to Download

laravel-model-affected-rows-verification is a library that extends the default Laravel model to include implicit row count verification for update and delete operations. This ensures that these operations are conducted safely, providing an extra layer of validation to prevent unintended data modifications and enhance the stability of your Laravel applications.

Go to Download

Service for upload files and delete them

Go to Download