Skip to main content
The API manages the registration of existing Remnawave subscriptions. Changes are delivered when you update your subscription through Gateway Axottle. The API does not create tariffs, change traffic limits, or give access to other people’s profiles. The Subscription Page → API tab shows the paths for the selected connection.

Authorization

You need a separate Bearer-token integration axt_…. Cookie-session panel, subscription link and the internal key page axsp_… for this API is not suitable. An administrator with settings.manage creates a token through POST /api/v1/internal-tokens using administrative panel authorization.
Replace CONNECTION_ID with the ID of the desired connection. The secret is returned once in the token field, the token identifier in token_info.id. Keep the secret on the integration server, not in the client application. The general scope of * does not open this API. Connection rights do not give you the right to change Flow.Flow right applies to all of its published profiles, including other connections. allowed_ips limits the IP/CIDR of Axottle’s direct network client. For reverse proxy, this is the proxy address, not the value of the client’s X-Forwarded-For. The blank list does not limit the source over IP.

Users and catalogues

Base path: /api/subscriptions/v1/connections/CONNECTION_ID. USER_UUID is the UUID of a Remnawave account, not a Telegram ID or subscription link token. The individual user’s reading, recording and preview checks it in Remnawave. The response does not reveal the original link or configuration keys. The main settings fields: Unknown fields are deflected. PATCH requires at least one field. PUT with an empty object resets all personal settings. Example of a theme change and personal announcement; variables are set on the integration server:
The preview is taken by the full draft settings, not the partial PATCH:
The result contains headings, topic applicability, selected message, audience matching, and Flow selection status.The actual intersection with available profiles is performed when a subscription is issued.

Announcements

Use GET /announcements, PUT /announcements/RULE_ID and DELETE /announcements/RULE_ID?version=N regarding the connection path. PUT accepts the complete rule. version: 0; to change, get the current version through GET. You must name up to 80 characters and text up to 200. all, squad, user; for the last two ask targets 1 to 32 identifiers. Exceptions are available. excluded_userspriority 0-100, starts_at / ends_atplatform any / ios / android / desktop precise tag. The outdated version returns 400 at PUT, 409 at DELETE. Reread the rule and combine the changes; automatic rewrite can lose operator edits; up to 100 connection rules. Priority of communications It matches the interface of the panel.

Issue of Flow

GET returns rulerelated nodes, profiles and information about the old rules legacy_rulesChange the required fields. rule and pass on full rule For a new record, the version is 0; the older version is rejected from 400. The exclusion state calculates the server. Rule includes regime drain_mode (off, manual, auto), accessibility health_enabledload source node_id, thresholds, minimum duration of exclusion hold_secondsHistory returns up to 50 events in 30 days, requires a separate scope Flow and an affordable ConnectionUnits capability. Assignment of settings.

Mistakes

The error body has a error field. Receiving an error should not be considered a successful save.

Verification

Start by reading the directory and settings of the test user. Perform a preview, then PATCH of one field and re-read. Update your subscription in the supported application. Separately check that the token does not have access to another connection or Flow.

Rollback

Return the saved fields via PATCH or delete the personal settings via DELETE. For the ad rule or Flow, get the current version first and then save the previous values. Token recall via DELETE /api/v1/internal-tokens/TOKEN_ID prohibits subsequent requests, but does not cancel the changes already saved. Examples use variables and conditional identifiers; requests to the workbar were not performed as part of the reconciliation.