🚀 API Playground
Test the Fluence Behavioral Intelligence API interactively with real-time responses. Enter your API key, select an endpoint, configure parameters, and see live results.
This playground connects to our production API. All requests consume credits from your account. Make sure you have sufficient credits before testing.
Features
- ✅ Interactive Testing - Test all endpoints with a single click
- 🔑 Secure API Key Storage - Your API key is stored locally in your browser
- 📊 Real-time Responses - See instant results with syntax highlighting
- 💳 Billing Visibility - View credits used and remaining after each request
- 🚀 Batch Support - Test batch endpoints with up to 10 profiles
- ⚡ Multiple Endpoints - Switch between Basic, Complete, and Batch endpoints
Available Endpoints
Single Profile Analysis
| Endpoint | Method | Credits | Fields | Description |
|---|---|---|---|---|
| CRM Basic | POST | 1 | 6 core | Essential lead qualification |
| CRM Complete | POST | 2 | 11+ with OCEAN/MBTI | Complete behavioral analysis |
| CRM Plus | POST | 3 | 12+ with AI insights | Premium market intelligence |
Batch Processing (Up to 50 Profiles)
| Endpoint | Method | Credits | Max Profiles | Description |
|---|---|---|---|---|
| CRM Basic Batch | POST | 1 × success | 50 | Bulk lead qualification |
| CRM Complete Batch | POST | 2 × success | 50 | Bulk behavioral analysis |
| CRM Plus Batch | POST | 3 × success | 50 | Bulk premium insights |
Utility
| Endpoint | Method | Credits | Description |
|---|---|---|---|
| Check Credits | GET | 0 | View remaining credits |
| Health Check | GET | 0 | API status verification |
Batch endpoints charge credits per successful profile analysis. For example:
- 10 profiles with CRM Basic Batch = 10 credits (1 × 10 successful)
- 10 profiles with CRM Complete Batch = 20 credits (2 × 10 successful)
- 10 profiles with CRM Plus Batch = 30 credits (3 × 10 successful)
- Failed profiles are not charged
All endpoints require the person to have a public profile on professional networks. We cross-reference information to ensure we find the correct person and provide accurate analysis.
🔑 API Configuration
📊 Select Endpoint
⚙️ Request Parameters
Note: The person must have a public profile on professional networks. We verify the information found matches the profile to ensure accuracy.
How to Use
1. Get Your API Key
If you don't have an API key yet, contact us at support@tryfluence.tech to get immediate access.
2. Enter Your API Key
Paste your API key in the "API Key" field at the top of the playground. Your key is stored locally and only used for API requests.
3. Select an Endpoint
Click on any endpoint card to select it. Each endpoint shows:
- HTTP method (GET/POST)
- Credit cost
- Required tier
- Description
4. Configure Parameters
Depending on the endpoint:
- Name + Company: Enter first name, last name, and company
- Batch: Add multiple profiles (up to 10)
5. Test!
Click the "🚀 Test Endpoint" button to send the request. You'll see:
- HTTP status code
- Response time
- Full JSON response
- Billing information (credits used/remaining)
Tips for Testing
Testing Best Practices
- Start with Check Credits - Verify your API key works and see your credit balance
- Try Basic Before Complete - Basic endpoints use fewer credits (1 credit vs 2 credits)
- Test Error Handling - Try invalid inputs to see error responses
- Monitor Your Credits - Check remaining credits after each request
Example Test Scenarios
Scenario 1: Quick Profile Check
Endpoint: CRM Basic
First Name: Satya
Last Name: Nadella
Company: Microsoft
Scenario 2: Full Analysis
Endpoint: CRM Complete
First Name: Sundar
Last Name: Pichai
Company: Google
Scenario 3: Premium Analysis
Endpoint: CRM Plus
First Name: Tim
Last Name: Cook
Company: Apple
Scenario 4: Batch Processing
Endpoint: CRM Basic Batch
Profiles:
1. Satya Nadella - Microsoft
2. Sundar Pichai - Google
3. Tim Cook - Apple
Total Credits: 1 × 3 = 3 credits
Scenario 5: Complete Batch Processing
Endpoint: CRM Complete Batch
Profiles:
1. Satya Nadella - Microsoft
2. Sundar Pichai - Google
3. Tim Cook - Apple
4. Elon Musk - Tesla
5. Jeff Bezos - Amazon
Total Credits: 2 × 5 = 10 credits
Scenario 6: Premium Batch Processing
Endpoint: CRM Plus Batch
Profiles:
1. Satya Nadella - Microsoft
2. Sundar Pichai - Google
3. Tim Cook - Apple
Total Credits: 3 × 3 = 9 credits
Understanding Responses
Success Response (200)
{
"analise": {
"perfil_profissional": "https://profiles.example.com/satyanadella",
"cargo": "Chairman and CEO",
"tipo_stakeholder": "C-Level Executive",
"tipo_mbti": "ENTJ",
"scores_ocean": {
"openness": 0.85,
"conscientiousness": 0.88,
"extraversion": 0.75,
"agreeableness": 0.70,
"neuroticism": 0.25
},
...
},
"billing_info": {
"creditos_utilizados": 2,
"creditos_restantes": 198,
"tipo_plano": "complete"
}
}
Error Response (422)
{
"error": "Profile not found",
"error_code": "PROFILE_NOT_FOUND",
"details": {
"search_performed": true,
"suggestions": [
"Verify name spelling",
"Check company name",
"Consider adding more context (role, region)"
]
},
"billing_info": {
"creditos_utilizados": 0,
"creditos_restantes": 200
}
}
Common Issues
"Please enter your API key"
Make sure you've pasted your API key in the API Key field at the top.
401 Unauthorized
Your API key is invalid or expired. Contact support for a new key.
402 Payment Required
You don't have enough credits. Check your billing or contact support to add credits.
403 Forbidden
Your tier doesn't have access to this endpoint. Upgrade your plan to access Complete tier endpoints.
422 Unprocessable Entity
The profile couldn't be found or analyzed. Try:
- Checking name spelling
- Using the full company name
- Verifying the person has a public professional network profile
Next Steps
- 📚 View Full API Documentation →
- 🔐 Learn About Authentication →
- 💼 Explore CRM Endpoints →
- 🚀 Try Batch Processing →
- ❌ Error Handling Guide →
Need Help?
- 📧 Email Support: support@tryfluence.tech
- 📖 Documentation: Browse the sidebar for detailed guides
- 🐛 Report Issues: Contact support with your request details
Your API key is stored in your browser's local storage and is never sent to our documentation servers. It's only used when you click "Test Endpoint" to make requests to the Fluence API.