Inbound Events

Inbound events allow you to notify ChronosHub when something happens in your system. You send events by making an HTTP POST request to our API. Each request is authenticated with the API key you received during onboarding.

How It Works

1. You send a POST request to the inbound endpoint with your event payload.
2. ChronosHub validates your API key and accepts the event.
3. You receive a 202 Accepted response with an event ID for your records.
4. ChronosHub processes the event asynchronously — no further action is needed from your side.

Endpoint

POST /inbound/{eventType}

Request

Component	Description
{eventType} (path)	The type of event being sent (e.g., manuscript.status.updated). Agreed upon during onboarding.
X-Api-Key (header)	Your API key, provided during onboarding.
Content-Type (header)	Must be application/json.
Request body	A JSON payload containing the event data.

Example

curl -X POST https://{base-url}/inbound/manuscript.status.updated \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -d '{
    "manuscriptId": "MS-2026-001",
    "status": "accepted",
    "updatedAt": "2026-02-26T12:00:00Z"
  }'

Replace {base-url} with the environment URL from the Overview.

Successful Response

A successful request returns 202 Accepted with the event ID:

{
  "eventId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "status": "Accepted"
}

The eventId is a unique identifier for the event. You can use it as a reference when communicating with ChronosHub support.

Error Responses

Status	Reason
400 Bad Request	Missing or empty payload, or your account is inactive.
401 Unauthorized	Missing or invalid API key.
500 Internal Server Error	An unexpected error occurred on our side.

For 400 and 500 responses, the body follows the Problem Details format:

{
  "type": "https://tools.ietf.org/html/rfc9110#section-15.5.1",
  "title": "One or more validation errors occurred.",
  "status": 400,
  "errors": {
    "": [
      "A non-empty request body is required."
    ]
  },
  "traceId": "00-87ca4ab744fecd95c68d7198e8640de9-c9897de70d245733-01"
}

The traceId field is a unique identifier for the request. If you need to contact ChronosHub support about a failed request, include the traceId so we can look into what went wrong.

Authentication

Every request must include a valid API key in the X-Api-Key header. Requests without a valid key are rejected with 401 Unauthorized.

API keys are provided during the onboarding process. See Partner Onboarding for details on how to obtain your API key.

Event Types

Event types are dot-separated identifiers that describe what happened (e.g., manuscript.status.updated). The available event types and their expected payload schemas are agreed upon between you and ChronosHub during onboarding.