Libraries tagged by example

An example of using js widgets jQWidgets. Exchange with the server is implemented using AJAX technology. The server part is written in PHP according to the MVC scheme.

Go to Download

Test example for package sergechurkin/cform

Go to Download

Example package.

Go to Download

**API Version**: 1.7 **Date**: 9th July, 2024 ## 📄 Getting Started This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. Every API call is established on which specific request type (GET, POST, PUT, DELETE) will be used. The API must not be abused and should be used within acceptable limits. To start using this API, you will need not create or access an existing Segnivo account to obtain your API key ([retrievable from your account settings](https://messaging.segnivo.com/account/api)). - You must use a valid API Key to send requests to the API endpoints. - The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources. - The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key or with details in the message key. ### 🔖 **Need some help?** In case you have questions or need clarity with interacting with some endpoints feel free to create a support ticket on your account or you can send an email ([[email protected]](https://mailto:[email protected])) directly and we would be happy to help. --- ## Authentication As noted earlier, this API uses API keys for authentication. You can generate a Segnivo API key in the [API](https://messaging.segnivo.com/account/api) section of your account settings. You must include an API key in each request to this API with the `X-API-KEY` request header. ### Authentication error response If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code. ## Rate and usage limits API access rate limits apply on a per-API endpoint basis in unit time. The limit is 10k requests per hour for most endpoints and 1m requests per hour for transactional/relay email-sending endpoints. Also, depending on your plan, you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code or HTTP 403 if sending credits have been exhausted. ### 503 response An HTTP `503` response from our servers may indicate there is an unexpected spike in API access traffic, while this rarely happens, we ensure the server is usually operational within the next two to five minutes. If the outage persists or you receive any other form of an HTTP `5XX` error, contact support ([[email protected]](https://mailto:[email protected])). ### Request headers To make a successful request, some or all of the following headers must be passed with the request. | **Header** | **Description** | | --- | --- | | Content-Type | Required and should be `application/json` in most cases. | | Accept | Required and should be `application/json` in most cases | | Content-Length | Required for `POST`, `PATCH`, and `PUT` requests containing a request body. The value must be the number of bytes rather than the number of characters in the request body. | | X-API-KEY | Required. Specifies the API key used for authorization. | ##### 🔖 Note with example requests and code snippets If/when you use the code snippets used as example requests, remember to calculate and add the `Content-Length` header. Some request libraries, frameworks, and tools automatically add this header for you while a few do not. Kindly check and ensure yours does or add it yourself.

Go to Download

Example package for Bagisto.

Go to Download

Simple OOP example explained as animals

Go to Download

Example of API versioning on Symfony Framework v4

Go to Download

Acme example plugin for Sylius.

Go to Download

Example EXT:container elements

Go to Download

This is a simple javascript loader with additions properties, See example for more details

Go to Download

Form Component V1 is Magento 2 example to add simple field(s) in form through data provider

Go to Download

ZF2 Module that utilize example of modelling with Zend\Db

Go to Download

Basic form management package for front-facing forms on the Inertia/Vue stack for Laravel. Install to add the vue components for admin and the forms themselves, migrations models controllers factories seeders unittests and dusk tests for the forms and all subtables, and routes for user submission and admin pages. The goal for development is to be able to seemlessly add form management to your Laravel site's admin quickly while remaining an open-ended solution with predictable early stage design choices (i.e. hold on tight). Development is here -> "Can install on any project" ->- "Can seed and display an example on any project" -- "Can integrate Unit and Dusk tests on any project" --

Go to Download

Project Example

Go to Download

A JSON dot.notation parser to access values. Example: persons.2.hobby

Go to Download