Create Entity
Entity Endpoints
Create Entity
Create a new entity, with optional file upload support
POST
Create Entity
Creates a new entity in your project. Supports optional file uploads viaDocumentation Index
Fetch the complete documentation index at: https://docs.replyke.com/llms.txt
Use this file to discover all available pages before exploring further.
multipart/form-data. When no files are attached, use application/json. The entity is attributed to the authenticated user unless excludeUserId is set.
Body Parameters
Your application’s identifier for this entity (URL, slug, database ID, etc.). Used to fetch or create entities without knowing the Replyke ID.
Groups entities by source. Use a topic ID or page ID to scope feeds to a specific context.
The ID of the space this entity belongs to. The space must exist in the same project.
Attribute the entity to a specific user. Must match the authenticated user ID unless the request uses a service or master key.
A title or headline for the entity.
The main body text of the entity.
An array of generic attachment objects. Each item is a free-form JSON object — structure is defined by your application.
Tags or keywords associated with this entity. Used for keyword-based filtering in the list endpoint.
Users or spaces mentioned in this entity. Each object is a discriminated union:
{ type: "user", id: string, username: string, foreignId?: string }{ type: "space", id: string, slug: string }
Geographic coordinates for this entity. Enables proximity-based filtering.
A free-form JSON object for any custom data your application needs alongside the entity. Supports rich filtering via
metadataFilters in the list endpoint.When
true, the entity is saved as a draft and excluded from public feeds. Publish it later via the Publish Entity endpoint.When
true, the entity is created without user attribution even if a user is authenticated.When
true, returns 401 if no user is authenticated.ISO 8601 datetime to backfill a creation timestamp. Service or master key only.
ISO 8601 datetime for
updatedAt. Requires createdAt to also be set. Must be ≥ createdAt. Service or master key only.File Uploads (multipart/form-data)
When uploading files, send the request asmultipart/form-data. All JSON fields above are sent as form fields.
Image files to attach. Maximum 10 images, 50 MB each. Must be valid images. Requires
images.options.Stringified JSON describing how to process uploaded images. Must include a
mode field:"exact-dimensions"— resize to specific pixel dimensions per variant"aspect-ratio-width-based"— resize by width maintaining aspect ratio"aspect-ratio-height-based"— resize by height maintaining aspect ratio"original-aspect"— preserve original ratio, resize by max dimension"multi-aspect-ratio"— generate crops at multiple aspect ratios
quality (1–100), format (webp, jpeg, png, original), stripExif (boolean), pathParts (string[]).Generic files to attach. Maximum 10 files, 50 MB each.
Stringified JSON for file options. Optional
pathParts (string[]) customizes the storage path.Response
Returns the created Entity object. When files are uploaded, the entity includes afiles array with signed URLs for each attachment.
Draft entities are invisible to all users until published. Use Fetch Drafts to list an author’s unpublished drafts.
Error Responses
User Required — 401
User Required — 401
Unauthorized User ID — 403
Unauthorized User ID — 403
Space Not Found — 404
Space Not Found — 404
Invalid Timestamp — 400
Invalid Timestamp — 400
updatedAt is earlier than createdAt:File Too Large — 413
File Too Large — 413
Invalid Image — 422
Invalid Image — 422

