Greip - Fraud Prevention API Documentation

This is the complete API documentation for connecting to the Greip - Fraud Prevention API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Greip - Fraud Prevention: Greip - Fraud Prevention provides IP intelligence, validation, and fraud-scoring APIs for geolocation, reputation checks, email and phone verification, domain and BIN/IBAN lookup, and payment risk analysis. Keep reading to get started.

Quickstart

Before you run your first Greip - Fraud Prevention request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Greip - Fraud Prevention connection — create or choose one in Connections. Note its connectionId.

Every Greip - Fraud Prevention action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/greip/latest/actions/{actionSlug}

You need a MindCloud API Key and a Greip - Fraud Prevention connection. Then call an action such as Get ASN Lookup:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/greip/latest/actions/get-asn-lookup" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Greip - Fraud Prevention account that should run the action. MindCloud stores and refreshes the Greip - Fraud Prevention credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Greip - Fraud Prevention actions

All 15 published actions for this Greip - Fraud Prevention version. Each page documents the endpoint, arguments, and response controls.

• DELETEDelete User Data
• GETGet ASN Lookup
• GETGet BIN/IIN Lookup
• GETGet Bulk IP Lookup
• GETGet Country Lookup
• GETGet Domain Lookup
• GETGet Email Scoring
• GETGet Free IP
• GETGet IBAN Lookup
• GETGet IP Geolocation
• GETGet IP Lookup
• GETGet IP Reputation
• GETGet Phone Number Scoring
• GETGet Profanity Detection
• GETRun Payment Fraud Detection

Related apps

More Business Intelligence apps on the Universal API, behind the same REST shape. Or browse all apps.

JotformFathomStravaCognito FormsPDF.coApifyBrowse AIPdfFiller