Libraries tagged by notes

Snotify is extension implements at server-side notification to the user without client-side.

Go to Download

Order notes for Commerce

Go to Download

Official PHP SDK for the stackin fiscal document API — issue, consult, cancel NF-e and NFS-e.

Go to Download

Magento 2 Customer Note

Go to Download

PHP SDK for the Falcon Fiscal Hub API — issue, query and cancel Brazilian service invoices (NFS-e, padrão nacional)

Go to Download

Pacote em Laravel/Lumen para conexão com a API da danfe.br.com

Go to Download

SDK PHP para emissão de NFS-e Nacional — Laravel ou standalone (sem framework)

Go to Download

PHP toolkit for Ecuador SRI electronic documents: access keys, XML builders, XAdES-BES signing and SOAP delivery.

Go to Download

SDK PHP para la API de Facturacion Electronica SUNAT de Intifact (Peru): facturas, boletas, notas de credito/debito, guias de remision, resumenes diarios.

Go to Download

PDF-Dokumentgenerator

Go to Download

PHP SDK da API de Nota Fiscal de Serviço da Webmania

Go to Download

Sticky Notes for Neos, only visible in the Backend

Go to Download

Generates changelogs from GitHub release notes, merging and de-duplicating entries from multiple repositories if needed

Go to Download

Project & task tracking workspace (projects, tasks, subtasks, assignments, notes, contacts) for Laravel + Inertia applications.

Go to Download

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