> ## Documentation Index > Fetch the complete documentation index at: https://docs.splose.com/llms.txt > Use this file to discover all available pages before exploring further. # Get a paged array of cases > Get a paged array of cases ## OpenAPI ````yaml get /cases openapi: 3.0.0 info: version: 1.0.0 title: splose public API description: "\nWelcome to the splose API documentation. splose serves as a comprehensive Allied Health & NDIS practice management software designed to streamline administrative tasks and foster the growth of your practice.\n\n# Introduction\nThe splose API follows a REST architectural style, offering JSON-encoded responses, standard HTTP response codes, easily understandable resource-oriented URLs, and robust authentication mechanisms.\n\n# Authentication\n### API Key Authentication\nThe splose API employs API keys for request authentication. Workspace owners can apply for and manage API keys through the splose dashboard. It's crucial to safeguard the API key, as it grants the same permissions as the associated user.\n\n### Bearer Authentication\nAuthentication for API access is achieved via Bearer Authentication. Include the API key in the request header using the format: `Authorization: Bearer your_api_key`.\n\n### Secure Communication\nAll API requests must be conducted over HTTPS. Requests made over plain HTTP will not succeed. Additionally, unauthenticated API requests will result in failure.\n\n# Rate limit\nThere are limits to the number of API calls that your application can make with one API key.\n\n+ Minute Limit: 60 calls per minute\n\n# Error\nsplose uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. \nCodes in the 4xx range indicate an error that failed given the information provided. Codes in the 5xx range indicate an error with splose's servers.\n\nError types:\n+ 400 - Bad request: the request failed due to missing or invalid parameters.\n+ 401 - Unauthorized: No valid API key provided.\n+ 404 - Not Found: \tThe requested resource doesn't exist.\n+ 429 - Too Many Requests: Too many requests hit the API too quickly.\n+ 500 - Internal Server Error : Something went wrong on splose's end.\n\n# Datetime\nAll datetime values provided in request parameters and responses are in Coordinated Universal Time (UTC). The accepted datetime formats are outlined below:\n+ 2023-07-01\n+ 2023-07-01T00:00:00Z\n+ 2023-07-01T00:00:00.000Z\n\n# Pagination\n\n### Pagination for Multiple Objects\nFor endpoints returning multiple objects, pagination is in place to manage response sizes. Each response is limited to a certain number of objects. \nAdditionally, the response includes a `links` field that provides URLs for fetching the next and/or previous pages, if applicable.\n\n### Manual Positioning\nYou have the option to manually specify the `id_gt` or `id_lt` value as a request parameter. This allows you to retrieve objects starting from a specific position. If neither of these values is provided, the initial page of objects will be returned by default.\n+ `id_gt`: Request for next page of objects with id greater than the specified value. \n+ `id_lt`: Request for previous page of objects with id less than the specified value. \n\n# Realtime feed\nCertain users may require real-time data retrieval. Given the substantial data volume, retrieving the complete dataset may not be efficient. To address this, we offer the option to retrieve data based on its update timestamp. This approach necessitates fetching the entire dataset only during the initial request. Subsequent retrievals involve fetching solely the modified data to replace outdated information.\n+ `update_gt`: Request for objects updated after the specified datetime. \n+ `update_lt`: Request for objects updated before the specified datetime. \n\n# Change log\n+ 2024-04-10: add payment method and payment endpoints\n+ 2024-02-28: add availability endpoint\n" contact: email: support@splose.com servers: - url: https://api.splose.com/v1 security: [] externalDocs: description: Find out more about splose url: https://splose.com paths: /cases: get: tags: - case summary: Get a paged array of cases description: Get a paged array of cases parameters: - schema: type: integer nullable: true description: The starting object id of the next page example: 200 required: false name: id_gt in: query - schema: type: integer nullable: true description: The starting object id of the previous page example: 100 required: false name: id_lt in: query - schema: anyOf: - type: string - type: string description: Search for objects updated after this date time example: '2023-07-30T09:00:00.000Z' required: false name: update_gt in: query - schema: anyOf: - type: string - type: string description: Search for objects updated before this date time example: '2023-07-30T09:00:00.000Z' required: false name: update_lt in: query - schema: type: string nullable: true enum: - 'true' - 'false' default: 'false' description: Whether archived objects should be retrieved, default is false required: false name: include_archived in: query - schema: type: number nullable: true description: Patient id example: 1 required: false name: patientId in: query - schema: type: number nullable: true description: Practitioner id example: 1 required: false name: practitionerId in: query - schema: type: number nullable: true description: Contact id example: 1 required: false name: contactId in: query - schema: type: string nullable: true enum: - Appointments - Hours - Budget description: Track type example: Budget required: false name: trackType in: query - schema: type: string nullable: true enum: - Open - Closed - Expired description: Status example: Open required: false name: status in: query responses: '200': description: A paged array of cases content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: integer minimum: 0 exclusiveMinimum: true description: Case id example: 1 caseNumber: type: string description: Case number example: '0002' budget: type: number nullable: true description: Budget example: 200 appointmentCount: type: number nullable: true description: Appointment count example: 12 contactId: type: integer nullable: true minimum: 0 exclusiveMinimum: true description: Contact Id example: 1 providerNumber: type: string nullable: true description: Provider number example: '1512' referralPeriod: type: string nullable: true description: Referral Period example: Standard issueDate: anyOf: - type: string - type: string - nullable: true description: Issued date in YYYY-MM-DD HH:MM:SS format example: '2024-06-09T14:30:00.000Z' expiryDate: anyOf: - type: string - type: string - nullable: true description: Expiry date in YYYY-MM-DD HH:MM:SS format example: '2024-06-25T14:29:59.000Z' notes: type: string nullable: true description: Notes example: Notes trackType: type: string enum: - Appointments - Hours - Budget description: Track type example: Budget hours: type: number nullable: true description: hours example: 32 includeDidNotArrive: type: boolean nullable: true description: Did not arrive example: true includeCancelled: type: boolean nullable: true description: Include cancelled example: true practitionerId: type: integer nullable: true minimum: 0 exclusiveMinimum: true description: Practitioner id example: 1 items: type: array items: type: object properties: typeId: type: integer minimum: 0 exclusiveMinimum: true description: Item type id example: 1 type: type: string enum: - Appointment - SupportActivity - File - SupportingActivity - Letter description: Item type example: Appointment required: - typeId - type additionalProperties: false description: >- An array of appointment connections associated with this case organisationId: type: integer minimum: 0 exclusiveMinimum: true description: Organisation id example: 1 patientId: type: integer minimum: 0 exclusiveMinimum: true description: Patient id example: 2 isOpen: type: boolean nullable: true description: Is open example: true hasAlert: type: boolean nullable: true description: Has alert example: true remindTime: type: string nullable: true description: Remind time example: Time utilisationAlert: type: number nullable: true description: Utilisation alert example: 1 isAlertUtilizationSent: type: boolean nullable: true description: Is alert utilization sent example: true createdAt: anyOf: - type: string - type: string description: Object creation date time example: '2023-07-30T09:00:00.000Z' updatedAt: anyOf: - type: string - type: string description: Object update date time example: '2023-07-30T09:00:00.000Z' required: - id - contactId - issueDate - expiryDate - hours - practitionerId - items - organisationId - patientId links: type: object properties: previousPage: type: string description: The link to retrieve next page example: /v1/${object_type}?id_gt=200 nextPage: type: string description: The link to retrieve previous page example: /v1/${object_type}?id_lt=100 required: - data - links security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer ````