Libraries tagged by manage settings

A package to manage global and model based settings

Go to Download

Manage global and model-scoped settings in Laravel with a clean API, artisan commands, and optional per-scope caching.

Go to Download

A package to manage setting of your models.

Go to Download

Tweak: Define and manage settings in your application

Go to Download

Manage wordpress with yaml. Create settings pages and metaboxes for posts and terms. Add pages to admin menu. Register custom post types and taxonomies via config.yaml file. Use it in all ur plugins or themes. Unleash full power of wordpress quickly.

Go to Download

Application languages using Backpack CRUD.

Go to Download

Manage settings package for laravel framework

Go to Download

A foundational package for WordPress to manage settings and forms.

Go to Download

Manage settings easily for your Alfred 3 or 4 Workflows.

Go to Download

The ACF package. A package to manage several different ACF settings, filters and actions.

Go to Download

Manage your business information under Settings, and access it sitewide.

Go to Download

The Flowroute APIs are organized around REST. Our APIs have resource-oriented URLs, support HTTP Verbs, and respond with HTTP Status Codes. All API requests and responses, including errors, will be represented as JSON objects. You can use the Flowroute APIs to manage your Flowroute phone numbers including setting primary and failover routes for inbound calls, and sending text messages (SMS and MMS) using long-code or toll-free numbers in your account.

Go to Download

Manage recurring widgets with the same settings. Made for WordPress.

Go to Download

更方便的管理您的定时任务，实时暂停、启动、修改定时任务的执行时间等等 With this package, you can better manage your multifarious timing tasks, just define an execution entry that can be implemented more flexibly by manipulating database data for timing, opening, closing, setting up time, and so on.Description: the task manager implements the flexibility of multiple processes. After the task is opened, each task takes up a sub process and automatically releases after completion.Preparation: installation extension To implement the multiple processes of PHP, we need two extensions pcntl and POSIX, which can be added at compile time: - enable-pcntl, do not use - disable-pcntl, POSIX is the default installation. PHP multi process modules rely on pcntl extensions

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