WeCanTrack Getting Started: Account, Keys, First Request (2026)

Getting started overview

To begin using WeCanTrack for affiliate marketing data centralization, the initial steps involve setting up an account, configuring data sources, and understanding the platform's data retrieval methods. WeCanTrack is designed to aggregate data from various affiliate networks and advertising platforms into a single interface, primarily through no-code integrations. For custom data retrieval or more advanced integrations, API access is available, typically for higher-tier plans, enabling programmatic interaction with the collected data WeCanTrack API documentation.

The core process for new users focuses on:

1. Account Creation: Registering for a WeCanTrack account.
2. Subscription Activation: Selecting and activating a paid plan, as a free tier is not offered.
3. Credential Retrieval: Locating necessary API keys or tokens for programmatic access.
4. Initial Data Source Setup: Connecting at least one affiliate network or advertising platform.
5. First API Request: Executing a basic API call to confirm connectivity and data access.

While WeCanTrack emphasizes no-code integrations, this guide will focus on the API aspect for developers and technical users who require programmatic access to their consolidated affiliate data. Understanding the principles of RESTful APIs, including HTTP methods and data formats like JSON, is beneficial for this process Mozilla Developer Network REST glossary.

Here's a quick reference table for the essential getting started steps:

Create an account and get keys

To access WeCanTrack's services, including its API, you must first create an account and subscribe to a paid plan. WeCanTrack does not offer a free tier WeCanTrack pricing plans. The process typically involves:

1. Registration: Navigate to the WeCanTrack website and complete the signup form. This usually requires basic contact information and setting up login credentials.
2. Subscription Selection: Choose a plan that aligns with your anticipated usage and required features. Plans start at $129/month for 100,000 requests and scale up WeCanTrack detailed pricing.
3. Payment Setup: Provide payment details to activate your subscription.
4. Account Activation: Confirm your email address if required to activate the account.

Once your account is active and a subscription is in place, you can locate your API key, which is essential for authenticating API requests. The API key serves as a unique identifier and security token, allowing your applications to interact with WeCanTrack's API on your behalf.

To retrieve your WeCanTrack API key:

1. Log in to your WeCanTrack dashboard.
2. Navigate to the Settings section.
3. Look for an option labeled API Access or similar.
4. Your API key should be displayed there. Treat this key as sensitive information, similar to a password, and keep it secure to prevent unauthorized access to your data.

WeCanTrack's API access is generally available for higher-tier plans. If you are on a lower-tier plan, you may need to upgrade to gain API functionality WeCanTrack API documentation overview.

Your first request

Before making your first API request, ensure you have connected at least one affiliate network or advertising platform within your WeCanTrack dashboard. This step populates your account with data that can then be retrieved via the API WeCanTrack integrations guide.

WeCanTrack's API is typically RESTful, meaning it uses standard HTTP methods (GET, POST, PUT, DELETE) to interact with resources and often returns data in JSON format. For a first request, a simple GET operation to retrieve a list of conversions or clicks is a common starting point.

Let's assume the WeCanTrack API provides an endpoint for retrieving recent conversions. A hypothetical endpoint might look like https://api.wecantrack.com/v1/conversions.

You will need your API key for authentication. This key is typically included in the request headers, often as an Authorization header with a Bearer token scheme, or as a query parameter. Refer to the official WeCanTrack API documentation for authentication specifics.

Example API Request (using cURL)

Assuming your API key is YOUR_API_KEY_HERE and the endpoint to fetch recent conversions is https://api.wecantrack.com/v1/conversions:

curl -X GET \
  'https://api.wecantrack.com/v1/conversions' \
  -H 'Authorization: Bearer YOUR_API_KEY_HERE' \
  -H 'Accept: application/json'

Replace YOUR_API_KEY_HERE with your actual API key obtained from your WeCanTrack dashboard. This cURL command sends an HTTP GET request to the specified endpoint, including the necessary authentication header and specifying that you expect a JSON response.

Expected Response

A successful response (HTTP status code 200 OK) would typically return a JSON object or array containing conversion data. For example:

