Libraries tagged by knet client
wyrimaps/oauth2-bnet
912 Downloads
A Battle.net provider for league/oauth2-client
tsdarky/oauth2-bnet
8 Downloads
A Battle.net provider for league/oauth2-client
relictos/oauth2-bnet
85 Downloads
A Battle.net provider for league/oauth2-client
mehr-als-nix/php-ftp-client
1 Downloads
New FTP Client based on old PEAR Net_FTP
hostingbe/api-client-certificatemanager
55 Downloads
php API REST client to connect to CertificateManager.net API, including logging and retry functionality. CertificateManager supplies you with more than 100 certificates and SSL tools to offer to your clients
jekk0/binlist-php-client
28 Downloads
Composer php client for interact with binlist.net api.
yoerioptr/tabt-api-client
196 Downloads
Helper library for the TabT API by Frenoy. For more information visit 'http://api.frenoy.net/'
tuuz/net
0 Downloads
TuuzNet is a lightweight cURL-based HTTP client library for PHP. Provides clean static interface for GET, POST (JSON/Form/File/Binary), PUT, DELETE requests with customizable headers, timeouts, and SSL configuration.
shiftechafrica/net-bill-360-php-sdk
46 Downloads
Library for NetBill360 Api Triggers. Use this to manage your ISP clients and network devices.
paythemnet/php8_inbound_api_client_baseintegration
2 Downloads
This official PayThem.Net base integration. All other PHP 8.0 clients will extend from here.
paythemnet/inbound_distributor_api_client
9 Downloads
This official PayThem.Net library for direct integration with the PayThem.Net Distributor API. PHP 8.0 and above.
mrpc/biblionet-client
27 Downloads
Client library for the web service of biblionet: https://biblionet.diadrasis.net/webservicetest/
jleagle/btn-api-client
18 Downloads
A helper class to access data from the BTN API
jleagle/battlenet-api-client
89 Downloads
A package to retrieve information from the Battle.net API
interserver/mailbaby-client-php
206 Downloads
**Send emails fast and with confidence through our easy to use [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) API interface.** # Overview This is the API interface to the [Mail Baby](https://mail.baby/) Mail services provided by [InterServer](https://www.interserver.net). To use this service you must have an account with us at [my.interserver.net](https://my.interserver.net). # Mail Orders Every sending account in MailBaby is backed by a **Mail Order** — a provisioned sending credential with a numeric `id` and a corresponding SMTP username (`mb`). Most calls accept an optional `id` parameter; when omitted the API automatically selects the first active order on your account. Use `GET /mail` to list all orders, and `GET /mail/{id}` to inspect a single order including its current SMTP password. # Sending Email Three sending methods are available depending on your use-case: | Endpoint | Best for | |----------|----------| | `POST /mail/send` | Simple single-recipient messages | | `POST /mail/advsend` | Multiple recipients, CC/BCC, attachments, named contacts | | `POST /mail/rawsend` | Pre-built RFC 822 messages (e.g. DKIM-signed payloads) | After a successful send each endpoint returns a `GenericResponse` whose `text` field contains the **transaction ID** assigned by the relay. This ID can later be matched against entries in `GET /mail/log` via the `mailid` query parameter. # Filtering & Logs `GET /mail/log` provides paginated access to every message accepted by the relay for your account. Combine any of the query parameters to narrow results — e.g. `from`, `to`, `subject`, `messageId`, `origin`, `mx`, `startDate`/`endDate`, and `delivered`. # Blocking Two independent mechanisms exist for suppressing unwanted email: - **Block lists** (`GET /mail/blocks`, `POST /mail/blocks/delete`) — addresses flagged by the system spam filters (LOCAL_BL_RCPT / MBTRAP rules in rspamd, and suspicious subjects). - **Deny rules** (`GET /mail/rules`, `POST /mail/rules`, `DELETE /mail/rules/{ruleId}`) — custom rules you configure to reject specific senders, domains, destination addresses, or subject-line prefixes before a message is even attempted. # Authentication In order to use most of the API calls you must pass credentials from the [my.interserver.net](https://my.interserver.net/) site. We support several different authentication methods but the preferred method is to use the **API Key** which you can get from the [Account Security](https://my.interserver.net/account_security) page. Pass your key in the `X-API-KEY` HTTP request header for every protected call.