Libraries tagged by one hour translation

onehourtranslation/api2

7 Favers
35127 Downloads

PHP client library for One Hour Translation API (version 2)

Go to Download


phrase/phrase-php

6 Favers
177099 Downloads

Phrase Strings API Reference. Phrase Strings is a translation management platform for software projects. You can collaborate on language file translation with your team or order translations through our platform. The API allows you to import locale files, download locale files, tag keys or interact in other ways with the localization data stored in Phrase Strings for your account.

Go to Download


eolica/laravel-content-tools

3 Favers
3740 Downloads

A Laravel package for editing your web frontend translations directly on the page

Go to Download


wordpress-premium/polylang-pro

5 Favers
2475 Downloads

With over 500,000 installs, Polylang is the most popular multilingual plugin available on the WordPress directory. You write your posts, pages and create categories and post tags as usual, and assign a language to each of them.

Go to Download


werkraum/deepl-translate-slim

3 Favers
53 Downloads

Translate all your pages on demand, without additional configuration. You do not need to set up more than one language in TYPO3. Enable Translation targets in your site configuration and display a language menu with our Menu Integration and you are ready to go.

Go to Download


karavasilev/cryptomanana

18 Favers
54 Downloads

CryptoManana is a cryptography framework for boosting your project's security.

Go to Download


soufian212/laratransmanager

6 Favers
2 Downloads

Store all your translations on the database and translate them easily with a dashboard

Go to Download


motia/laravel-translations-port

0 Favers
46 Downloads

Import/Export your laravel translations(including the missing ones!) to/from your separate frontend apps.

Go to Download


azenet/translation-keys-bundle

0 Favers
28 Downloads

Allows you to see keys untranslated on your website.

Go to Download


mageinic/translation

0 Favers
2 Downloads

Translation by MageINIC. Advance Translation extension simplifies the process of translating your online store's content. It allows you to manage translations directly from the admin area, eliminating the need to manually edit CSV files. You can configure translations at the store view level, making it easy to offer multilingual support on specific store views.

Go to Download


admica/trans-files

3 Favers
3 Downloads

You can translate your resources/lang files and folders with command lines using google translate, this may save lots of your time if you are working on multilanguage website.

Go to Download


admica/laravel-google-translate-files

3 Favers
27 Downloads

You can translate your resources/lang files and folders with command lines using google translate, this may save lots of your time if you are working on multilanguage website.

Go to Download


guyver4mk/language_translate

0 Favers
11 Downloads

A PHP Class to create a static array of translations, to use on your website

Go to Download


aozisik/translatable

0 Favers
29 Downloads

Translatable is a package that helps you have translatable fields on models. These fields will store your translations in JSON format and will be automatically fetched to your current app locale when you try to reach them. You can also get a specific language of your choice by using certain methods. Please refer to the Github page for further details.

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


Next >>