Libraries tagged by support-ticket

shaz3e/support-ticket

0 Favers
6 Downloads

Customer Support Ticket System

Go to Download


tishmalo/escalation-matrix

0 Favers
12 Downloads

Escalation Matrix Package for Laravel

Go to Download


srayner/cobalt

3 Favers
7 Downloads

ICT Asset and Project Management Application

Go to Download


pliic/pliic-php

0 Favers
15 Downloads

Official PHP SDK for the Pliic feedback and support platform: typed API client, end-user token minting, and webhook signature verification.

Go to Download


paksuco/lara-ticket

0 Favers
10 Downloads

A laravel 5 package to handle 'support ticket', a fork from sdkcodes/lara-ticket

Go to Download


lenz/shopware-account-api

1 Favers
3 Downloads

Standalone PHP client for the Shopware Account / Store (SBP) API: authentication, plugins, support tickets, provisions and statistics.

Go to Download


evangeo/tickets

1 Favers
12 Downloads

Ticket Support System

Go to Download


yezzmedia/laravel-user-support

0 Favers
11 Downloads

User-facing support ticket system with public contact form, legal pages, and operator-managed conversations for the Yezz Media Laravel platform.

Go to Download


visio/support

0 Favers
19 Downloads

FilamentPHP 3 plugin for partner support ticket system

Go to Download


stellarsecurity/support-client-laravel

0 Favers
28 Downloads

Laravel HTTP client for Stellar Security Support Ticket API

Go to Download


segnivo/php-sdk

0 Favers
0 Downloads

**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


quendistudio/support

0 Favers
1 Downloads

Backend support ticket system for Winter CMS

Go to Download


nitsan/ns-helpdesk

0 Favers
253 Downloads

TYPO3 Helpdesk Extension - Manage customer support with the all-in-one TYPO3 Help Desk extension. This user-friendly tool lets you set up a support help desk quickly with support tickets, providing a dedicated dashboard, ticketing system, email notifications, restricted access, and options for file and media uploads.

Go to Download


justinholtweb/craft-csr

0 Favers
0 Downloads

A public knowledge base and support ticketing desk for Craft CMS 5 — articles that deflect tickets before they are raised, failed-search analytics, SLAs and canned replies.

Go to Download


idoneo/humano-tickets

0 Favers
5 Downloads

Support tickets management module

Go to Download


<< Previous Next >>