Libraries tagged by sharding

Cross-origin resource sharing (CORS) middleware & ServiceProvider for Lumen micro-framework.

Go to Download

LinkedIn API PHP SDK with OAuth 2.0 & CSRF support. Can be used for social sign in or sharing on LinkedIn. Examples. Documentation.

Go to Download

The Vimeo module is designed to let you display a gallery of videos from the Vimeo video sharing site. The module also adds a shortcode to embed a Vimeo video into any text field.

Go to Download

This library is to enable cross site origin sharing

Go to Download

Adds mutations for sharing functionality

Go to Download

Moves meta, adds social sharing options and adds rich snippets

Go to Download

Configurable data provider for easy data sharing with external scripts such as Google Tag Manager.

Go to Download

The QR WishList module is designed to make the process of sharing your wish list more convenient and efficient for you and your customers.

Go to Download

Twitter and Facebook sharing meta tags for Magento 2

Go to Download

Plugin to allow login via an nonce, created by an api call, to avoid the sharing of credentials when multiple people use the same account.

Go to Download

Fenom Bridge for Laravel 5. Package for sharing template engines Fenom and Blade.

Go to Download

Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application

Go to Download

Tophy - Extensible PhoTOgraPHY platform for sharing image galleries and a journal.

Go to Download

### Introduction Use the Numeno Article Recommender API to get personalized article recommendations in three easy steps: 1. Define a Persona: Simply provide a description of your interests, vibe, and target audience. 2. Associate the Persona with a Feed. 3. Pull from the Feed to receive a curated selection of articles from across the web. ### Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/), allowing cross-domain communication from the browser. All responses have a wildcard same-origin policy which makes them accessible from any code on any site.

Go to Download

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