Libraries tagged by acceptance

Includes twig and css templating, js and php logic allowing the display of a cookie acceptance message

Go to Download

A Laravel package for integrating with Cybersource Secure Acceptance Hosted Checkout.

Go to Download

Acceptance test framework for web applications.

Go to Download

Test emails in your Codeception acceptance tests

Go to Download

Test emails in your Codeception acceptance tests

Go to Download

Codeception module for acceptance testing an application that uses Gov.uk Notify

Go to Download

A Magento 2 module that adds the Privacy acceptance checkbox in customer registration page, contact page and newsletter subscription form (retrieving text from Terms and Conditions).

Go to Download

PHPStan Rules to Disallow Float proliferation in contexts where IEEE-754 rounding errors are not acceptable

Go to Download

XML Reader to simplexml/array iterator with low memory usage and an acceptable level of ease of use.

Go to Download

A minimal League/CSV wrapper. Gives the powerful CSV tool an acceptable API. Very opinionated. Used for own projects, so might not fit your case. Just use League/csv.

Go to Download

Development assertion helpers that show acceptable values on failure

Go to Download

Allows you to analyze orders placed and determine which of them are suspected frauds. You can specify the degree of personally acceptable risk or report fali positives and false negatives

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

This is an easy way to check if a email address is acceptable so you can avoid fake/invalid users on your database.

Go to Download

Set a minimum acceptable code coverage in your pipeline

Go to Download