If your app already knows when something new is published, it can tell your social channels too.
Publishing from code
Zedgad accepts content as a simple JSON payload: an ID, a type, a title, a summary, a URL, an optional image, and optional extra data. Send it with the project API key and zedgad posts it to the project's connected accounts.
There are examples for Python, Node, PHP, Ruby, Go, and cURL in the docs, so the integration is usually a few lines.
Common triggers
Developers typically call zedgad when a GitHub release is published, a changelog entry is merged, a blog post is deployed, or a new item is added in their app, such as a job, product, or listing.
Because each payload includes your own stable ID, you can match zedgad's response to the item in your system.
Handling the response
Zedgad records a publish result for every platform in the project log, and the API response tells your code that the content was accepted.
Keep your API key on the server, never in client-side code, and use a separate project for testing so test posts never reach your real audience.
Key takeaway
Send a small JSON payload when something ships, and let zedgad handle every network's API.