Skip to main content

In your app

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

Add the controller

app/controllers/list_image_folder_photos_controller.ts

Add the route

start/routes.ts

Call it

Terminal
With node ace serve running, it prints its answer as JSON.
A reference folder (one whose images never feed a gallery) answers 404.

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. listImageFolderPhotos({ id }); leave out the optional fields.
string
required
Required. The folder’s document ID.
string | null | undefined
Optional. Leave it out and the site uses "1". Send 0 for this folder only; anything else includes its subfolders.
number | null | undefined
Optional. Leave it out and the site uses 200. At most this many photos. 1 to 200.
A ListImageFolderPhotosResponse. The folder and its photos. Read its properties (listImageFolderPhotos.folder): 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, _urls → urls).
ListImageFolderPhotosResponseFolder
Always sent. A ListImageFolderPhotosResponseFolder.
readonly GalleryPhoto[]
Always sent. A list of GalleryPhoto.
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.
401
The API key is missing, malformed, unknown, disabled, expired or archived, or a request its signing mode requires to be signed is not.Retried first: No. Read: siteMessage, errorName, data.
403
The API key lacks the scope this route needs (the message names it) or is used from outside its allowlist; or, on a route that answers 403 to everyone it refuses, the caller may not use it.Retried first: No. Read: siteMessage, errorName, data.
404
Nothing matches the identifier, or the caller may not use this route at all (it is not advertised).Retried first: No. Read: siteMessage, errorName, data.
429
The key used up its per-minute limit. Still, after the client’s own waits and retries.Retried first: Yes: the client waits Retry-After (1 s when absent; over 60 s it gives up at once) and retries, up to retries times (2 by default). Read: retryAfter (seconds, or null), siteMessage.
5xx
The site failed (or something in front of it did). Its logs say why.Retried first: A 502, 503 or 504: yes, after 0.5 s then 1 s. A 500: no. 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 images:read, or media:all, or admin:all, or any signed-in CMS user. The site’s own server may call it too. Other callers get 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.

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/image_folders_list_image_folder_photos.spec.ts, then run your tests:
tests/unit/image_folders_list_image_folder_photos.spec.ts
Terminal
Answer with your own values: fake imageFolders.listImageFolderPhotos with factories.ListImageFolderPhotosResponse({...}), the fields you give over a valid example (nested ones too).
tests/unit/image_folders_list_image_folder_photos_answers.spec.ts

Get the image folder tree

site.imageFolders().getImageFolderTree()

List image folders

site.imageFolders().listImageFolders()

Create an image folder

site.imageFolders().createImageFolder()

Get an image folder

site.imageFolders().getImageFolder()

Replace an image folder

site.imageFolders().replaceImageFolder()

Delete an image folder

site.imageFolders().deleteImageFolder()

GET /image-folder/{_id}/photos

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