🫡 Greetings!

Now, with any request, you can use the nocors=true parameter so that all links to copper have a format for bypassing CORS.

🫡 Greetings!

We integrated a new technology for the business endpoint using GPT, which did not always provide complete information. As a result, we received the maximum response rate, complete information, at the moment the technology is being actively tested, you can see

"unrelated_data":{"GPT":true,"time_gen":1.02}

If the request could not be executed using the usual method, then GPT technology will be used.

We will actively implement this technology to other endpoints as well, if the test is successful.

Hello everyone, if you are unable to subscribe to our API or you encounter any problems related to META checks, we recommend that you subscribe to our spare similar API.

https://rapidapi.com/for-sharm/api/flashapi1/

We are pleased to announce that our partners have integrated Stripe, which allows accepting payments with bank cards. You can use our API on this platform to access and manage these payment functionality. As we mentioned earlier, the cost per request is only 0.00035, which makes using our services even more affordable and economical.

In addition, we present Flint, an experimental interface for communicating with APIs and exploring their capabilities in depth. Flint is a developer tool that allows you to explore the API in a conversational format, which greatly simplifies the integration and testing process.

Try Flint right now and start exploring our APIs in a convenient conversational format!

For more information, check out our documentation on Instagram Scraper API and documentation on Flint.

Hey everyone, great news! ✨
We've updated our analytics, and now our system takes post publication time into account. What does this mean?

Date and Time Tracking ⏰
We now capture the exact time each post was published and display it in a convenient format. This makes it easier for you to see which days and hours bring the highest engagement.

Human-Readable Format 👀
All timing information is now shown in a friendly way: “1 hour ago,” “2 days ago,” etc. This makes the analytics more transparent — you can see at a glance how long ago each post was published.

Engagement Speed Calculation ⚡️
Our new metrics — “likes per hour” and “comments per hour” — help you understand how quickly your audience reacts to fresh posts. You can use this insight to better plan your posting times and boost your most popular content.

Optimized Posting Schedule ✅
By knowing when your followers are most active, you can schedule your posts for the best times and increase engagement.

Try our updated analytics today and find out when your posts perform best! If you have any questions or feedback, feel free to reach out anytime.

Thank you for sticking with us and helping us get better! 🎉

For developers or anyone interested in the technical details:
Check out our Basic Engagement endpoint here:
https://rapidapi.com/arraybobo/api/instagram-scraper-2022/playground/apiendpoint_fd24519a-9539-4bb6-8691-7d21d69e4308

The post_info endpoint will be implemented in accordance with the post_invo_v2 endpoint, since in this concept it is possible to get the play_count parameter as well as a lot more useful information, a lot of people ask about it, but post_info takes much longer to load information, or it does not appear at all in web api requests. Therefore, we would like to inform you that we are preparing for the changes. For each endpoint that will be transferred to the format of the mobile api request, notifications about them will also be released.

The response structure is specified in the file

The method of getting the list of posts by user ID and username will also be changed in order to make the api more stable.

At the moment, all updates have already been launched, RapidAPI has also fixed the access problem. ✅

Hi! 🤝

If you are using an Instagram share URL, extract and use the shortcode

📢 Hello everyone! (BETA)

Recently, Instagram started using byte-range streaming for videos, which caused regular video links to stop working properly.

We found a workaround to ensure correct video downloading, which includes:
✅ Byte alignment and accurate stream handling.
✅ Merging video and audio streams to ensure seamless playback.
✅ Detecting whether a link requires processing (is_only_download_manifest = true).
🔹 How does it work?

If a video requires processing (is_only_download_manifest = true), we automatically download and merge it.

The response now includes direct links to the processed file:

is_only_download_manifest: true
"download_links": {
    "video_url": "https://cdn.igapi.ru/cache/final_899c71518a4a33c96ebb97f898a79d69.mp4",
    "audio_url": "https://cdn.igapi.ru/cache/audio_899c71518a4a33c96ebb97f898a79d69.m4a"
}

Currently available for endpoints

Get Media /p/ - /tv/ - /reel/
Get Media More Data

Hello everyone Well, META has finally achieved its goal, at the moment our api is closed, as of March 14, as Rapidapi states, it will be completely deleted.

🫡 If you want to stay with us, here are the options:

🚀 To continue working further, use any plafthorm that is convenient for you.🚀

1. https://rapidapi.com/for-sharm/api/flashapi1
2. https://flashapi.ru

Corrected the links