Run Instagram from your own code

A REST API that lets your own code do most of what the Inrō dashboard does: read and update contacts, trigger automations, manage campaigns and folders, configure your AI agent, and publish posts and stories to Instagram. Requests and responses are JSON.

No, and that is rather the point. Inrō is an official Meta Tech Provider and handles the Instagram side, so there is no developer app to register, no Graph API setup and no app review to sit through. You sign up, copy a token, and start making requests.

With a Bearer token in the Authorization header on every request. You will find it under Integrations & API in the account menu. If it ever leaks, regenerate it from the same card and the old one stops working immediately.

20 requests per second, 1,000 per minute, 10,000 per hour and 100,000 per day, per organization. Go over and you will get a 429 response with a Retry-After header telling you how long to wait before trying again.

No. It sends messages and manages your contacts and automations, but browsing the inbox or pulling past conversation history stays in the app.

Pro or Trial. Free accounts receive a 403 when they call the API.

Yes. Alongside the simple token, Inrō supports OAuth 2.1 with PKCE and automatic discovery, which is the right path for a product connecting other people's accounts rather than your own.

Every request is logged for 30 days with its parameters and the response, under Profile then View platform logs.

No. The API works on your live data, so test writes such as triggering scenarios or updating contacts against a throwaway contact or a test scenario first.

The API is for your code. The MCP server is for your AI assistant, which calls the same API on your behalf when you describe what you want in plain language. If you are not a developer, MCP is usually the faster path.