AlayaCare Directory API
The Directory API from AlayaCare — 1 operation(s) for directory.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/alayacare-directory-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
version: 1.0.0
title: AlayaCare External Files Directory API
description: '**Remarks:**
Please note that the difference between a `Directory` and a `File` resource is that `Directory` requires a trailing `/` at the end of the path
**AlayaCare IDs:**
The following terms are used to reference IDs that identify resources in AlayaCare:
- id
'
servers:
- url: https://homecare.alayacare.com/ext/api/v2/files
tags:
- name: Directory
paths:
/client/{id}/{path}/:
parameters:
- name: id
in: path
required: true
schema:
type: integer
- name: path
in: path
required: true
schema:
type: string
get:
tags:
- Directory
summary: Get the content of a directory
responses:
200:
description: Content of a directory
content:
application/json:
schema:
type: array
items:
type: object
properties:
name:
type: string
description: Path to file or directory
example: client/1002/report.pdf
last_modified:
type: string
format: date-time
description: 'When the file or directory was last modified (ISO 8601)
'
example: '2017-07-08T13:30:00+00:00'
size:
type: integer
description: Size of the file in bytes
example:
- last_modified: '2016-01-14T18:58:44+00:00'
name: client/1002/Physician Order/
size: 0
- last_modified: '2016-08-24T18:45:29+00:00'
name: client/1002/picture.jpg
size: 5499
404:
description: Directory not found
content:
application/json:
schema:
$ref: '#/components/schemas/DirectoryNotFoundSchema'
post:
tags:
- Directory
summary: Create a new directory
description: 'Create a directory at the `path` location, along with the underlying folder structure if it doesn''t exist already
'
responses:
201:
description: Directory created
content:
application/json:
schema:
type: object
properties:
code:
type: integer
description: http status response code
example: 201
name:
type: string
description: Url to the directory created
example: client/1002/new directory/
400:
description: 'Bad Request: Can''t post a file when creating a directory
'
content:
application/json:
schema:
type: object
properties:
code:
type: integer
description: http status response code
example: 400
message:
type: string
description: Detail on the error
example: Can't post a file when creating a folder
put:
tags:
- Directory
summary: Copy or move a directory
description: 'Copy or move a directory and create the underlying folder structure of the new location if it doesn''t already exist.
Whether the directory is moved or simply copied is defined by a `move` header that can be set to `true` (if the header is not provided, its value defaults to `false` and the `source` directory will remain).
The url of the `PUT` request is the path to the destination location.
i.e., if we have the following directories:
- `dir1/child1/`
- `dir2/child2/`
and we want to copy `child1/` inside `dir2/` (the goal is to have `dir2/child1/`), the `path` in the url of the `PUT` request has to be: `dir2/child1/`. The `source` header of the request has to be `dir1/child1/`.
A 400 response will be returned for a request to move a folder in one of its own subfolders.
'
parameters:
- name: source
in: header
description: 'path of the directory to copy or move (source directory)
'
schema:
type: string
- name: move
in: header
description: 'specifies if the directory is moved or copied (defaults to false, i.e. copied)
'
schema:
type: boolean
responses:
200:
description: Directory copied or moved
content:
application/json:
schema:
type: object
properties:
code:
type: integer
description: http status response code
example: 200
name:
type: string
description: 'Url to the new location of the copied or moved directory
'
example: client/1002/new directory copied/
400:
description: 'Bad Request: Missing `source` header
'
content:
application/json:
schema:
type: object
properties:
message:
type: object
properties:
source:
type: string
description: Detail on the error
example: The request cannot be processed without the source variable
404:
description: Source Directory not found
content:
application/json:
schema:
$ref: '#/components/schemas/DirectoryNotFoundSchema'
delete:
tags:
- Directory
summary: Delete a directory
description: 'Delete a directory and its content. A `forced-delete` header set to `true` must be provided for the directory to be deleted. Otherwise, the reponse will be a confirmation message with a status `400`.
'
parameters:
- name: forced-delete
in: header
required: true
description: required header to delete a directory
schema:
type: boolean
responses:
204:
description: Directory deleted
400:
description: 'Bad Request: Missing `forced-delete` header
'
content:
application/json:
schema:
type: object
properties:
code:
type: integer
description: http status response code
example: 400
message:
type: string
description: Detailon the error
example: This action will delete the folder and its content. Please confirm
404:
description: Directory not found
content:
application/json:
schema:
$ref: '#/components/schemas/DirectoryNotFoundSchema'
components:
schemas:
DirectoryNotFoundSchema:
type: object
properties:
code:
type: integer
description: http status response code
example: 404
message:
type: string
description: detail on the error
example: Folder "Ghost Directory" not found