FindIP.Net

FindIP Shield Server Verification API

One endpoint. Your backend sends the Shield session ID it received from the browser, authenticated with the site's secret key, and gets back the risk Shield…

Maps & location#geocoding

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

One endpoint. Your backend sends the Shield session ID it received from the browser, authenticated with the site's secret key, and gets back the risk Shield recorded for that session. Browser-side results can be altered by the visitor; this response cannot.

The result is a set of risk signals and a recommendation for your code to use. It is an assessment, not proof of abuse, and Shield takes no action on its own.

Guide: https://www.findip.net/docs/shield/server-verification

Endpoints 1

  • POSTVerify a session's risk/v1/shield/sessions/verifyReturns the risk Shield has recorded for one session of the site that owns the secret key. A session Shield has never seen for this site is not an error: the…

API details

Base URL
https://shield.findip.net
Authentication
A bearer token in the Authorization header
Operations
1 operation on 1 pathPOST 1
Response formats
application/json
Description format
OpenAPI 3.1.0, API version 1.0.0

How to test the FindIP Shield Server Verification API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the FindIP Shield Server Verification API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses A bearer token in the Authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Verify a session's risk” (POST /v1/shield/sessions/verify), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the FindIP Shield Server Verification API?

One endpoint. Your backend sends the Shield session ID it received from the browser, authenticated with the site's secret key, and gets back the risk Shield… It is listed under Maps & location and has 1 endpoint.

Who publishes the FindIP Shield Server Verification API?

It is listed from FindIP.Net's public API description (an OpenAPI document), not published by FindIP.Net on Swastik Codes. Anyone who controls findip.net can claim the profile by adding a DNS TXT record.

What is the base URL of the FindIP Shield Server Verification API?

Requests go to https://shield.findip.net. Endpoint paths are added to this base URL.

How do I authenticate with the FindIP Shield Server Verification API?

With A bearer token in the Authorization header.

How many endpoints does the FindIP Shield Server Verification API have?

1 operation on 1 path (1 POST).

Is forking the FindIP Shield Server Verification API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.