import.io Getting Started: First Request & Account (2026)

Getting started overview

To begin using import.io for web data extraction, the initial steps involve account creation, credential retrieval, and the execution of a foundational API request. Import.io specializes in providing structured web data, often through a platform interface or managed services, tailored for enterprise requirements (import.io Pricing Page). While extensive self-service API documentation for immediate programmatic access isn't publicly detailed in the same manner as some developer-focused APIs, the core principle remains: obtain authorization, define your extraction target, and initiate a data capture operation. This guide focuses on the general workflow for achieving a first working interaction with the import.io platform, recognizing that specific API endpoints and authentication methods may be customized based on enterprise agreements.

The import.io platform is designed for large-scale data acquisition, supporting various use cases such as competitive intelligence and market research (import.io Homepage). This involves setting up 'extractors' that define how data is collected from specific web pages or sites. For programmatic access, these extractors can then be triggered and their results retrieved via an API. The emphasis here is on understanding the sequence of actions necessary to move from a new user to making an initial data request.

Here's a quick reference table outlining the getting started process:

Create an account and get keys

Creating an import.io account is the first step. Given its focus on enterprise-grade solutions and managed services, the signup process typically involves direct engagement with their sales team rather than an immediate self-service portal for API key generation. Users generally request a demo or contact sales through the import.io enterprise data solutions homepage. During this onboarding, the import.io team will provision access to the platform, which includes the necessary credentials for API interaction.

After your account is set up and activated, you will gain access to the import.io dashboard. Within this dashboard, you locate your API key, also sometimes referred to as an API token or access key. This key is a unique identifier that authenticates your application or script when making requests to the import.io API. It's crucial to treat this key as sensitive information, similar to a password. Storing it securely and avoiding hardcoding it directly into production code is a best practice for API security, as outlined in general API security guidelines (AWS Access Keys Best Practices). The exact location for retrieving the key may vary slightly within the dashboard interface but is typically found under settings, profile, or an 'API Access' section.

For example, a typical API key might look like a long alphanumeric string:

sk_live_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

This key must be included with every API request, usually in an HTTP header (e.g., Authorization: Bearer YOUR_API_KEY) or as a query parameter. The specific method will be detailed in the platform's API documentation provided after account setup. Ensure you understand the scope and permissions associated with your API key, as some keys might have restricted access based on your service agreement.

Your first request

After acquiring your API key, the next step is to make your first programmatic request. With import.io, this typically involves interacting with an existing 'extractor' or configuring a new one via the platform UI and then using the API to run it or retrieve its results. An extractor defines the specific data points you want to collect from target websites.

Assuming you have an extractor set up within your import.io account (e.g., named my_first_extractor) and you want to retrieve the data it has collected, a common API pattern involves a GET request to a data export endpoint. While specific endpoint URLs and payload structures are dependent on your import.io configuration and API version, a conceptual example using cURL might look like this:

curl -X GET \
  'https://api.import.io/v3/extractors/my_first_extractor/data/_download?format=json' \
  -H 'Authorization: Bearer YOUR_API_KEY'

In this example:

• https://api.import.io/v3/extractors/my_first_extractor/data/_download?format=json is the hypothetical API endpoint to download data from an extractor named my_first_extractor in JSON format.
• -H 'Authorization: Bearer YOUR_API_KEY' passes your API key in the Authorization header, following the Bearer Token scheme, a common method for authenticating API requests (OAuth 2.0 Bearer Token Usage). Replace YOUR_API_KEY with your actual key.

Upon successful execution, this request would return the extracted data as a JSON array or object, depending on the extractor's configuration and the data collected. The structure of this JSON will mirror the fields you defined in your extractor. For instance, if your extractor targets product names and prices, the JSON output would contain arrays of objects with product_name and price keys.

Alternatively, if you need to initiate an extraction job programmatically, the request might involve a POST request to a 'run' endpoint, providing parameters like the target URL or specific run configurations:

curl -X POST \
  'https://api.import.io/v3/extractors/my_new_job/runs' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -d '{ "urls": ["https://example.com/page1", "https://example.com/page2"] }'

