Skip to main content

In your app

A controller answers a route on your app: it calls getFileFolder() and returns the answer.

Add the controller

app/controllers/get_file_folder_controller.ts

Add the route

start/routes.ts

Call it

Terminal
With node ace serve running, it prints its answer as JSON.

Find the id

id is the document’s _id, from a list. Ask the list for only the fields you need: each row is a document’s id and those fields.
AdonisJS
Pass row.id as id. See Find an id.

Required parameters

One object, e.g. getFileFolder({ id }); leave out the optional fields.
string
required
Required. The document’s _id: a full id names its own locale and mode (the draft’s …:en:draft, the published one’s …:en:published; no aposMode needed), a bare aposDocId takes the request’s (aposLocale, aposMode).
boolean | null | undefined
Optional. Leave it out and the site uses false. true: each area’s widgets come back rendered as HTML (_rendered), beside their data.
A FileFolder. FileFolder content type. Read its properties (fileFolder.title): each says whether the site always sends it. The example answer is the site’s wire JSON: some keys differ from the property names (_id → id, _parent → parent).
string
Always sent. Its title: the name it goes by in every list, and the heading of its page where it has one.
string
Always sent. The URL name: lowercase words joined by hyphens (letters outside a–z, even emoji, are kept).
Visibility
Always sent. Select whether this content is public or private. One of public, loginRequired; a newer site may send others, so keep a fallback.
string
Always sent. The document’s id. On a type with drafts it ends in its locale and mode (…:en:published, …:en:draft): the part before the first colon is its aposDocId, shared by both copies. The {_id} the type’s routes take.
string
Always sent. The document type’s name: always this type’s.
Date
Always sent. When it was created (ISO 8601). Format: an ISO 8601 date and time.
Date
Always sent. When it last changed (ISO 8601). Format: an ISO 8601 date and time.
readonly Readonly<Record<string, unknown>>[] | null
Sometimes sent: undefined when the site leaves it out, and it can be null. The related file-folder documents, in order (empty when none). To set it, send a list of { "_id": "…" }, one per document (one at most); a document the site can’t find is left out. At most 1 items.
boolean | null
Sometimes sent: undefined when the site leaves it out, and it can be null. Media in this folder (and every folder inside it) are kept for comparison only: you can browse them here, but they can never be used on the site.
boolean | null
Sometimes sent: undefined when the site leaves it out, and it can be null. In the archive: kept, but out of every list and off the site until it is restored. false (or null) for a live document.
string | null
Sometimes sent: undefined when the site leaves it out, and it can be null. Its place in the tree: each folder’s URL name from the top, joined by / (albums/summer). Set by the site from _parent and title; a value sent is ignored.
string | null
Sometimes sent: undefined when the site leaves it out, and it can be null. The parent folder’s id, empty at the top. Set by the site from _parent; a value sent is ignored.
string | null
Sometimes sent: undefined when the site leaves it out, and it can be null. Its own part of folderPath, made from its title. Set by the site; a value sent is ignored.
number | null
Sometimes sent: undefined when the site leaves it out, and it can be null. How deep it sits: 0 at the top. Set by the site from _parent; a value sent is ignored.
Nothing to catch: the SDK retries what is safe, and throws the rest as the classes below. Your exception handler turns them into your app’s own answers, once for every call (see Map SDK errors to responses); catch only what you want to react to here.
400
The site refused what was sent: errors lists each field’s problem, siteMessage the first.Retried first: No. Read: errors (field → messages), siteMessage.
401
The API key is missing or refused (malformed, revoked, expired), or a signature its signing mode needs is missing or stale.Retried first: No. Read: siteMessage, errorName, data.
403
The key may not do this: a scope it lacks, or an address outside its allowlist. siteMessage names it.Retried first: No. Read: siteMessage, errorName, data.
404
Nothing matches, or the caller may not see it.Retried first: No. Read: siteMessage, errorName, data.
500
The site failed. Its logs say why.Retried first: No (only a 502, 503 or 504 is retried). Read: siteMessage, errorName, data.
no answer
No answer: DNS, a refused connection, TLS, or the timeout (15 s per attempt by default).Retried first: Yes, after 0.5 s then 1 s. Read: reason, neverConnected.
not sent
The client refused to send it (e.g. a path segment of ..); the site never saw it.Retried first: No. Read: reason (what to change).
any other
Any other status, or a success whose JSON doesn’t match this SDK version’s types (update the SDK).Retried first: No. Read: reason, status.
setup
sites.forSite('acme') named a slug config/attract.ts doesn’t list (with the keys in the database: no row in attract_api_keys).Retried first: No: nothing was sent. Read: message, slug.
setup
The site’s entry is wrong: a malformed baseUrl or key, a key filed under another slug, or no default site. node ace attract:check names the fix.Retried first: No: nothing was sent. Read: message (what to fix).

Behavior

  • Access: an API key with content:files:read (or a master above it: content:files:all, content:all, admin:all) reads the published documents. A signed-in person may call it as far as their own permissions allow; anyone else gets 404.
  • Rate limit: the key’s own reads-per-minute limit, set when the key is created (default 600); over it, 429 with Retry-After. The client waits and retries for you; you see RateLimited only if that runs out.
  • Retries: a read is safe to repeat: the client retries it on no answer, a 502/503/504 and a 429.
  • Timeout: 15 s per attempt by default; raise timeout (milliseconds) in config/attract.ts for longer.

More examples

Test it

It calls the controller above with the SDK faked: fakeAttract() puts the fake in the container for this one test, and it answers every call with a valid example, so nothing leaves your machine and no key is read. Save it as tests/unit/file_folders_get_file_folder.spec.ts, then run your tests:
tests/unit/file_folders_get_file_folder.spec.ts
Terminal
Answer with your own values: fake fileFolders.getFileFolder with factories.FileFolder({...}), the fields you give over a valid example.
tests/unit/file_folders_get_file_folder_answers.spec.ts

Get the file folder tree

site.fileFolders().getFileFolderTree()

List file folders

site.fileFolders().listFileFolders()

Create a file folder

site.fileFolders().createFileFolder()

Replace a file folder

site.fileFolders().replaceFileFolder()

Delete a file folder

site.fileFolders().deleteFileFolder()

Update a file folder

site.fileFolders().updateFileFolder()

GET /file-folder/{_id}

The endpoint this calls, in the API reference: the HTTP request and answer, and every rule the site checks.