Libraries tagged by locum

Export documents to YAML, so that they can be used in fixtures

Go to Download

This TYPO3 extension creates restructured files to document the API

Go to Download

A purely PHP library for indexing and searching documents against an Apache Solr installation

Go to Download

Replace variables in docx document

Go to Download

The API comes free of charge with your ShootProof account and currently is only available in the form of JSON responses. Read up on the API documentation to discover the different methods that are available.

Go to Download

PHPExcel - OpenXML - Read, Create and Write Spreadsheet documents in PHP - Spreadsheet engine

Go to Download

ODT document generator (plugin replacement for cybermonde/odtphp)

Go to Download

LinkedIn API PHP SDK with OAuth 2.0 & CSRF support. Can be used for social sign in or sharing on LinkedIn. Examples. Documentation.

Go to Download

Roadiz sub-package which generates Markdown documentation skeleton based on your schema

Go to Download

PHP PDF library for generating and importing PDF documents. A component of the Pop PHP Framework

Go to Download

TCPDF is a PHP class for generating PDF documents and barcodes.

Go to Download

PHPVisio - Read, Create and Write Diagrams documents in PHP

Go to Download

Redis ODM (Object Document Mapper) for Symfony - store and retrieve PHP objects using Redis

Go to Download

By Square document encoding, parsing and rendering utilities

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