This conceptual POST request would trigger an extraction for the specified URLs using the my_new_job extractor. The response would typically include a job ID or status, allowing you to later query for the results once the extraction is complete.

Common next steps

After successfully making your first request and retrieving data, several common next steps emerge for integrating import.io into your applications or workflows:

1. Data Processing and Storage: The raw data you receive from import.io often needs further processing. This might involve cleaning, transformation, or enrichment before storing it in a database (SQL, NoSQL), a data warehouse, or a data lake. Consider using libraries specific to your programming language for JSON parsing and data manipulation.
2. Scheduling and Automation: For ongoing data collection, you'll want to schedule your API calls. This can be achieved using cron jobs on Linux systems, cloud-based schedulers like AWS EventBridge (AWS EventBridge Overview) or Google Cloud Scheduler (Google Cloud Scheduler Documentation), or workflow automation platforms like Tray.io (Tray.io Data Integrations). Automating runs ensures you have fresh data at desired intervals.
3. Error Handling and Monitoring: Implement robust error handling in your code to manage API rate limits, authentication failures, or issues with the target websites. Monitoring your extraction jobs and API usage provides visibility into performance and potential problems, ensuring data continuity.
4. Advanced Extractor Configuration: Explore more advanced features within the import.io platform to refine your extractors. This includes handling pagination, dynamic content (JavaScript rendering), login-protected sites, and complex data relationships.
5. Integration with Other Systems: Integrate the extracted data with business intelligence tools, CRM systems, marketing platforms, or custom applications. This often involves building connectors or using existing integration platforms.
6. Scaling Your Operations: As your data needs grow, consider how to scale your import.io usage. This may involve optimizing extractor performance, managing larger volumes of URLs, or coordinating multiple concurrent extraction jobs.

Each of these steps builds upon the initial successful API call, moving towards a more robust and integrated data extraction solution.

Troubleshooting the first call

When your first import.io API call doesn't return the expected results, here are common areas to troubleshoot:

• API Key Validity: Double-check that your API key is correct and hasn't expired or been revoked. Ensure there are no leading or trailing spaces if copying and pasting. If unsure, regenerate the key from your import.io dashboard if that option is available, or contact support.
• Authentication Method: Verify that you are passing the API key in the correct header or parameter as specified by import.io's documentation (e.g., Authorization: Bearer YOUR_KEY vs. a custom X-API-Key header). Mismatched authentication methods are a frequent cause of 401 Unauthorized errors.
• Endpoint Accuracy: Confirm the API endpoint URL is precisely correct, including any version numbers (e.g., /v3/) and resource paths. Minor typos can lead to 404 Not Found errors.
• HTTP Method: Ensure you are using the correct HTTP method (GET, POST, etc.) for the specific action you intend to perform (e.g., GET for retrieving data, POST for initiating an extraction). Using the wrong method often results in 405 Method Not Allowed errors.
• Request Body/Parameters: If your request includes a body (for POST requests) or query parameters, ensure they are correctly formatted (e.g., valid JSON) and contain all required fields. Missing or malformed data can prevent the request from being processed.
• Network Issues: Check your internet connection and any local firewall rules that might be blocking outbound API calls. Temporarily disabling a firewall for a test can help diagnose this.
• Rate Limiting: While less common on a very first call, repeated failed attempts might trigger rate limiting, resulting in 429 Too Many Requests errors. If this happens, wait and retry, or review import.io's rate limit policies.
• Extractor Status: If you are trying to retrieve data from an extractor, ensure the extractor itself is active, configured correctly, and has successfully run at least once to collect data. An empty data response might mean the extractor hasn't yielded any results yet.
• Error Messages: Pay close attention to the HTTP status codes and any error messages returned in the response body. These messages are often highly descriptive and can pinpoint the exact issue.
• Contact Support: If you've exhausted these troubleshooting steps, consult import.io's support documentation or contact their customer support team. Provide them with the exact request you're making, the response you're receiving, and any relevant error codes or messages.