FlashAPI Ask for access

Invite only Phase 1: Facebook, Instagram, Threads

One call. Every feed.

FlashAPI is a hosted API that publishes content to social platforms for any product. One HTTP call reaches every connected account, with each product's editorial rules and each platform's hard limits applied for you.

Ask for access How it works
Example requestillustrative
POST https://api.flashapi.dev/v1/posts
Authorization: Bearer $FLASHAPI_KEY

{
  "idempotencyKey": "weekly-news-41",
  "targets": ["facebook", "instagram", "threads"],
  "content": {
    "default": {
      "text": "This week's news is out.",
      "link": "https://example.com/news",
      "media": [{
        "url": "https://media.flashapi.dev/…",
        "type": "image",
        "alt": "Weekly news card"
      }]
    }
  }
}

202 Accepted
{ "postId": "post_…", "status": "queued" }
  • Facebook
  • Instagram
  • Threads

How it works

Your product makes one request. FlashAPI does the per-platform work and tells you what happened to each target.

  1. Your product calls FlashAPI

    Send the text, an optional link, any images and the targets. You can override any field for a single target.

  2. Rules are applied

    First the product's own rules, such as where the link goes and which hashtags to add. Then each platform's limits. Content that cannot be posted is rejected before anything is sent.

  3. Media is hosted

    Instagram and Threads fetch images from a public address. Upload an image once and FlashAPI returns an HTTPS URL for it.

  4. Published, with retries

    Each target publishes on its own. Temporary failures retry with backoff. Check the post later to see the status and link for every target.

Built to never post twice, or post wrong

Safe to retry
Every post carries an idempotency key. Send the same key again and you get the original post back, with nothing published twice.
Checked first
Content is validated against each platform's declared limits before anything goes out. A failed check returns an error and posts nothing. Read the limits yourself at GET /v1/platforms.
One goes first
With several targets, one is published first as a canary. If it fails, the others are held back. If it succeeds, the rest go out independently, so one failure never undoes another.
Product rules, not code
Link placement (in the text, before hashtags, as a first comment, or dropped) and hashtags are set per product and per platform. A new product needs rules, not new code.
Dry run and kill switch
Add ?dryRun=1 to see exactly what each target would receive, without publishing. Publishing for a product can be halted at any moment.
Small on purpose
No dashboard, no scheduler and no content generation. You send finished text and media, and your own cron decides when.

Platforms

Phase 1 covers Meta, which shares one sign-in system across all three platforms.

Live

  • Facebook
  • Instagram
  • Threads

Image posts. Video is in testing.

Planned for Phase 2

  • Bluesky
  • X
  • LinkedIn
  • Reddit

Adding a platform is one adapter file, with no change to the core.

Used by

TTSensei and Aigregator, both built by the same maker.

Not open to the public yet

FlashAPI has no signup. Access is by invitation while it is in early access. Write a short note about what you would publish, and where.

Ask for access

Built by Yuri Bondarenko