LogoLogo
Nimble HomeLoginCreate an Account
  • Home
  • Quick Start Tutorials
    • Tutorial Library
      • Track SEO and SEM Ranking
      • Reddit as a Guerilla Marketing Strategy
  • Nimble Platform
    • Nimble Platform Overview
    • Online Pipelines
      • Supermarkets
        • ASDA
        • Tesco Groceries
        • Sainsbury’s
        • Morrisons
      • eCommerce
      • Restaurants
        • Yelp
        • Tabelog
        • Uber Eats Japan
        • Demaecan
        • Uber Eats US
      • Real Estate
        • Zillow
  • Nimble SDK
    • SDK Overview
    • Web API
      • Web API Overview
      • API Product Specs
      • Nimble Web API Quick Start Guide
        • Introduction
        • Nimble APIs Authentication
        • Real-time URL request
        • Delivery methods
        • Batch processing
        • Response codes
        • FAQs
      • Nimble Web API Functions
        • Realtime, Async & Batch Request
        • Geo Location Targeting
        • Javascript Rendering
        • Page Interaction
          • Wait (delay)
          • Wait for Selector
          • Wait and Click
          • Wait and Type
          • Scroll
          • Scroll to
          • Infinite Scrolling
          • Capturing Screenshots
          • Collecting Cookies
          • Executing HTTP Requests
          • Operation Reference
        • Network Capture
          • Filter by URL Matching
          • Filter By Resource Type
            • Real World Demo: Capturing Ajax Requests
          • Wait for Requests
          • Capturing XHR without Rendering
          • Operation Reference
        • Data Parsing
          • Parsing Templates
          • Merge Dynamic Parser
        • Custom Headers & Cookies
        • General Params
      • Vertical Endpoints
        • SERP API
          • Real-time search request
          • Getting local data
          • Browsing SERP pagination
          • Delivery methods
          • Batch Processing
          • Endpoints and Response Codes
        • Maps API
          • Searching for places
          • Getting information about a place
          • Collecting reviews
          • Delivery methods
          • Batch processing
          • Endpoints and Response Codes
    • Web Retrieval API
      • Web Retrieval API Overview
    • Proxy API
      • Nimble IP Overview
      • Nimble IP Quick Start Guide
        • Send a request
        • Nimble IP Autentication
        • Geotargeting and session control
        • Response codes
        • FAQs
      • Nimble IP Functions
        • Country/state/city geotargeting
        • Controlling IP rotation
        • Geo-sessions: longer, stickier, more accurate sessions
        • Using IPv6 Proxies
        • Response Codes
      • Integration Guides
        • Incogniton
        • Kameleo
        • VMLogin
        • AdsPower
        • FoxyProxy
        • Android
        • Multilogin
        • iOS
        • SwitchyOmega
        • Windows
        • macOS
        • Proxifier
        • MuLogin
        • Puppeteer
        • Selenium
        • Scrapy
    • Client Libraries
      • Installation
      • Quick Start
    • LangChain Integration
  • Technologies
    • Browserless Drivers
      • API Driver-Based Pricing
    • IP Optimization Models
    • AI Parsing Skills
  • Management Tools
    • Nimble Dashboard
      • Exploring the User Dashboard
      • Managing Pipelines
      • Reporting and Analytics
      • Account Settings
      • Experimenting with the Playground
      • Billing and history
    • Nimble Admin API
      • Admin API basics
      • Admin API reference
  • General
    • Onboarding Guide
      • Getting started with Nimble's User Dashboard
      • Nimble IP Basics
      • Nimble API Basics
      • Helpful Resources
    • FAQs
      • Account Settings and Security
      • Billing and Pricing
      • Tools and Integrations
      • Nimble API
      • Nimble IP
    • Deprecated APIs
      • E-commerce API
        • E-commerce API Authentication
        • Real-time product request
        • Real-time product search request
        • Delivery methods
        • Batch Processing
        • Endpoints and Response Codes
      • Unlocker Proxy Overview
        • Unlocker Proxy Quick Start Guide
          • Real-time request
          • FAQs
        • Unlocker Proxy FAQ
Powered by GitBook
On this page
  • Retrieval API Overview
  • Key Concept: Pipeline
  • How It Works
  1. Nimble SDK
  2. Web Retrieval API

Web Retrieval API Overview

Nimble Labs Beta Feature

Retrieval API Overview

The Retrieval API is designed to streamline the process of generating insights from public web data. With just a few simple steps, you can provide URLs and questions, and receive detailed answers based on the content of those URLs. This API is perfect for quickly generating insights from online data sources, using a powerful pipeline model that makes the process both flexible and efficient.

Key Concept: Pipeline

The Retrieval API revolves around the concept of a Pipeline. A Pipeline is a generative flow where you provide your data sources (URLs, Files, Nimble Online Pipelines) and questions (plain text), and the API processes them to deliver insightful answers.

How It Works

Step 1: Create a New Pipeline

To begin, you’ll create a new pipeline by providing a set of data sources (public URLs) and questions. Each pipeline is tailored to the data you upload, ensuring that the answers provided are based on those specific sources.

  • What You Provide:

    • A list of URLs to public data sources

    • A list of questions you want answers to

Once the pipeline is created, the system will generate a unique pipeline_id and a task_exec_id for tracking the generation process.

Step 2: Get Your Pipeline ID and Task Exec ID

Once your pipeline is created, you will receive two key pieces of information:

  • Pipeline ID: This is the unique identifier for your entire pipeline.

  • Task Exec ID: This tracks the specific generative task, helping you query the answers for your pipeline's data.

Step 3: Query the Results

After your pipeline is generated, you can retrieve the results using different query methods:

  • All Pipelines: Retrieve the results of all pipelines you've created.

  • Specific Pipeline: Focus on the results of one pipeline using its unique pipeline_id.

  • Task Exec ID: Drill down into a specific generative task within a pipeline using the task_exec_id.

This flexibility allows you to monitor both broad and granular insights with ease.

Step 4: Update the Pipeline

If you have new data sources or additional questions, you can update an existing pipeline. This ensures that your insights stay relevant and up-to-date without having to create a new pipeline from scratch. Just add the new URLs or questions to your existing pipeline and continue generating answers.


Why Use Answerit API?

  • Quick and Simple: Creating and managing pipelines is fast, allowing you to generate insights with just a few API calls.

  • Flexible Data Handling: You can easily update existing pipelines with new information, ensuring that your questions and answers remain relevant.

  • Granular Control: Track both entire pipelines or specific tasks, giving you the power to analyze results at any level of detail.

AnswerIt API is designed to be both user-friendly and powerful, letting you extract insights from public web data with minimal effort.

PreviousWeb Retrieval APINextProxy API

Last updated 7 months ago