Libraries tagged by specs
tkijewski/php-lnurl
8293 Downloads
PHP implementation of lnurl Spec
spurwork/spectator
1447 Downloads
Testing helpers for your OpenAPI spec
rowbot/url
598562 Downloads
A WHATWG URL spec compliant URL parser for working with URLs and their query strings.
erasys/openapi-php
56949 Downloads
Open API 3.0 builder and validation library for PHP that helps you write valid specs.
api-clients/openapi-client-generator
8267 Downloads
Generate a client based on an OpenAPI spec
kphoen/rulerz-spec-builder
41320 Downloads
Specification builder for RulerZ
fesor/json_spec
42113 Downloads
Easily handle JSON Structures with PhpSpec and Behat
duxet/json_spec
34499 Downloads
Easily handle JSON Structures with PhpSpec and Behat
hanken/phpspec-code-coverage
14581 Downloads
Generate Code Coverage reports for PhpSpec tests
aryeo/papi
15140 Downloads
Powerful API (PAPI) utilities.
magetest/magento-phpspec-extension
65712 Downloads
Magento PHPSpec extension
ybelenko/openapi-data-mocker
12897 Downloads
Library that generates fake data from Swagger 2.0|Openapi 3.0 spec
tuutti/php-klarna-base
74641 Downloads
Klarna API base spec
thewoods96/doc-shamer
1664 Downloads
A basic Laravel Artisan command to check an OpenAPI spec against application API routes to summarise doc coverage
paypaplane/svix-client
4942 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.