What is Integration Framework?

The ChronosHub Integration Framework lets your organisation connect its own systems to ChronosHub. ChronosHub tells your systems when something happens, for example a manuscript was uploaded, an invoice was paid or a licence was signed, and your systems can send events back into ChronosHub. Both directions are secure, reliable and asynchronous, so your systems and ChronosHub do not have to be available at the same moment.

In practice that means you can automate work that would otherwise be done by hand or by exporting and importing files: pick up incoming manuscripts for processing, keep your finance and production systems in step with ChronosHub, and report results back without anyone re-keying them.

Typical Scenarios

• Pick up every new manuscript. When a manuscript is uploaded, ChronosHub sends a Manuscript Uploaded event with a link to the manuscript file and, where known, the publisher, journal and manuscript stage. This happens on every upload. Your system can download the file and process it. For example, a partner might run its own checks on the manuscript and, if that is agreed with ChronosHub during onboarding, send a result back as an inbound event, echoing the correlationId from the Manuscript Uploaded event unchanged.
• Reconcile payments. When an invoice is paid, ChronosHub sends an Invoice Paid event with the amount, tax, currency, payment method and any institutional agreement. Your finance system can record the payment against the right manuscript without a manual lookup.
• Track licensing. When a licence is signed, ChronosHub sends a License Signed event with who signed, when, and which licence applies. Your production or rights system can act on it straight away.
• Push your own events into ChronosHub. Your system can notify ChronosHub when something happens on your side, for example a status change, by sending an inbound event. See Inbound Events.

New terms are explained in the Glossary. If something goes wrong, see the Errors Reference.

What Can You Do With It?

Depending on your integration needs, you can use the framework in two ways — or both:

Send Events to ChronosHub (Inbound)

If your system needs to notify ChronosHub about things that happen on your side (e.g., a manuscript status change), you send events to our API. You authenticate with an API key, post your event payload, and ChronosHub takes it from there.

See Inbound Events for details.

Receive Events from ChronosHub (Outbound)

If you need to know when something happens in ChronosHub (e.g., a manuscript was submitted), we deliver events to your webhook endpoint. Each request is signed so you can verify it came from us.

See Outbound Events for details.

How It Works

Partner                 ChronosHub Integration Framework
  │                                  │
  │── POST /inbound/{eventType} ────▶│   (you send events to us)
  │                                  │
  │◀── POST /your-webhook-url ──────│   (we send events to you)
  │                                  │

• Inbound events are accepted immediately and processed asynchronously. You receive a 202 Accepted response with an event ID for reference.
• Outbound events are delivered to your registered webhook URL as signed HTTP POST requests. Your endpoint should respond with a 2xx status code to acknowledge receipt.