Libraries tagged by free api

iptrace/iptrace-php

0 Favers
1 Downloads

Free IP to Geolocation API.

Go to Download


aalfiann/pubproxy-class-php

1 Favers
198 Downloads

Get working public proxy list for free by PubProxy (No API key required).

Go to Download


ralphg6/hadassar

1 Favers
215 Downloads

A simple RESTful API framework for Fat-Free Framework

Go to Download


mrl22/puresms-sdk

2 Favers
0 Downloads

An unofficial, dependency-free PHP client for the PureSMS API.

Go to Download


thinwrap/llm

1 Favers
1 Downloads

Unified, SDK-free PHP facade over LLM chat & embeddings APIs — OpenAI, Anthropic, Bedrock, Gemini and 14 more behind one typed interface. Stateless, no vendor SDKs; BYO PSR-18 HTTP client, with php-http/discovery as the only runtime dependency (auto-wires a client when none is injected).

Go to Download


routiller/routiller

0 Favers
2 Downloads

Laravel-like REST API routing for WordPress plugins. Conflict-free, multi-plugin safe.

Go to Download


zeroad.network/token

0 Favers
37 Downloads

An HTTP-header-based "access / entitlement token" library for Zero Ad Network partnering sites using PHP

Go to Download


zapmail/zapmail

2 Favers
30 Downloads

Official ZapMail API library client for PHP

Go to Download


tooljoom/imageoptimizer

0 Favers
18 Downloads

Optimize images using the free 'resmush.it' service.

Go to Download


shiftechafrica/net-bill-360-php-sdk

3 Favers
46 Downloads

Library for NetBill360 Api Triggers. Use this to manage your ISP clients and network devices.

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


s1syphos/kirby3-gesetze

0 Favers
18 Downloads

Linking german legal norms for Kirby v3, dependency-free & GDPR-friendly

Go to Download


reiterus/informer-magento

2 Favers
4 Downloads

Get Magento 2 store information from REST API endpoints

Go to Download


portospire/suitecrmclient

2 Favers
18 Downloads

A free client library for use with SuiteCRM to abstract the various API usage to enable easier integrations. Provided by PortoSpire

Go to Download


olegv/sheets

2 Favers
3 Downloads

Google sheets manager

Go to Download


<< Previous Next >>