API & development

Applications, WordPress, Git and schedules API

All 19 versioned routes in this family with authorization and request boundaries.

Platform
Go
Technology
Go

Read this contract with the installed version

Use API authentication and request conventions first. Paths below are normalized; mount under the correct local Admin or Customer namespace. Every handler independently enforces current authorization, resource/account scope, feature/licence state and actual installed capability. A listed route is not a token-scope grant or native production acceptance. Read the operational procedure and fields before changing data. The newer source reference includes preparation/activation routes which earlier kits may not expose.

Every route in this family

Method Normalized path Request and effect
GET /v1/application-capabilities Read authorized state/content; inspect observation time and pagination.
POST /v1/application-secrets Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
GET /v1/applications Read authorized state/content; inspect observation time and pagination.
POST /v1/applications Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
GET /v1/applications/{id} Read authorized state/content; inspect observation time and pagination.
GET /v1/applications/{id}/releases Read authorized state/content; inspect observation time and pagination.
GET /v1/applications/{id}/logs Read authorized state/content; inspect observation time and pagination.
GET /v1/applications/{id}/logs/{log_id}/content Read authorized state/content; inspect observation time and pagination.
POST /v1/applications/{id}/wordpress/update Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/git/deploy Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/git/rollback Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/suspend Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/reactivate Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/terminate Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
GET /v1/applications/{id}/schedules Read authorized state/content; inspect observation time and pagination.
POST /v1/applications/{id}/schedules Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/schedules/{schedule_id}/update Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/schedules/{schedule_id}/delete Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.
POST /v1/applications/{id}/schedules/{schedule_id}/run Explicit typed mutation; use the current revision/preview/CSRF or separately authorized token contract as applicable.

Delivery, verification and errors

A returned operation or 202 means accepted work, not completed service change. Retain the operation ID and inspect events and actual resource state. Preserve one idempotency key for a reviewed ambiguous-delivery attempt. Current revision/ETag, exact impact preview and confirmation are separate protection mechanisms; do not guess or reuse stale values.

For 401, restore a valid local session/token. For 403, inspect the actual typed authorization/freshness/licence denial; generic denial is not automatically a password prompt. For 409, reload changed state or inspect the original operation. A capability/storage/agent 503 stays unavailable. Never place passwords, bearer tokens, private keys or recovery material in a URL. The complete request/response field reference distinguishes internal lifecycle models from public client input.

← All EmailaPanel guidesGet help →

Need help with EmailaPanel?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila