Social feed API for posts, stories, likes, and profiles

ChefSphere social feed APIs cover posts, stories, likes, comments, saves, blocks, and profiles—the engagement layer food and creator apps expect. You should not rebuild a social network from scratch just to attach comments to recipes, kitchens, or creator profiles. The module sits beside media uploads, moderation reports, and realtime notifications so community feels native rather than bolted on after launch.

This guide is about feed and profile product behavior, not moderation queues, not push delivery, and not media transforms, even when those modules are adjacent. Each page keeps distinct search intent so teams planning community scope are not forced through a generic platform essay. If your question is reports and appeals, read moderation; if it is notification delivery, read realtime push instead of this feed guide.

Posts and stories need authorship, visibility, and media references your clients can render consistently across mobile and web without inventing schema mid-sprint. Likes, comments, and saves need idempotent writes and clear ownership so retries do not corrupt engagement counts users notice immediately. Blocks and profile controls are not optional if you open public commenting to strangers at scale.

Creating a social post sits above a simple catalog read on the prepaid token table, but below AI vision and marketplace checkout in published weights. That middle weight is deliberate: engagement writes matter, yet they should not price out healthy community volume on Starter and Growth packs. Packs start at $29 for 200,000 tokens shared across every module you enable, including social, media, and moderation together.

Pair social with moderation before you invite strangers, and pair with media when images and short video dominate the feed experience you market. Pair with realtime push when likes and comments should notify without polling batteries into the ground on mobile clients. Early access is the moment to name which of those arrive in version one versus a later release with clearer staffing.

Calls authenticate with an X-API-Key in the Firebase-style model and burn prepaid tokens from one shared balance across nineteen modules. Unused tokens stay available when engagement is quieter between campaigns, so you are not punished for seasonal community traffic. Growth and Scale packs exist for teams that expect dense feed write traffic alongside live or AI features in the same product month.

Request early access, describe your community norms and content types, and we email you when onboarding opens for your use case. Illustrative OpenAPI samples help you design clients; production contracts follow access so you integrate against the real surface.

Ship profiles and posts before stories if your team is small, and add blocks plus report hooks before public discovery surfaces strangers to each other. Measure whether community is a retention engine or a support sink before you expand mentions, follows, and ranking ambitions. Staffing reality matters more than a feature checklist copied from a larger social network you are not prepared to operate.

Related guides on moderation, media assets, and realtime push complete the community stack without pretending social alone is enough for public UGC. Request early access with a short note on audience size and whether UGC is public by default. That context helps us prioritize onboarding for teams ready to operate trust workflows alongside feed features.