Getting Started

Welcome to the Monark Markets API! This guide will help you get started by outlining key details about API usage, access, and best practices.

API Key Management

  • API Usage requires a unique API Key, which must be requested by contacting: [email protected]
  • Keys are issued as standard API Keys. API Keys are environment-specific.
  • Use the issued API Key in an HTTP Header like this: Authorization: <Api Key>
  • Monark currently supports two environments for partners:
    • Sandbox (sandbox-api.monark-markets.com): For API testing, integration, and conformance testing checks.
    • Production (api.monark-markets.com): For live operations.
  • Always keep your API Keys secure. Avoid hardcoding them into applications and rotate them regularly as a security best practice.

Rate Limiting

  • Individual rate limits apply to each endpoint. If you encounter rate-limiting issues, reach out to [email protected] for assistance.
  • Monitor your usage to ensure uninterrupted access to the API.

Idempotency

Idempotent API operations guarantee that multiple identical requests produce the same result as a single request. Our API supports idempotency via the optional IdempotencyKey header—a unique client-generated identifier that prevents duplicate operations.

The IdempotencyKey header is:

  • Optional and only applicable for POST requests (it is ignored on PUT)
  • Valid for 24 hours from first use
  • Client-generated (any unique string)

When a POST request fails or times out, you can retry with the same IdempotencyKey within the 24-hour window, and Monark returns the original response instead of repeating the operation. Keys expire after 24 hours, so ensure retries occur within this timeframe.

Idempotency keys are best-effort: they are held in memory by the server that handled the request, so a retry that reaches a different server, or arrives after a restart, may be processed again. Where an endpoint takes a referenceId, such as Omnibus orders and model orders, a reused referenceId is always refused with 409 (DuplicateReferenceId), so use a stable referenceId as your guaranteed protection against duplicates.

Example header:

IdempotencyKey: 123e4567-e89b-12d3-a456-426614174000

Documentation and Support

  • All available endpoints are documented in detail on the following pages. Refer to them for specifics on each API call.
  • For additional help, contact [email protected]