Skip to main content
POST
/
templates
Create new template
curl --request POST \
  --url https://api.nexrender.com/api/v2/templates \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "type": "aep",
  "displayName": "<string>"
}'
{
  "id": "<string>",
  "type": "<string>",
  "displayName": "<string>",
  "status": "<string>",
  "createdAt": "2023-11-07T05:31:56Z",
  "updatedAt": "2023-11-07T05:31:56Z",
  "compositions": [
    "<string>"
  ],
  "layers": [
    "<string>"
  ],
  "mogrt": {},
  "error": "<string>",
  "uploadInfo": {
    "url": "<string>",
    "method": "PUT",
    "fields": {},
    "expiresIn": 123,
    "key": "<string>"
  }
}
Before uploading your project files, you need to register a template object using the Nexrender Cloud API. This tells the system:
  • What type of template you’re going to upload (aep, zip, or mogrt)
  • How to label this template for your internal reference

​
What Happens Behind the Scenes?

  • The backend reserves storage for your file
  • Generates a secure upload URL valid for ~1 hour
  • Waits for the actual file to be uploaded (in the next step)
  • The template status is initially set to awaiting_upload
You must upload the correct file matching the declared type — otherwise the introspection process will fail.

​
Common Mistakes to Avoid

MistakeResult
Declaring type: zip but uploading .aep or .mogrtThe render job will fail or silently break asset resolution
Uploading to the wrong URLThe template will remain in awaiting_upload status
Forgetting to use the pre-signed URLYou’ll get a 403 Forbidden error or SignatureDoesNotMatch
Once the upload is complete, the status will transition to uploaded, and Nexrender Cloud will extract all available compositions and dynamic layers.

​
API Reference

Authorizations

​
Authorization
string
header
required

Bearer token authentication using API tokens for team-based access control.

You can generate your own API token at: https://app.nexrender.com/team/settings

Body

application/json

Configuration for creating a new template with project file type and display information

​
type
enum<string>
required

Template project file type - aep (After Effects Project), zip (compressed project), or mogrt (Motion Graphics Template)

Available options:
aep,
zip,
mogrt
​
displayName
string
required

Human-readable name for the template shown in UI and listings

Response

Template successfully created with upload information

Complete template object with metadata, processing status, and content information

​
id
string

Unique template identifier used for referencing in jobs and API operations

​
type
string

Template file format (aep, zip, or mogrt)

​
displayName
string

Human-readable name displayed in UI and template listings

​
status
string

Current processing status (awaiting_upload, processing, uploaded, error)

​
createdAt
string<date-time>

ISO timestamp when the template was initially created

​
updatedAt
string<date-time>

ISO timestamp of the most recent template modification

​
compositions
string[]

List of compositions found within the template that can be rendered

Individual composition name available for rendering

​
layers
string[]

List of layers available for asset replacement and manipulation

Individual layer name within the template

​
mogrt
object

Motion Graphics Template specific metadata and properties

​
error
string | null

Error message if template processing or validation failed (null if successful)

​
uploadInfo
object

Presigned upload URL and metadata for securely uploading template files to cloud storage

⌘I