Search competitions

Competition name, trimmed case-insensitive contains matching, minimum two characters.

Minimum length: 2. Maximum length: 100.

Exact competition country, uppercase ISO 3166-1 alpha-2.

Pattern: "^[A-Z]{2}$".

Filter on international competitions. Omission means no filter.

Discipline filter. Omission means all disciplines.

Allowed values: ["jumping","dressage","eventing"].

Sort profile. id is recommended for exhaustive traversal. Rejected as an override once a traversal has begun.

Allowed values: ["name","id"]. Default: "name".

Page size, capped at 100. Bound to the traversal token; rejected as an override once a traversal has begun.

Default: 100. Minimum: 1. Maximum: 100.

Opaque signed continuation token from next_page_token of the previous page. It is bound to the originating query parameters, sort profile, page size and API key, and expires. Callers never interpret its contents.

Once a traversal has begun, per-request sort or page_size overrides are rejected. A malformed, signature-invalid or mismatched token returns 400 invalid_page_token; an expired token returns 400 page_token_expired and the traversal restarts from page one.

Requests fresher data for this call. live bypasses the freshness cache; the override may only request fresher data and never affects price. Any other value fails validation.

Allowed values: ["cached","live"].

Optional pin to the API version your integration was built against. The only accepted value is v1, which today changes nothing. If a later version of the API changes behaviour in a way that is not backwards compatible, requests that send v1 keep the v1 behaviour. Any other value returns 400 unsupported_version.

Optional idempotency key for billable requests. Reuse by the same API key with the same normalized request within 24 hours never creates a second debit. A repeat within that window of a successful request that was charged or used a free allowance is not charged again: it answers with Idempotent-Replayed: true and Hippomundo-Charged-Milli-Credits: 0. Its response is read again, so it may carry current data and a new next_page_token. A success that cost nothing for another reason is not recorded under the key, so a repeat of it is priced like a new request and carries no Idempotent-Replayed. A free page stays free. A free repeat of a request you paid for shortly before is charged once that free period has passed. A repeat of an uncharged failure runs again. Reuse with a different normalized request within 24 hours of a success that was charged or used a free allowance returns an uncharged 409 idempotency_conflict. A key with no such success, or whose 24 hours have passed, takes a different request as a new one. Without the header, each request is independent.

Maximum length: 255.

Always private, no-store on successful responses: data can change at any time, so no cache may store or reuse them, and the API answers no conditional requests.

The milli-credits this request debited from your balance, read from the recorded charge; one credit is 1,000 milli-credits. 0 when the request debited nothing, for example on a free operation, under a free allowance, or on an idempotent replay. Error responses are never charged and do not carry this header.

Minimum: 0.

Sandbox only. Names the copy of the sandbox data that answered this request. The weekly data refresh replaces that copy and publishes a new value, so a client that keeps sandbox data can key it on this value. HTTP caches still may not store the response (Cache-Control: private, no-store). A next_page_token issued under an earlier value answers 400 page_token_expired. Absent in production, and in the sandbox until its first refresh.

Pattern: "^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$".

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

true when this response answers a repeat, within 24 hours and with the same Idempotency-Key, of an earlier successful request that was charged or used a free allowance. The repeat is not charged again, so Hippomundo-Charged-Milli-Credits is 0. Absent otherwise, including on a repeat of a request that cost nothing for another reason.

Allowed values: ["true"].

Request quota of the applied rate-limit window. The same rate-limit headers appear on successful authenticated responses.

Requests remaining in the applied rate-limit window.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

Always ApiKey, without credential detail.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

Seconds to wait before retrying. Required on 429 and on 402 api_key_credit_cap_reached, where it counts to the start of the next UTC day or month; present on 503 when the service knows a meaningful recovery interval.

Minimum: 0.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

Seconds to wait before retrying. Required on 429 and on 402 api_key_credit_cap_reached, where it counts to the start of the next UTC day or month; present on 503 when the service knows a meaningful recovery interval.

Minimum: 0.

Request quota of the applied rate-limit window. The same rate-limit headers appear on successful authenticated responses.

Requests remaining in the applied rate-limit window.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.

Seconds to wait before retrying. Required on 429 and on 402 api_key_credit_cap_reached, where it counts to the start of the next UTC day or month; present on 503 when the service knows a meaningful recovery interval.

Minimum: 0.

RFC 9457 problem document used by every managed error response under /v1, regardless of which layer produced it. Content type is always application/problem+json. Clients branch on code, retain an unknown-code fallback, use status only for broad handling and must ignore unknown top-level fields. title and detail are human-readable English, may be clarified without versioning and are never parsed.

Always no-store on error responses.

Compact server-generated request identifier carried on every response. On errors it equals the body request_id. Quote it in support requests; it contains no customer identity. An inbound customer-supplied value is never trusted as this identifier.