Libraries tagged by api_platform
botble/api
26482 Downloads
API package for Botble CMS
theodo/accent-bundle
446 Downloads
Access Control Checker Easy Neat Thorough
rekalogika/rekapager-symfony-bridge
1292 Downloads
Common classes for Symfony integration.
jojari/simple-linkedin-php
43203 Downloads
A simple, stand-alone wrapper for the most-used functionality of the LinkedIn API platform
fortress/behat-contexts
17437 Downloads
Behat contexts
dunglas/digital-ocean-bundle
1818 Downloads
DigitalOcean API v2 client for Symfony and API Platform
bitbag/graphql-plugin
4437 Downloads
Sylius backend integration for Vue Storefront 2
api-platform/ramsey-uuid
2153 Downloads
API Platform RamseyUuid bridge
api-platform/json-hal
853 Downloads
API Hal support
api-platform/graphql
5036 Downloads
Build GraphQL API endpoints
api-platform/parameter-validator
1616 Downloads
Validates parameters depending on API-Platform filter description
marghoobsuleman/hashtagcms
771 Downloads
Headless CMS, Use it as Headless CMS or Bundled, API enabled, Admin Panel, Multisite, Multi-platform, Multilingual.The Most powerful, fast and user-friendly platform. Made with PHP Laravel Framework.
shopsys/luigis-box
8641 Downloads
Shopsys Platform connector to Luigi's Box
shopex/prism
16054 Downloads
SDK for shopex prism platform
paypaplane/svix-client
9061 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.