Libraries tagged by verbum

baghayi/http-verb-extraction

0 Favers
31 Downloads

Zf2 module for extracting http verbs of resources used in Apigility, to their own classes.

Go to Download


actionable/http-verb-condtional-display-shortcode

0 Favers
39 Downloads

A WordPress shortcode that only displays content if page is called with a specific verb (GET/POST/etc)

Go to Download


jamessessford/playing-cards

0 Favers
1 Downloads

A PHP implementation of a deck of playing cards to be used with Verbs

Go to Download


imonroe/corpora

1 Favers
5 Downloads

A PHP-friendly version of the dariusk/corpora javascript library. It provides "[a] collection of small corpuses of interesting data for the creation of bots and similar stuff"

Go to Download


nw/request-limit-bundle

2 Favers
1 Downloads

This bundle provides a light way to restrict user access to some action for a specific time frame

Go to Download


taeluf/rdb

0 Favers
25 Downloads

Custom property getters on beans, better error reporting, sql-verbs as an API. And some other quality of life stuff.

Go to Download


taeluf/lildb

0 Favers
147 Downloads

A simple PDO wrapper with convenience methods for common SQL verbs like insert, update, delete, select

Go to Download


shell/card-management-sdk

0 Favers
2 Downloads

The Shell Card Management API is REST-based and employs OAUTH 2.0,Basic and ApiKey authentication. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes.All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources. The internal workings of the platform are not important when interacting with the API. However, it is worth noting that the platform uses a microservice architecture to communicate with various backend systems and some API calls are processed asynchronously. All endpoints use the POST verb for retrieving, updating, creating and deleting resources in the Shell Card Platform. The endpoints that retrieve resources from the Shell Card Platform allow flexible search parameters in the API request body.

Go to Download


sergiosgc/rest-router

1 Favers
0 Downloads

Filesystem based request router for HTTP verb-aware applications (RESTful)

Go to Download


nodeum-io/nodeum-sdk-php

0 Favers
0 Downloads

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download


alissonlinneker/statuspage-php-sdk

0 Favers
0 Downloads

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download


verumconsilium/laravel-browsershot

113 Favers
420277 Downloads

Browsershot Laravel wrapper to generate PDF files and Screenshots using Headless Chrome

Go to Download


sandromiguel/verum-php

18 Favers
119 Downloads

Server-Side Form Validation Library for PHP

Go to Download


pakled/vernum

0 Favers
19 Downloads

Library that helps creating, editing, sorting and comparing semantic version numbers

Go to Download


vertumnus/skeleton

0 Favers
0 Downloads

Vertumnus Laravel package skeleton

Go to Download


<< Previous Next >>