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
  • Introduction
  • Key Endpoints
  • Additional Information
  1. Nimble SDK
  2. Web API
  3. Vertical Endpoints
  4. Social API

Instagram

Introduction

The Instagram API allows you to access and interact with Instagram's social media content. It provides endpoints for searching users, hashtags, and locations, as well as retrieving posts, media, and more.

  • Base URL: https://api.webit.live/api/v1/realtime/social/instagram/v1

Key Endpoints

  • Search: Retrieve data by searching for users, hashtags, or locations on Instagram. This endpoint allows you to find relevant content or profiles based on specific queries.

  • Profiles: Access detailed information about Instagram user profiles, including their bio, follower count, and recent posts. This helps in obtaining user-specific data for further analysis.

  • Posts: Get details about individual posts, including media, captions, likes, and comments. This endpoint is useful for analyzing specific content and its engagement metrics.

  • Hashtags: Search for posts related to specific hashtags and retrieve information about hashtag trends and usage. This is helpful for tracking topics and trends within Instagram.

  • Locations: Find posts and information related to specific geographic locations. This endpoint allows you to explore content based on where it was created.

  • Comments: Retrieve comments on individual posts and their details. This is useful for analyzing engagement and interactions on specific posts.

Additional Information

rank_token

This parameter is a UUID version 5, and for each request that use it you should pass a newly generated UUID. If the request is of pagination type, use the same rank_token for all pagination requests.

For example, when you request the paris hashtag feed and the generated UUID is f0d8368d-85e2-54fb-73c4-2d60374295e3, all the pagination requests of paris hashtag will use the same UUID:

GET /instagram/v1/feed/tag/paris?rank_token=f0d8368d-85e2-54fb-73c4-2d60374295e3
GET /instagram/v1/feed/tag/paris?rank_token=f0d8368d-85e2-54fb-73c4-2d60374295e3&max_id=QVFCQ0ZDMUlNOEw0X3dyNGJQSXR0UVVNaU9yM2tNdzlFN2ZyMnJDY1V2VXhTemEzbTQzTmxfRTNhY3pHUlFMT0kwQ2RVMTNqSy1DRXJadm1SWW41THhQTw==
GET /instagram/v1/feed/tag/paris?rank_token=f0d8368d-85e2-54fb-73c4-2d60374295e3&max_id=...

Then, when you request for a different hashtag, let's say israel, you'll have to generate a new UUID:

GET /instagram/v1/feed/tag/israel?rank_token=35adbb92-df2c-4ec3-909e-ddaa081d2b39
GET /instagram/v1/feed/tag/israel?rank_token=35adbb92-df2c-4ec3-909e-ddaa081d2b39&max_id=...

Last updated 3 months ago