NewEvoras for AI agents
Evoras

Webhook / REST

POST each finished article as JSON to any endpoint you control.

If you need articles to arrive in a system Evoras doesn't natively support — a static-site generator, a custom CMS, or a middleware pipeline — use the webhook integration. Evoras sends a POST request with the full article as JSON.

What you'll need

  • A URL that accepts POST requests (HTTP or HTTPS)
  • (Optional) A secret for verifying requests came from Evoras

How it works

When an article finishes and autopilot triggers (or you manually publish), Evoras sends a POST to your URL with this JSON structure:

{
  "id": "article-uuid",
  "title": "Article Title",
  "slug": "article-title",
  "content": "<h1>Article body as HTML...</h1>",
  "excerpt": "Meta description...",
  "featured_image": "https://cdn.evoras.app/images/...",
  "images": [
    {
      "url": "https://cdn.evoras.app/images/...",
      "alt": "Image description"
    }
  ],
  "tags": ["keyword-1", "keyword-2"],
  "published_at": "2026-07-19T12:00:00Z",
  "site_id": "site-uuid"
}

Verifying requests

If you set a secret, Evoras includes it as the X-Evoras-Signature header. Your endpoint can check the header matches your secret to verify the request is genuinely from Evoras.

Response expectations

Your endpoint should respond with a 2xx status code to acknowledge receipt. Evoras will retry up to 3 times if it gets a non-2xx response or a timeout, with a brief delay between attempts.

Connect in Evoras

Go to Integrations, click Connect on Webhook / REST, and enter your endpoint URL and optional secret.