Skip to main content

Instagram for Business

Fancified

Instagram for Business for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/instagram-business-ui npm install @particle-academy/instagram-business-ui
Node @particle-academy/instagram-business-js npm install @particle-academy/instagram-business-js
PHP 8.4+ particle-academy/instagram-business-php composer require particle-academy/instagram-business-php
Python 3.11+ fancy-instagram-business pip install fancy-instagram-business

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No Instagram for Business SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

Credentials

A Instagram for Business connection holds 4 values.

Two kinds of value, and mixing them up matters. A provider credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An account credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.

Field Scope Secret Where it comes from
App ID per installation not secret From the Meta app dashboard. One value serves the installation.
App secret (OAuth) per installation secret Used for the authorization-code exchange.
App secret (proof) per installation secret Keys appsecret_proof on outgoing Graph API calls.
Instagram access token per connected account secret The connected professional account's long-lived Meta access token.

Authorising

Instagram for Business uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.

This flow issues NO refresh token. A connection is RE-AUTHORISED rather than refreshed when the access token expires — checked, not assumed.

The estate

Instagram for Business has no test estate, and somebody checked. Everything this connector does is real. Use the faker to build against it.

Instagram publishing has no sandbox. Publishing creates a real post on a real professional account, and an unpublished container expires after 24 hours.

What it can do

Actions

media_container_create — Instagram media container

Create an Instagram image container. This reports success before any post exists: pass its id to Publish Instagram media, or the unpublished container expires after 24 hours without producing a post.

POST /{igUserId}/media · unsafe to replay — a retried durable run does it TWICE

Input Required What it is
igUserId yes The professional Instagram account's numeric Graph API id.
imageUrl yes A publicly reachable image URL. Meta fetches its bytes while creating the container.
caption no The caption stored with the container and used when published.

media_publish — Publish Instagram media

Publish a previously created Instagram media container as a real post.

POST /{igUserId}/media_publish · unsafe to replay — a retried durable run does it TWICE

Input Required What it is
igUserId yes The same professional account id used to create the container.
creationId yes The id returned by Create Instagram media container. Unpublished containers expire after 24 hours.

Run it before you have credentials

Every operation ships a faker, whether or not Instagram for Business has a sandbox. Set a node's mode to fake and it returns the shape Instagram for Business actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/instagram-business; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-instagram-business 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fancy-instagram-business 0.2.0
File Size Uploaded Provenance Actions
fancy_instagram_business-0.2.0.tar.gz 20.5 kB Without provenance Details for fancy_instagram_business-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fancy-instagram-business 0.2.0
File Interpreter ABI Platform Actions
fancy_instagram_business-0.2.0-py3-none-any.whl Python 3 none any Details for fancy_instagram_business-0.2.0-py3-none-any.whl

Total release size: 43.4 kB

Release files / fancy_instagram_business-0.2.0.tar.gz

Download URL fancy_instagram_business-0.2.0.tar.gz
Size 20.5 kB
Tags Source
SHA-256 checksum
How to use checksums
8acfa21f480bf31799b2a7796b7f3fa146dd3b169b69340e9f536acdde62e630
BLAKE2b-256 checksum
How to use checksums
4e2f6f64f0438b34a0d23aedcf31f3713f1f678b432aab1f3343ba7dba210d46
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Release files / fancy_instagram_business-0.2.0-py3-none-any.whl

Download URL fancy_instagram_business-0.2.0-py3-none-any.whl
Size 22.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f3a0fab44b2afd1c945491fd17d46348e21271f336596dedeace0dff746bbe06
BLAKE2b-256 checksum
How to use checksums
0f95e6a8f69e57ea68fee5688ebaaf528f1b57612b823a6281664444acaf8f80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Security for fancy-instagram-business 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page