MRC classifications pushed to your endpoint as soon as they are published. This page covers the three things teams ask about most.
Every webhook delivery is signed with an HMAC over the request body using a shared secret issued with your integration key. Verify the signature before trusting the payload. Drop any request whose computed signature does not match the header value.
The exact header name, hashing algorithm, and timestamp tolerance are documented in the API portal so they always match the active deployment.
Non-2xx responses are retried with exponential backoff. Your endpoint must be idempotent because the same delivery may arrive more than once. Each delivery carries a unique delivery_id; deduplicate on it.
Exact retry counts and intervals are in the API portal. Persistent failures eventually drop the delivery, and Mindforge will email the account contact if your endpoint is failing repeatedly.
Acknowledge fast. Return a 2xx as soon as you have persisted the delivery. Push downstream work (alerts, ticketing, dashboards) to a queue. Long-running handlers will be cut off and the delivery will retry.
The current acknowledgement timeout is documented in the API portal.
Header names, signature algorithm, retry intervals, payload schema, and timeout values live in the API documentation portal. They version with each deploy.
Research use only. Not investment advice. Past performance ≠ future results. Mindforge is not a registered investment adviser. Full terms · Methods
