> ## Documentation Index > Fetch the complete documentation index at: https://docs.goodgrants.com/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve leaderboard results > Retrieves leaderboard results. A missing or unresolvable `score_set` parameter returns `404 Not Found`. ## OpenAPI ````yaml /api-reference/openapi-v2_3.yaml get /leaderboard openapi: 3.1.0 info: title: Good Grants API version: '2.3' description: > The Good Grants API enables you to programmatically manage grant-making programs, funding cycles, and application workflows. Use this API to: - Create and manage grant applications and submissions - Automate review workflows and scoring assignments - Track grant payments and fund allocations - Generate compliance reports and analytics - Integrate with external systems via webhooks All API requests require authentication using an API key provided in the `X-Api-Key` header. license: name: Creative Force Client Subscription Terms url: https://creativeforce.team/agreement/ servers: - url: https://api.us.cr4ce.com description: US regional endpoint - url: https://api.eu.cr4ce.com description: EU regional endpoint - url: https://api.au.cr4ce.com description: Australasia regional endpoint - url: https://api.ca.cr4ce.com description: Canada regional endpoint - url: https://api.hk.cr4ce.com description: Hong Kong regional endpoint security: - ApiKeyAuth: [] tags: - name: Account description: >- Use this operation to retrieve information about your organization account. The account resource provides metadata about the tenant associated with your API key. Note: Account information is read-only and contains organization-level settings and identifiers. - name: Action tasks description: >- Use these operations to manage individual review and evaluation activities. Action tasks represent specific actions that reviewers or administrators need to complete during the evaluation process. Tasks track timestamps, decisions, and reviewer associations. Action tasks integrate with the broader review workflow and status tracking. - name: Allocation payments description: >- Use these operations to manage individual payments made against grant allocations. Allocation payments represent installments or disbursements of awarded funds. Payments track scheduling, status (pending, paid, cancelled), and amounts. Comments can be added to payments for grantee communication and record-keeping purposes. - name: Allocations description: >- Use these operations to manage grant allocations awarded to applications. An allocation represents the award of funds from a budget (fund) to an application or applicant. Allocations track the total grant amount, currency, and outstanding balance. Multiple payments can be made against a single allocation to facilitate installment-based grants or milestone payments. - name: Applications (realtime) description: >- Use these operations to perform granular updates on applications without replacing the entire resource. These endpoints enable real-time updates to specific application properties such as: title, category assignment, chapter assignment, individual field values, document uploads, tags, and recusal status. These operations are optimized for interactive applications that need to update grants incrementally. - name: Applications description: >- Use these operations to manage grant applications submitted to your funding programs. Applications are the core entity that flows through the entire lifecycle from submission to review to grant award. Applications can contain custom form fields, supporting documents, contributors, and be organized by categories and chapters. Each application progresses through various statuses including draft, submitted, under review, and approved stages. - name: Assignments description: >- Use these operations to manage review assignments for evaluating grant applications. Assignments connect reviewers (or roles) with applications and scoring rubrics to facilitate the evaluation process. Assignments can be created individually or in bulk (asynchronous operations). Each assignment tracks completion status, scores, and panel membership. Assignments enable structured review workflows with configurable scoring criteria. - name: Attachments description: >- Use these operations to manage files uploaded to applications through attachment tabs. Attachments are distinct from field-based file uploads and allow for supplementary materials such as letters of support or compliance documents. Each attachment can have its own metadata and custom fields for categorization. Attachments remain associated with their application throughout the application lifecycle. - name: Categories description: >- Use these operations to manage funding categories or program areas. Categories organize applications into logical groups and can be hierarchical with parent-child relationships. Each category can have its own application form, chapter availability, submission limits, and custom labels. Categories support translated names and descriptions for multi-language grant programs. - name: Chapters description: >- Use these operations to manage geographic or organizational divisions within your grant programs. Chapters enable you to run regional funding programs, manage local grants, or organize by funding priorities. Applications can be assigned to chapters, and chapters can have their own administrators and configurations. Chapters support translated names and custom images for branding. - name: Contributors description: >- Use these operations to manage additional people associated with applications beyond the primary applicant. Contributors represent project team members, fiscal sponsors, or partners on a grant proposal. Each contributor can have their own custom fields and data collection requirements. Contributors are organized by tabs and can be managed independently from the main application. - name: Documents description: >- Use these operations to generate and retrieve PDF documents and data exports. Documents can be created based on application data, grantee data, compliance reports, or other program information. Document generation is asynchronous - after creating a document, poll the endpoint to check when generation is complete. Generated documents are available for download and can be associated with specific applicants or applications. - name: Fields description: >- Use these operations to manage custom form fields used to collect data throughout your grant programs. Fields can be attached to applications, users, contributors, attachments, and other resources. Supported field types include text, textarea, select, multi-select, date, file upload, table, and more. Fields support conditional logic, validation rules, and different protection levels. Note: Field deletion and updates are managed through the Good Grants interface. - name: Files description: >- Use these operations to retrieve information about uploaded files. Files provide metadata and download links for documents uploaded throughout the system. Access files using their secure token identifiers. Note: Files are read-only via this endpoint - file uploads are handled through resource-specific upload endpoints. - name: Forms description: >- Use these operations to retrieve application form structures and configurations. Forms define the data collection structure for grant applications within categories. Each form contains custom fields organized into tabs, along with content blocks and call-to-action elements. Forms support various types including application forms, review forms, and nomination forms. Note: Forms are read-only via the API and must be configured through the Good Grants interface. - name: Funds description: >- Use these operations to manage budget sources for allocations and grants. Funds represent pools of money available for distribution, such as "Innovation Fund 2026" or "Community Development Budget". Each fund tracks its budget, currency, and can have multiple allocations drawn against it. Funds enable financial tracking and reporting across your grant-making programs. - name: Grant reports description: >- Use these operations to manage grant reports and post-award compliance documentation. Grant reports track progress reporting requirements and outcomes for awarded grants. Reports capture applicant information, application details, custom form fields, and status tracking. - name: Grant statuses description: >- Use these operations to retrieve custom grant lifecycle statuses. Grant statuses provide additional status tracking beyond standard application review statuses. These are used to track stages like "Eligibility Review", "Compliance Check", "Funding Approved", "Grant Agreement Signed". Note: Grant statuses are read-only via the API and must be configured through the Good Grants interface. - name: Leaderboard description: >- Use these operations to retrieve ranking results and scores for applications. The leaderboard shows how applications rank based on score sets, with support for filtering by category, chapter, and tags. Results can be filtered to show specific subsets of the funding program. Note: The leaderboard is read-only and reflects calculated results from the review process. - name: Rounds description: >- Use these operations to retrieve round information for your grant programs. Rounds represent phases within a funding cycle, such as application rounds, review rounds, or decision rounds. Each round has specific start and end dates, associated forms, and can be scoped to specific chapters. Note: Rounds are read-only via the API and must be managed through the Good Grants interface. - name: Score sets description: >- Use these operations to retrieve scoring rubrics and evaluation criteria. Score sets define the questions, scoring scales, and calculation methods used to evaluate grant applications. Score sets can operate in different modes including scoring, ranking, and decision-making. Note: Score sets are read-only via the API and must be configured through the Good Grants interface. - name: Seasons description: >- Use these operations to retrieve information about funding cycles (seasons). A season represents a time-bound grant program instance, such as "2026 Community Grants" or "Q1 2026 Innovation Fund". Seasons contain forms, rounds, categories, and chapters. Seasons progress through statuses: draft, active, archived, and destroyed. Note: Seasons are read-only via the API and must be managed through the Good Grants interface. - name: Taxes description: >- Use these operations to retrieve tax configurations for financial transactions. Tax settings define how taxes are calculated and applied to orders and payments. Note: Tax configurations are read-only via the API and must be managed through the Good Grants interface. - name: Users description: >- Use these operations to manage user accounts in your grant-making organization. Users represent people who interact with your programs, including applicants, reviewers, administrators, and other roles. Users can be assigned roles, have custom profile fields, receive notifications, and authenticate via API tokens. Each user has a unique slug identifier and can participate across multiple funding cycles. - name: Webhooks description: >- Use these operations to manage webhook subscriptions for real-time event notifications. Webhooks notify your external systems when events occur in Good Grants, such as application submissions, status changes, or payment completions. Available events include: application created, application submitted, application status changed, payment success, user confirmed, and 20+ more. Configure webhooks to send HTTP POST requests to your specified URLs with event payloads. paths: /leaderboard: get: tags: - Leaderboard summary: Retrieve leaderboard results description: >- Retrieves leaderboard results. A missing or unresolvable `score_set` parameter returns `404 Not Found`. operationId: GetLeaderboardCollectionV23 parameters: - $ref: '#/components/parameters/leaderboardScoreSetFilter' - $ref: '#/components/parameters/categoryFilter' - $ref: '#/components/parameters/chapterFilter' - $ref: '#/components/parameters/entryFilter' - $ref: '#/components/parameters/tagFilter' - $ref: '#/components/parameters/archivedFilter' - $ref: '#/components/parameters/page' - $ref: '#/components/parameters/perPage' - $ref: '#/components/parameters/leaderboardOrder' - $ref: '#/components/parameters/sortDirection' - $ref: '#/components/parameters/Accept' - $ref: '#/components/parameters/X-Api-Language' responses: '200': description: Leaderboard results retrieved. headers: ETag: $ref: '#/components/headers/ETag' X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/LeaderboardList' application/xml: schema: $ref: '#/components/schemas/LeaderboardList' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooManyRequests' '503': $ref: '#/components/responses/ServiceUnavailable' components: parameters: leaderboardScoreSetFilter: name: score_set in: query required: true description: Filter by score set slug. schema: type: string categoryFilter: name: category in: query required: false description: Filter by category slug. schema: type: string chapterFilter: name: chapter in: query required: false description: Filter by chapter slug. schema: type: string entryFilter: name: application in: query required: false description: Filter by application slug. schema: type: string tagFilter: name: tag in: query required: false description: Filter by tag. schema: type: string archivedFilter: name: archived in: query required: false description: |- Filter by archive mode. * `only` - Show only archived resources. * `all` - Include archived resources. * `none` - Exclude archived resources. schema: type: string enum: - only - all - none page: name: page in: query required: false description: Specify the page number to return. schema: type: number perPage: name: per_page in: query required: true description: > Limit the number of items returned to between 1 and 100. If you provide a value outside this range, you will receive a `400` response. schema: type: number leaderboardOrder: name: order in: query required: false description: |- Sort by a supported leaderboard field. * `category` - Sort by category slug. * `chapter` - Sort by chapter slug. schema: type: string enum: - category - chapter - division - link - slug - status - submitted - auto_score - title - tags sortDirection: name: dir in: query required: false description: >- Sort in ascending or descending order. Invalid values are rejected with `400 Bad Request`. schema: type: string enum: - asc - desc Accept: name: Accept in: header required: true description: Defines the response type. schema: type: string enum: - application/vnd.Creative Force.v2.3+json - application/vnd.Creative Force.v2.3+xml X-Api-Language: name: x-api-language in: header required: false description: >- Defines the languages included in the response. If non are provided, the account default language is returned. Value `all` overrides any other values present. You can request multiple languages using a comma-separated string of languages. The selected language must be supported by your account or a `400` error is returned. style: simple explode: false schema: type: array items: type: string enum: - all - ar_AR - bg_BG - bn_IN - ca_ES - cs_CZ - cy_GB - da_DK - de_DE - en_GB - en_US - el_GR - es_NN - es_LA - et_EE - fa_NN - fi_FI - fr_FR - fr_CA - he_IL - hi_IN - hr_HR - hu_HU - hy_AM - it_IT - ja_JP - ko_KR - lt_LT - ms_MY - nl_NL - nb_NO - pl_PL - pt_BR - ro_RO - ru_RU - sk_SK - sl_SI - sq_AL - sr_RS - sv_SE - sw_NN - th_TH - tr_TR - uk_UA - vi_VN - zh_CN - zh_HK example: - en_GB - fr_FR headers: ETag: description: Entity tag for the selected representation. schema: type: string X-RateLimit-Limit: description: Maximum number of requests allowed per minute. schema: type: integer example: 60 X-RateLimit-Remaining: description: Number of requests remaining in the current rate limit window. schema: type: integer example: 58 X-RateLimit-Reset: description: Unix timestamp when the rate limit window resets. schema: type: integer example: 1783470988 Retry-After: description: Number of seconds the client should wait before retrying. schema: type: integer example: 60 schemas: LeaderboardList: title: Leaderboard list description: >- Paginated leaderboard for a single score set. Wraps the ranked applications in `data` with the score set and season they belong to, alongside the standard pagination envelope. allOf: - $ref: '#/components/schemas/Pagination' - type: object properties: data: type: array description: Leaderboard rows for the current page. items: $ref: '#/components/schemas/Leaderboard' score_set: type: object description: Score set the leaderboard is calculated for. properties: slug: type: string description: Short URL-safe identifier for the score set. name: type: object description: >- Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string. additionalProperties: type: string mode: type: string enum: - voting - qualifying - scoring - top_pick description: |- Scoring mode of the score set. Determines the shape of each row's `scores` object. form: type: object description: Form the score set scores applications from. properties: slug: type: string description: Short URL-safe identifier for the form. link: type: string format: uri description: Canonical URL for the form resource. name: type: object description: >- Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string. additionalProperties: type: string season: type: object description: Season the leaderboard belongs to. properties: slug: type: string description: Short URL-safe identifier for the season. link: type: string format: uri description: Canonical URL for the season resource. name: type: object description: >- Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string. additionalProperties: type: string example: current_page: 1 data: - slug: AbCdEfGh title: Sustainable Cities Initiative tags: '' category: slug: IjKlMnOp link: https://api.au.cr4ce.com/category/IjKlMnOp name: en_GB: Documentary chapter: slug: QrStUvWx link: https://api.au.cr4ce.com/chapter/QrStUvWx name: en_GB: United Kingdom division: null submitted: '2026-01-15T09:00:00Z' auto_score: 0 status: submitted grant_status: null link: https://api.au.cr4ce.com/application/AbCdEfGh scores: total_votes: 12 - slug: MnOpQrSt title: Ocean Cleanup Documentary tags: '' category: slug: IjKlMnOp link: https://api.au.cr4ce.com/category/IjKlMnOp name: en_GB: Documentary chapter: slug: QrStUvWx link: https://api.au.cr4ce.com/chapter/QrStUvWx name: en_GB: United Kingdom division: null submitted: '2026-01-12T14:20:00Z' auto_score: 0 status: submitted grant_status: null link: https://api.au.cr4ce.com/application/MnOpQrSt scores: total_votes: 9 first_page_url: https://api.au.cr4ce.com/leaderboard?score_set=UvWxYzAb&page=1 from: 1 last_page: 1 last_page_url: https://api.au.cr4ce.com/leaderboard?score_set=UvWxYzAb&page=1 next_page_url: '' path: https://api.au.cr4ce.com/leaderboard per_page: 10 prev_page_url: '' to: 2 total: 2 score_set: slug: UvWxYzAb name: en_GB: Voting mode: voting form: slug: GhIjKlMn link: https://api.au.cr4ce.com/form/GhIjKlMn name: en_GB: Application form season: slug: CdEfGhIj link: https://api.au.cr4ce.com/season/CdEfGhIj name: en_GB: '2025' Pagination: type: object title: Pagination description: >- Pagination envelope returned by every list endpoint. Wraps the result set with positional fields (`current_page`, `from`, `to`, `total`) and navigation URLs (`first_page_url`, `last_page_url`, `next_page_url`, `prev_page_url`) for traversing the full list. The records themselves are returned in a sibling `data` array supplied by the wrapping schema. properties: current_page: type: integer description: Number of the page returned by this response. The first page is `1`. first_page_url: type: string description: >- URL of the first page in the result set. Relative when the requested page is beyond the last page. from: type: - integer - 'null' description: >- Position of the first record on this page within the full result set. The first record is at position `1`. `null` when the requested page is beyond the last page. last_page: type: integer description: Number of the last page. Equals the total number of pages. last_page_url: type: string description: >- URL of the last page in the result set. Relative when the requested page is beyond the last page. next_page_url: type: string description: |- URL of the next page in the result set. Empty string when the current page is the last page. path: type: string description: Canonical URL of the endpoint, without query parameters. per_page: type: integer minimum: 1 maximum: 100 default: 10 description: Maximum number of records returned per page. prev_page_url: type: string description: |- URL of the previous page in the result set. Empty string when the current page is the first page. to: type: - integer - 'null' description: >- Position of the last record on this page within the full result set. `null` when the requested page is beyond the last page. total: type: integer description: Total number of records across all pages. Leaderboard: title: Leaderboard description: >- Single row in a score-set leaderboard, representing one application and its scores under the selected score set. Combines the identifying details for the application (title, category, chapter, division, and tags) with its auto-score, status, and a `scores` object whose shape depends on the mode of the score set. type: object properties: slug: type: string description: Short URL-safe identifier for the application. title: type: string description: Title of the application as submitted by the applicant. tags: type: string description: |- Comma-separated tags applied to the application. Empty string when no tags are applied. category: type: - object - 'null' description: |- Category the application was submitted to. `null` when the application is not assigned to a category. properties: slug: type: string description: Short URL-safe identifier for the category. link: type: string format: uri description: Canonical URL for the category resource. name: type: object description: >- Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string. additionalProperties: type: string chapter: type: - object - 'null' description: |- Chapter the application belongs to. `null` when the application is not assigned to a chapter. properties: slug: type: string description: Short URL-safe identifier for the chapter. link: type: string format: uri description: Canonical URL for the chapter resource. name: type: object description: >- Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string. additionalProperties: type: string division: type: - string - 'null' description: |- Division the application is assigned to. `null` when the application is not assigned to a division. submitted: type: string format: date-time description: Date and time the application was submitted, in ISO 8601 format. auto_score: type: - number - 'null' description: >- Automated score calculated from the auto-scored fields of the application. `null` when the application has no auto-scored fields. status: type: string description: Submission status of the application. grant_status: type: - string - 'null' description: |- Grant status of the application. `null` unless grants are enabled on the account. link: type: string format: uri description: Canonical URL for the application resource. scores: description: >- Scores for the application under the selected score set. The shape depends on the mode of the score set: `voting`, `qualifying`, `scoring`, or `top_pick`. anyOf: - title: Voting type: object description: Scores returned for a `voting` score set. properties: total_votes: type: integer description: Total number of votes the application received. - title: Qualifying type: object description: Scores returned for a `qualifying` score set. properties: final_decision: type: - string - 'null' enum: - pass - fail - unsure description: |- Qualifying decision recorded for the application. `null` when no decision has been recorded. - title: Scoring type: object description: Scores returned for a `scoring` score set. properties: total_score: type: object description: Aggregated score across all criteria. properties: value: type: number description: Total score awarded across all criteria. max_score: oneOf: - type: integer - type: string description: |- Maximum achievable total score. Empty string when no maximum is configured. final_score: type: string description: >- Formatted total score, such as `8/10`. Returns `-` when no maximum is configured. criteria: type: array description: Per-criterion scores making up the total. items: type: object properties: name: type: object description: >- Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string. additionalProperties: type: string value: type: number description: Score awarded for the criterion. max_score: type: integer description: Maximum achievable score for the criterion. final_score: type: string description: Formatted criterion score, such as `4/5`. weight: type: number description: Relative weight of the criterion in the total. - title: Top pick type: object description: >- Scores returned for a `top_pick` score set. Keyed by preference position (for example, `preference_1`), with the number of reviewers who ranked the application at that position. additionalProperties: type: integer example: slug: AbCdEfGh title: Sustainable Cities Initiative tags: '' category: slug: IjKlMnOp link: https://api.au.cr4ce.com/category/IjKlMnOp name: en_GB: Documentary chapter: slug: QrStUvWx link: https://api.au.cr4ce.com/chapter/QrStUvWx name: en_GB: United Kingdom division: null submitted: '2026-01-15T09:00:00Z' auto_score: 0 status: submitted grant_status: null link: https://api.au.cr4ce.com/application/AbCdEfGh scores: total_score: value: 8 max_score: 10 final_score: 8/10 criteria: - name: en_GB: Originality value: 4 max_score: 5 final_score: 4/5 weight: 1 BadRequest: allOf: - $ref: '#/components/schemas/BaseProblem' - type: object properties: status_code: type: integer minimum: 400 maximum: 400 Unauthorized: allOf: - $ref: '#/components/schemas/BaseProblem' - type: object properties: status_code: type: integer minimum: 401 maximum: 401 Forbidden: allOf: - $ref: '#/components/schemas/BaseProblem' - type: object properties: status_code: type: integer minimum: 403 maximum: 403 NotFound: allOf: - $ref: '#/components/schemas/BaseProblem' - type: object properties: status_code: type: integer minimum: 404 maximum: 404 TooManyRequests: allOf: - $ref: '#/components/schemas/BaseProblem' - type: object properties: status_code: type: integer minimum: 429 maximum: 429 BaseProblem: description: Standard error envelope shared by every error response on this API. type: object properties: message: type: string status_code: type: integer minimum: 400 maximum: 599 responses: BadRequest: description: >- Request was rejected before the endpoint could process it. Common causes: invalid `Accept` header, unsupported `x-api-language` code, empty request body on `POST` / `PUT`, invalid JSON in the request body, or an invalid slug format in a path parameter. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/BadRequest' application/xml: schema: $ref: '#/components/schemas/BadRequest' Unauthorized: description: Missing `x-api-key` header. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Unauthorized' application/xml: schema: $ref: '#/components/schemas/Unauthorized' Forbidden: description: |- Authenticated request denied. Common causes: invalid or unknown API key, suspended account, or `api` feature not enabled for the account. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Forbidden' application/xml: schema: $ref: '#/components/schemas/Forbidden' NotFound: description: >- Resource identified by the path slug does not exist. Returned when the slug is well-formed but no record matches it. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/NotFound' application/xml: schema: $ref: '#/components/schemas/NotFound' TooManyRequests: description: Rate limit of 60 requests per minute exceeded. headers: Retry-After: $ref: '#/components/headers/Retry-After' content: application/json: schema: $ref: '#/components/schemas/TooManyRequests' application/xml: schema: $ref: '#/components/schemas/TooManyRequests' ServiceUnavailable: description: Service is temporarily unavailable due to regional maintenance. content: application/json: schema: type: object properties: status: type: string description: Human-readable maintenance status. example: status: Maintenance in progress application/xml: schema: type: object properties: status: type: string description: Human-readable maintenance status. example: status: Maintenance in progress securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: |- API key used to authenticate and authorise every request. Include it in the `x-api-key` header. ````