Libraries tagged by wikiseda

webignition/internet-media-type

11 Favers
134414 Downloads

PHP model of an http://en.wikipedia.org/wiki/Internet_media_type

Go to Download


mediawiki/oauthclient

11 Favers
105112 Downloads

PHP OAuth client for use with Wikipedia and other MediaWiki-based wikis running the OAuth extension

Go to Download


mediawiki/core

4169 Favers
3045 Downloads

Free software wiki application developed by the Wikimedia Foundation and others

Go to Download


wikibase/wikibase

129 Favers
10608 Downloads

Structured data repository for MediaWiki

Go to Download


wikibase/data-model-services

3 Favers
154736 Downloads

Services around the Wikibase DataModel

Go to Download


professional-wiki/wikibase-local-media

12 Favers
2394 Downloads

Adds the local media data type to Wikibase

Go to Download


professional-wiki/wikibase-edtf

7 Favers
6776 Downloads

Adds the EDTF data type to Wikibase

Go to Download


wikimedia/toolforge-bundle

13 Favers
17278 Downloads

Symfony bundle providing useful Toolforge features.

Go to Download


wikimedia/smash-pig

3 Favers
24551 Downloads

The open source PHP flexible payments library and frontend/backend mediator.

Go to Download


wikimedia/lucene-explain-parser

0 Favers
72178 Downloads

Parsing and pretty-printing Lucene explain data

Go to Download


wikimedia/avro

0 Favers
949497 Downloads

A library for using Apache Avro with PHP.

Go to Download


paypaplane/svix-client

0 Favers
10048 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.

Go to Download


wikimedia/wikipedia-preview

64 Favers
0 Downloads

Shows Wikipedia article preview in a popup

Go to Download


survos/wikidata

0 Favers
354 Downloads

A PHP client for working with Wikidata API.

Go to Download


illuminated/wikipedia-grabber

46 Favers
7262 Downloads

Wikipedia/MediaWiki Grabber for Laravel.

Go to Download


<< Previous Next >>