{
  "data": [
    {
      "conversion_id": "co_abc123",
      "timestamp": "2026-05-29T10:00:00Z",
      "amount": 15.50,
      "currency": "USD",
      "status": "approved",
      "network": "ExampleAffiliateNet",
      "campaign_id": "cmp_xyz789"
    },
    {
      "conversion_id": "co_def456",
      "timestamp": "2026-05-29T09:45:00Z",
      "amount": 22.00,
      "currency": "EUR",
      "status": "pending",
      "network": "AnotherAffiliateNet",
      "campaign_id": "cmp_uvw321"
    }
  ],
  "meta": {
    "total": 2,
    "page": 1,
    "limit": 100
  }
}

The exact structure of the JSON response will depend on the specific API endpoint and the data available in your WeCanTrack account. Always consult the WeCanTrack API documentation for precise endpoint definitions and response schemas.

Common next steps

Once you have successfully made your first API request and received data, you can proceed with further integration and data utilization:

1. Explore More Endpoints: Review the WeCanTrack API documentation to discover other available endpoints, such as those for retrieving clicks, campaigns, or aggregated reports.
2. Implement Data Filtering and Pagination: Learn how to filter results by date ranges, campaign IDs, or other parameters, and how to use pagination to retrieve large datasets efficiently. This is crucial for building robust applications that interact with large volumes of data Google Developers on pagination.
3. Automate Data Retrieval: Set up scheduled tasks (e.g., cron jobs, cloud functions) to periodically pull data from WeCanTrack's API and store it in your own database, data warehouse, or analytics platform.
4. Integrate with Business Intelligence (BI) Tools: Connect the retrieved data to BI tools like Tableau, Power BI, or Looker Studio to create custom dashboards and reports that analyze your affiliate performance.
5. Monitor API Usage: Keep track of your API request volume to stay within your plan's limits and manage costs. WeCanTrack provides tools within the dashboard to monitor usage.
6. Error Handling: Implement robust error handling in your code to manage various API responses, including rate limits, authentication failures, and data format errors.
7. Webhooks: Investigate if WeCanTrack offers webhooks for real-time notifications of new conversions or other events. Webhooks can reduce the need for constant polling and provide more immediate data updates PayPal Developer Webhooks guide.

Troubleshooting the first call

Encountering issues during your first API call is common. Here are some troubleshooting steps:

• Check API Key: Ensure your API key is correct and included in the request headers as specified in the WeCanTrack API documentation. A common error is a malformed Authorization header or an expired key.
• Verify Endpoint URL: Double-check that the API endpoint URL is accurate, including the correct version (e.g., /v1/) and resource path (e.g., /conversions).
• HTTP Method: Confirm you are using the correct HTTP method (e.g., GET for retrieving data, POST for creating). Using the wrong method will often result in a 405 Method Not Allowed error.
• HTTP Status Codes: Pay attention to the HTTP status code returned in the API response. Common error codes include:
  • 400 Bad Request: Your request was malformed or missing required parameters.
  • 401 Unauthorized: Missing or invalid authentication credentials (API key issue).
  • 403 Forbidden: Your API key does not have permission to access the requested resource, or your plan does not include API access.
  • 404 Not Found: The endpoint or resource you are trying to access does not exist.
  • 429 Too Many Requests: You have exceeded the API rate limits. Implement a backoff strategy.
  • 5xx Server Error: An issue occurred on WeCanTrack's servers.
• Response Body: Examine the response body for detailed error messages. APIs often provide specific error codes or human-readable descriptions that can guide your troubleshooting.
• Network Connectivity: Ensure your network can reach api.wecantrack.com. Proxy issues or firewall rules can block API requests.
• Data Source Configuration: Confirm that you have correctly set up and connected your affiliate networks within the WeCanTrack dashboard. If no data sources are connected, the API may return empty datasets.
• WeCanTrack Documentation: Always refer to the official WeCanTrack API documentation for the most accurate and up-to-date information on endpoints, parameters, and error codes.
• Support: If you've exhausted troubleshooting options, contact WeCanTrack support for assistance.