to navigate
to select
esc to close
GET Entries

Entries API

https://api.airogelcms.com/v1/accounts/:account_id/collections/:collection_id/entries

Entries are individual content items within a collection (e.g., individual blog posts, pages).

Supported Operations

  • GET /v1/accounts/:account_id/collections/:collection_id/entries - List entries
  • GET /v1/accounts/:account_id/collections/:collection_id/entries/:id - Get an entry
  • POST /v1/accounts/:account_id/collections/:collection_id/entries - Create an entry
  • PUT /v1/accounts/:account_id/collections/:collection_id/entries/:id - Update an entry
  • DELETE /v1/accounts/:account_id/collections/:collection_id/entries/:id - Delete an entry

Core Fields

FieldTypeRequiredDescription
handlestringyesURL-friendly identifier
titlestringyesDisplay title
publishedbooleannoWhether publicly visible
published_atdatetimenoPublication date (required for date-based routing)
include_in_sitemapbooleannoInclude in XML sitemap
positionintegernoManual sort order. Lower values appear first.
blueprint_handlestringnoWhich blueprint to use
template_handlestringnoOverride template
layout_handlestringnoOverride layout

Content Fields: Include any fields defined in the blueprint as top-level properties.

Field Value Formats

Image fields accept:

  • Asset path: "featured_image": "images/photo.jpg"
  • Asset prefix ID: "featured_image": "acass_abc123"

Entity fields (references to other entries) accept:

  • Entry prefix ID: "related_post": "cnety_xyz789"
  • Collection:Handle format: "related_post": "posts:my-other-post"

Parameters

Name Type Required Description
account_id string Required Your account ID
collection_id string Required Collection handle or ID
handle string Optional Filter by exact handle match
published boolean Optional Filter by published status
page integer Optional Page number (default: 1)

Request Example

# List entries
curl https://api.airogelcms.com/v1/accounts/$ACCOUNT_ID/collections/posts/entries \
  -H "Authorization: Bearer $API_TOKEN"

# Create entry
curl -X POST \
  -H "Authorization: Bearer $API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "handle": "my-first-post",
    "title": "My First Post",
    "published": true,
    "published_at": "2025-01-08T10:00:00Z",
    "position": 1,
    "body": "

Post content...

", "excerpt": "A brief summary", "featured_image": "images/photo.jpg" }' \ https://api.airogelcms.com/v1/accounts/$ACCOUNT_ID/collections/posts/entries

Response Example

{
  "data": [
    {
      "id": "cnety_abc123",
      "handle": "my-first-post",
      "title": "My First Post",
      "published": true,
      "published_at": "2025-01-08T10:00:00Z",
      "position": 1,
      "content_path": "/blog/my-first-post",
      "collection_handle": "posts",
      "blueprint_handle": "blog-post",
      "body": "

Post content...

", "excerpt": "A brief summary", "featured_image": "/assets/images/photo.jpg", "created_at": "2025-01-08T12:00:00Z", "updated_at": "2025-01-08T12:00:00Z" } ] }

Additional Notes

Content path auto-generation: URLs are automatically generated based on the collection's routing pattern. The path is returned in the response as content_path.

Entry ordering: For collections with orderable enabled, use the position field for manual ordering. Position always sorts ascending (lower values first).

Blueprint field values: All blueprint fields are flattened into the root object in responses and requests.