Skip to main content
This guide walks you through making your first API request to the Everflow platform.

​
Prerequisites

  • An Everflow account with network-level access
  • A Network API key — see Authentication for how to create one

​
Base URL

All API requests are made to: 
https://api.eflow.team/v1/
The path after /v1/ depends on the API you are using:
APIPath prefix
Network/v1/networks/...
Affiliate/v1/affiliates/...
Advertiser/v1/advertisers/...
Marketplace/v1/partners/...

​
Step 1: Get your network info

Make a GET request to retrieve your network’s configuration: 
curl -H "X-Eflow-API-Key: <your-api-key>" \
  https://api.eflow.team/v1/networks
You’ll receive a JSON object with your network’s details: 
{
  "network_id": 1,
  "name": "My Network",
  "status": "active",
  "default_currency_id": "USD",
  "reporting_timezone_id": 67,
  "time_created": 1709500000,
  "time_saved": 1709500000
}
See Get Network Info for the full response schema.

​
Step 2: Search with pagination

Most resources have a listing endpoint (POST .../table) that supports pagination and filtering. Search for active offers: 
curl -X POST \
  -H "X-Eflow-API-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "filters": {
      "offer_status": "active"
    },
    "paging": {
      "page": 1,
      "page_size": 10
    }
  }' \
  https://api.eflow.team/v1/networks/offers/table
The response includes your results and pagination metadata: 
{
  "offers": [
    {
      "network_offer_id": 1,
      "name": "Example Offer",
      "offer_status": "active"
    }
  ],
  "paging": {
    "page": 1,
    "page_size": 10,
    "total_count": 47
  }
}
See Paging for more on paginating through results.

​
Next steps

Authentication

Learn about API key types and portal access.

Request & Response Format

Understand date formats, IDs, enums, and other conventions.

Rate Limiting

Know your request quotas before building integrations.

Network API Reference

Explore the full Network API.