Libraries tagged by ticketit
ticketpark/locale-bundle
13861 Downloads
This bundle adds functionalities to simplify the handling of localized strings
ticketpark/image-bundle
14581 Downloads
This bundle assists in manipulating images
ticketpark/fixtures-autoload-bundle
4841 Downloads
Simplifies loading doctrine fixtures
ticketpark/expiring-url-bundle
5092 Downloads
Create urls which expire after a certain period.
ticketbureau/yii2-seatwave-api
279 Downloads
Yii 2 Seatwave API extension. http://www.yiiframework.com
vortechstudio/laravel-github-issues
4 Downloads
Ce package dédié à laravel permet d'ouvrir un ticket sur github quand une Exception de type Erreur, Critique ou Urgence apparait dans le code, il peut être aider d'openAI pour créer le ticket.
virtual-queue/people-forwarder
1 Downloads
People forwarder for the queue to prevent ticket portal overload
valantic-cec/aijira
16 Downloads
Use OpenAI to generate sprint goals, a sprint review agenda or jira ticket field descriptions.
spanjaan/wn-support-plugin
2 Downloads
A simple ticket system for WinterCMS
snappy/jira
235 Downloads
Snappy application for turning tickets into Jira issues.
snappy/hipchat
250 Downloads
Notify HipChat with tickets or wall posts.
snappy/github
268 Downloads
Convert Snappy tickets into Github issues.
shawnhooper/outdated-to-jira
0 Downloads
Creates JIRA tickets for outdated Composer and npm dependencies.
segnivo/php-sdk
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.
rayenbou/dashboard-bundle
0 Downloads
A Symfony bundle to manage tickets from ticket bundle