Libraries tagged by api resources

omalizadeh/laravel-api-response

4 Favers
612 Downloads

Basic and standard api response format for laravel using json resources

Go to Download


wurfl/wurfl-api

11 Favers
127001 Downloads

WURFL, the Wireless Universal Resource FiLe, is a Device Description Repository (DDR), i.e. a software component that maps HTTP Request headers to the profile of the HTTP client (Desktop, Mobile Device, Tablet, etc.) that issued the request

Go to Download


sinemacula/laravel-resource-exporter

0 Favers
4103 Downloads

A versatile Laravel package for exporting JsonResource and JsonResourceCollection objects into various formats with customizable drivers.

Go to Download


edfi/resources

2 Favers
21533 Downloads

The Ed-Fi ODS / API enables applications to read and write education data stored in an Ed-Fi ODS through a secure REST interface. *** > *Note: Consumers of ODS / API information should sanitize all data for display and storage. The ODS / API provides reasonable safeguards against cross-site scripting attacks and other malicious content, but the platform does not and cannot guarantee that the data it contains is free of all potentially harmful content.* ***

Go to Download


yaangvu/laravel-base

8 Favers
10519 Downloads

Laravel API Resource Base

Go to Download


netsells/laravel-resourceful

2 Favers
40809 Downloads

Laravel API Resources supercharged to get rid of N+1 problems.

Go to Download


paypaplane/svix-client

0 Favers
14391 Downloads

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download


tunecino/yii2-nested-rest

47 Favers
14954 Downloads

Adds nested resources routing support along with related actions and relationship handlers to the Yii RESTful API framework

Go to Download


tiagomichaelsousa/laravelresources

158 Favers
13521 Downloads

Laravel Resources is a speed-up development package that allows you to create a boilerplate for Laravel apps with a default API structure.

Go to Download


nabilhassen/laravel-usage-limiter

155 Favers
677 Downloads

A laravel package to manage and limit usages/seats by plan, users, or other models

Go to Download


microweber-deps/laravel-cors

1 Favers
58213 Downloads

Fork of fruitcake/laravel-cors Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application

Go to Download


manish-pareek/laravel-cors

0 Favers
7730 Downloads

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

Go to Download


jsor/hal-client

24 Favers
25224 Downloads

A lightweight client for consuming and manipulating Hypertext Application Language (HAL) resources.

Go to Download


gener1c-code/oauth2-server

0 Favers
5663 Downloads

A lightweight and powerful OAuth 2.0 authorization and resource server library with support for all the core specification grants. This library will allow you to secure your API with OAuth and allow your applications users to approve apps that want to access their data from your API.

Go to Download


chervand/yii2-oauth2-server

15 Favers
22962 Downloads

OAuth 2.0 server for Yii 2.0 with MAC tokens support.

Go to Download


<< Previous Next >>