Refresh package lists on receiving server

POST

/apt/update

Last modified:2026-10-30 21:14:54

OperationId:RefreshPackageListsLocal

Runs apt update on the server that receives the request, so apt sees the newest versions its repositories offer. It installs nothing. Requires Super User scope. To choose the server, use POST /apt/update/{hostname}.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Query Params

Header Params

Body Params application/json

Examples

Responses

🟢200OK

text/plain

apt output as plain text, streamed while the command runs. The connection stays open until apt finishes, which can take several minutes. The text starts with an Executing command: line and ends with Command executed successfully with exit code: 0 or Command failed with exit code: <n>. Both lines carry ANSI color codes. A failed apt run still answers 200, so read the last line, not the status code. If another apt operation holds the apt lock, the request waits up to 20 minutes for it, then answers 409 instead of streaming. Each server also runs apt update on its own every 6 hours.

🟠401Authentication Required

🟠403Forbidden

🟠409Conflict

🟠429Too Many Requests

🔴500Server Error

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/apt/update?ticket=API-1234' \
--header 'X-Ticket: API-1234' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
  "ticket": "API-1234"
}'

Response Example

200 - apt update



Executing command: sudo apt update
Hit:1 https://aptng.example.com/aptng/netsapiens/v46.0 noble InRelease
Reading package lists...
Building dependency tree...
All packages are up to date.

Command executed successfully with exit code: 0

Modified at 2026-10-30 21:14:54

List installed packages on server

List repositories on server