Libraries tagged by Match

A cmf router matching the slug to a found commercetools slug.

Go to Download

Laravel Searchy makes user driven searching easy with fuzzy search, basic string matching, Levenshtein Distance and more.

Go to Download

Handy array-reduce functions, like 'are all matching', 'is one matching', 'first matching'

Go to Download

A package to easily make us of more powerful route pattern matching in Laravel.

Go to Download

Detects browser versions, matches .browserslistrc files and serves encore builds accordingly.

Go to Download

Mime-type matching

Go to Download

Tools for facial matchin using AWS Rekognition

Go to Download

This library allows user to calculate the points/magic points that a team has reached after a soccer match. The total can be altered through some bonus like the defense one.

Go to Download

Modifies the filename of a PDF generated from an article to match the article's alias

Go to Download

Useful utilities when dealing with arrays, strings, and matching.

Go to Download

Filter DataObjects created with the DataObjectAsPage module - Allows for multi select and match all filters

Go to Download

Manage matches.

Go to Download

Abstract Path Matcher, lightweight library for matching routes in different formats

Go to Download

# 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

Redirect user to product if sku matches in search and no other results found

Go to Download