Libraries tagged by IP API
ipdon/ipdon
0 Downloads
IPdon API integration - IP intelligence, served
qubit-hq/verifip
0 Downloads
Official PHP SDK for the VerifIP IP fraud scoring API
tenfef/ipfind-php
317 Downloads
PHP Library to fetch location information from an IP Address
foxliscom/geo
22 Downloads
Get user location by IP using Foxlis Geo API: city, country, subdivisions, continent, etc
apiverve/tordetect
2 Downloads
Tor Node Detector is a Tor exit node checker API: send any IP address and it tells you whether that IP belongs to an active Tor exit node, so you can identify traffic originating from the anonymity network.
ipregistry/ipregistry-php
74 Downloads
Official PHP client library for the Ipregistry IP geolocation and threat data API.
ipregistry/ipregistry-laravel
0 Downloads
Official Laravel integration for the Ipregistry IP geolocation and threat data API.
qasimleoo/whoisfreaks-php
1 Downloads
Complete WhoisFreaks API — WHOIS, DNS, SSL, Geolocation, Typosquatting, IP Intelligence, Domain Reputation, and bulk database downloads. ## Authentication All requests require an `apiKey` query parameter. ## Resources - Docs: https://whoisfreaks.com/documentation - Billing: https://billing.whoisfreaks.com - Support: [email protected]
weijiajia/http-proxy-manager
46 Downloads
A Laravel package for managing HTTP proxies from various proxy service providers with a unified API
update-gip2/up-geoip2
11 Downloads
MaxMind GeoIP2 PHP API
sfere-io/sfere-laravel
2 Downloads
Sfere server SDK for Laravel: server-to-server event collection that forwards the end user's IP, user agent and ad click IDs
sahicheck/sahicheck-laravel
1 Downloads
Official Laravel integration for the SahiCheck verification API
redeyed/sdk
0 Downloads
Official Redeyed API client for PHP — AI tools, Sentinel human verification & IP reputation. Free to install; requires a Redeyed API key to activate.
rdapapi/rdapapi-php
4 Downloads
Official PHP SDK for the RDAP API — look up domains, IPs, ASNs, nameservers, and entities via RDAP.
piurafunk/docker-php
9 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```