Libraries tagged by notes
spryker-feature/customer-notes
518273 Downloads
Customer Notes [feature]
spryker-feature/configurable-bundle-note
213734 Downloads
Configurable Bundle Note [feature]
spryker-feature/cart-notes
518133 Downloads
Cart Notes [feature]
digitalcloud/nova-resource-notes
23120 Downloads
A Laravel Nova Resource Note.
digitalcloud/laravel-model-notes
34113 Downloads
A package to enable assigning notes to Eloquent Models
networkteam/contentcomments
21589 Downloads
A Neos package to add content comments to any node (as communication medium)
webmaniabr/nfse
3546 Downloads
PHP SDK da API de Nota Fiscal de Serviço da Webmania
webmaniabr/nfe
4812 Downloads
PHP SDK da REST API de Nota Fiscal Eletrônica da WebmaniaBR®
zaius/zaius-php-sdk
61127 Downloads
The Zaius SDK for PHP. Validated for use in zaius-magento-2, users in custom environments are encouraged to test and validate thoroughly (and note any issues via the GitHub issue tracker).
rohitkundale/order-comment
8165 Downloads
Allows customer to add a special note/message/comment or instruction while placing an order
rfc/scannable
866 Downloads
Note that this is not a scanner of its own. It is merely an interface that describes a scanner.
rfc/response
861 Downloads
Note that this is not a response of its own. It is merely an interface that describes a response.
rfc/request
860 Downloads
Note that this is not a request of its own. It is merely an interface that describes a request.
paypaplane/svix-client
12922 Downloads
Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [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.
listennotes/podcast-api
5206 Downloads
PHP bindings for the Listen Notes Podcast API