DODO APP / TECHNICAL DOCUMENTATION

Connect your service to DoDo.

Set up subscription delivery, add your service name and helpful links for users. All you need is a compatible HTTPS response — you do not need to share access to your panel's API.

HTTPS subscriptions Remnawave or your own panel Status by platform

Android 2.2.0 is available as an APK, build 2107 dated November 10. Download APK. This release is distributed outside Google Play; the store update will be announced separately. If you installed DoDo from Google Play, update through the store: signatures may differ. Do not delete the app or its data to install the APK.

iOS 2.2.0 was published on the App Store on November 6, supports iOS 15 and later and uses Xray 26.10.31. Android features below refer to APK 2.2.0 (2107). macOS and Windows are covered separately.

Features by platform

01 / GETTING STARTED

Quick start

Implemented
  1. Give the user an HTTPS subscription link: a URI list, Base64 or supported Xray JSON.
  2. If your panel selects the format by User-Agent, configure full Xray JSON delivery for DoDoApp on iOS and the DoDoApp/ prefix on Android.
  3. Add the service name, refresh interval and other subscription details to the HTTP response headers.
  4. Users add the link via “+”: from the clipboard, manually or by QR code. For a bot or website, use the dodoapp://import described below.
  5. Test adding and refreshing the subscription, and connecting to servers.
GET /sub/demo-token HTTP/1.1
Host: example.invalid
User-Agent: DoDoApp
Accept: */*

Minimal response from your server

Return HTTP 200 at the HTTPS subscription link, with subscription details in the response headers and the configuration in the body. For Xray JSON, set Content-Type: application/json and send JSON instead of a URI list.

HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
profile-title: Demo Provider
profile-update-interval: 1
support-url: https://example.invalid/support

vless://00000000-0000-4000-8000-000000000001@example.invalid:443?security=tls&type=ws&path=%2Fdemo#Demo

After adding the link, users will see a subscription card and a server list. The name and support button come from your response. Replace the example.invalid address and keys in the examples with your own; keep working subscription links secret.

DoDo is a connection app. Your service provides the servers and access. You can use Remnawave or your own panel that delivers subscriptions in one of the formats below.

DODO PARTNERS / EARLY ACCESS

Free provider registration

Full production launch coming soon

Provider registration is open in early access. Sign in with Google, create your service dashboard and verify the exact key delivery domain. There are no plans, payments or free-access expiry dates; technical limits apply to prevent spam and overload.

1. Create your service

After signing in with Google, enter a name and an optional public HTTPS support link. The dashboard belongs to the signed-in account; no Firebase UID, panel password or user key is needed. Clicking again does not create a second dashboard. You can prepare branding and drafts; public display requires DNS verification and DoDo approval.

2. Verify your domain

Under “Domains and access”, enter the exact host, such as sub.example.com, without a protocol, path or port. Click “Get TXT record”, copy the name and unique value into your DNS panel, then click “Check DNS”. Example record structure:

Тип: TXT
Имя: _dodo-verify.sub.example.com
Значение: dodo-verification=v1:КОД_ИЗ_ВАШЕГО_КАБИНЕТА

Do not copy this example in place of your actual code. Your DNS panel may append the domain automatically — check the record's final fully qualified name. If the code has expired, get a new one. The dashboard shows the verification expiry and latest DNS check result separately.

Verification is valid for 30 days. The dashboard displays a warning seven days before expiry. Click “Renew DNS”, publish a new TXT record and complete the check before expiry. There is no automatic background renewal. If verification has expired or the domain has been revoked, you must verify it again. A signing key is not required for public branding and stories; in the optional advanced protocol, previous keys are not automatically re-enabled after trust is lost.

Verification applies only to the specified domain, not all subdomains or other services on a shared CDN. For a shared domain with different secret paths, use your own domain or a dedicated subdomain. DoDo's manual decision history is stored separately: manual approval is not DNS verification.

3. Wait for DoDo approval and add one header

Google verifies the owner's account; DNS verifies control of the exact domain. Service approval by the DoDo team remains a separate requirement. After these steps, take the provider ID from your dashboard and add it to an actual successful HTTPS subscription response on that same exact host:

x-dodo-provider-id: UUID_ПРОВАЙДЕРА_ИЗ_КАБИНЕТА_DODO

This is a real HTTP response header, not a body comment or JSON field. An error, HTML placeholder page, redirect or response from another host will not work. Do not confuse this UUID with the short providerid for the fallback address.

4. Set up public branding and stories

Configure your service's branding and posts in your dashboard. For public branding and stories, you do not need to install a module, create a signer or a key pair, share your panel's API token, or change Xray, VPN nodes or the subscription body. Publishing stories still requires valid DNS verification and DoDo approval.

Public content is isolated in /api/provider-content/v1. It does not verify an active or paid subscription, create a private audience or enable targeted push notifications. Do not publish material intended only for paying subscribers here. Content errors must not block import, subscription refresh or VPN.

Advanced: signed verification of a specific subscriber

This is an optional, separate protocol, not a requirement for public branding and stories. Its strict checks remain in place; a public ID does not replace a server signature.

Google verifies the owner's account, DNS verifies domain control, and a signed response from your server verifies a specific subscriber's right to receive your service's content. These are different checks. A matching profile-title, support-url or public ID alone does not grant access to another service's content or reports.

  1. Create an Ed25519 signing key in your infrastructure. Register only the public JWK in the dashboard after DNS verification. The private key stays on your server.
  2. Add x-dodo-provider-id from your dashboard to a successful HTTPS key delivery response. The optional x-dodo-connector-id is not required for the standard flow.
  3. When the app sends a request with x-dodo-subscriber-challenge, check the key, subscriber entitlement and your device policy, then create a signed x-dodo-subscriber-token.
  4. After integration testing and DoDo approval, the content session grants access only to this service. Users do not need a Google account in the app itself.
Integration pilot headers
HeaderDirectionPurpose
x-dodo-provider-idProvider server → DoDoPermanent dashboard UUID. Service discovery only, not authorization.
x-dodo-subscriber-challengeApp → provider serverOne-time verification request tied to a specific installation.
x-dodo-subscriber-tokenProvider server → appDynamic signed response to this request. It cannot be replaced with one shared string for everyone.

A separate endpoint and the full Remnawave administrative API are not required: you can add the check to the existing key delivery handler. The same principle applies to custom panels. No changes to Xray or VPN nodes are needed. Token responses must bypass shared CDN caches and use Cache-Control: private, no-store; do not write keys, HWID, challenges or tokens to public logs.

A content verification error must not disrupt normal key delivery, import or VPN. Multiple services on one device are linked independently; deleting a key or revoking permission stops the associated content from being shown. This protocol remains in the /api/provider-binding/v1 namespace, separate from public content.

These instructions do not mean production has launched. Preparing the dashboard and DNS does not confirm server deployment, a new App Store build or an iPhone test. Display requires a compatible app version. Bulk targeted push notifications are not included in the simple connection method.

DODO PROVIDER CONSOLE

Self-hosted panel

Early access · 0.1.1

Install a standalone dashboard on a Linux server and open it on your own HTTPS domain. Branding, domains and stories are managed through the DoDo API. The main admin panel, other services, shared diagnostics and push-sending keys are not included. Data and published files are stored by DoDo.

  1. Extract the archive, check SHA256SUMS and set the dashboard's exact address in .env.
  2. Start Docker Compose and configure an HTTPS proxy to 127.0.0.1:8795. The container runs without root or access to VPN nodes.
  3. Get a private setup code using the command in the guide. In your panel, click “Connect to DoDo”, then sign in with Google on the DoDo website, select your service and confirm the one-time code.
  4. To work with data, sign in separately as an owner or editor. Each installation receives its own revocable access; the installation itself does not replace a person's permissions.
  5. Verify the key delivery domain with DNS TXT and add x-dodo-provider-id to the successful response. The dashboard domain and key delivery domain may differ.

No Remnawave module, VPN panel password or administrative API token is needed. Manage installations and revoke access in the main DoDo dashboard, in your provider's section. Do not share the private setup code with support or in screenshots.

Statistics for your service only. Panel 0.1.1 shows devices with reports, models, OS and DoDo versions, the latest submission date and history for 1/7/30 days. It uses the provider ID and exact domain from a successful key delivery response; the server checks for valid DNS verification. A compatible updated iOS client is required; older apps do not send this data before its release. Providers are not given old reports based on a matching name or support link. This is not an online counter or a database of paying subscribers. Targeted push notifications and payments are not yet connected.

If the API is unavailable, the dashboard will offer a retry; there is no infinite retry queue. After a write timeout, refresh the section and check the result first. Keys and VPN work independently of this dashboard's availability.

02 / COMPATIBILITY

Protocols

The formats below apply to iOS 2.2.0. When setting up your service, test import and connection with the transports and parameters your panel delivers. Android-specific details follow the table.

ProtocolInput formatSupport and details
VLESSvless://, Xray JSONImplemented Including compatible TLS / Reality profiles.
VMessvmess:// with Base64 JSON, Xray JSONImplemented Transport and security parameters are validated.
Trojantrojan://, Xray JSONImplemented TLS is used by default for URIs.
Shadowsocksss://, Xray JSONImplemented Common SIP002 / Base64 variants. Cipher support depends on the core; external plugins in URIs are not supported.
Hysteria2hy2://, hysteria2://, compatible Xray JSONImplemented Version 2; Salamander and hopping parameters are available in supported formats.
SOCKS5socks://, socks5://, Xray JSONImplemented With or without a username/password. This is a SOCKS connection, not additional protection by itself.
Standard WireGuardwg://, wireguard://Limited A URI with parameters or a Base64 wg-quick profile inside a URI. Files with arbitrary peer sets and AmneziaWG parameters are not supported.
AmneziaWG, TUIC, SSR, Hysteria v1Their own schemes and extensionsNot supported on iOS An AmneziaWG profile is not converted to standard WireGuard.

Full Xray JSON may include auxiliary HTTP, SOCKS and WireGuard outbounds. For standalone imports, use only the URIs listed in the table.

Android APK 2.2.0 details. AmneziaWG remains available on Android and is not available on iOS. Hysteria2 import and startup are supported; test connections with your server's parameters. Full JSON is accepted if the app recognizes the main proxy protocol and all related outbounds.

03 / TRANSPORTS

Transports and TLS

Depends on the profile
URI parameterSupported valuesNote
type / networktcp, raw, ws, websocket, grpc, xhttp, splithttp, httpupgrade, kcp, mkcpwebsocket is read as WS, splithttp as XHTTP. Send complex transport settings as full JSON.
securitynone, tls, realityThe combination must be supported by the protocol and core themselves.
TLS / Realitysni / peer, fp / fingerprint, alpn; for Reality — pbk, sid, spxUse values matching the server settings. The app will pass them to Xray.
WS / gRPC / XHTTPhost, path; gRPC serviceName, authority; XHTTP mode, JSON object extraFull JSON is preferred for complex nested parameters.
Certificate verificationpcs / pinnedPeerCertSha256, vcn / verifyPeerCertByNameAn invalid pin, unsupported ECH requirement or certificate verification bypass causes the URI import to be rejected, rather than weakening TLS verification.

Hysteria2 uses QUIC without type=quic. Send it via hy2:// or hysteria2://. URI transport values quic, h2 and http are not supported on iOS.

04 / SUBSCRIPTION RESPONSE

Formats and profile preservation

Implemented
  • Plain-text URI list: individual servers, usually one per line.
  • Base64: an encoded list or supported JSON container. Base64 is not encryption.
  • Full Xray JSON: one logical profile with DNS, rules, balancers and outbound dependencies.
  • Array of JSON profiles: standalone configurations appear as separate choices.
  • Collection of independent outbounds: shown as separate servers, without adding a balancer.

A full configuration is saved as one profile, not replaced with a link to the first outbound. DoDo preserves compatible rules, tags, DNS, observatory / burstObservatory, policy / stats and outbound relationships. Profile capabilities depend on the Xray version in use.

Configuration via JSON TLS fragmentation, including freedom.settings.fragment, can be supplied in a compatible full profile. The app has no dedicated fragmentation editor. Service inbounds, local ports and startup parameters are adapted for iOS.

vless://00000000-0000-4000-8000-000000000001@example.invalid:443?type=ws&security=tls&path=%2Fdemo#Demo
trojan://demo-not-a-real-password@example.invalid:443?security=tls#Demo
hy2://demo-not-a-real-password@example.invalid:443?sni=example.invalid#Demo

A corrupt or unsupported profile is rejected in full. If an update fails, previous servers remain. Matching servers keep their IDs, order, pinned status, selected server and latest ping values.

Temporary compatibility with Happ JSON delivery

Temporary compatibility DoDo first sends a normal request. If the server returns usable full JSON, no further requests are made. Otherwise, the app may retry the same URL with User-Agent: Happ/DoDoApp-compat and X-DoDo-Client, which identifies the actual DoDo client. Responses are not merged into a single list.

For full JSON delivery, configure a DoDo User-Agent rule or provide an explicit link with /json. The app does not append this path to arbitrary links. If the compatibility request fails, a usable primary response is kept; an existing full profile is not replaced with an incomplete URI list.

Not supported happ://crypto…, happ://crypt…, proprietary encrypted Happ formats and opening Happ deeplinks. DoDo's own crypt1 and AGE1 addressed to DoDo are available in iOS 2.2.0 and Android APK 2.2.0. DoDo cannot decrypt AGE files encrypted only for Happ or another recipient.

Download limits in iOS 2.2.0: up to 8,000,000 bytes per response, 12,000,000 bytes total per operation and 2,000,000 bytes per individual JSON profile. AGE1 has a separate 2 MiB limit for the encrypted body. In Android 2.2.0, response and operation limits are 2 / 4 MiB respectively. The overall time limit is 25 seconds, with a limited number of attempts. TLS verification is not disabled on error. A partially downloaded response with a network error is not imported.

04.1 / PROTECTED LINKS

DoDo crypt1: deliver subscriptions without exposing the URL

Implemented

Available in iOS 2.2.0 from the App Store and Android APK 2.2.0 (2107). On Android, add protected links from the clipboard or manually. On some HUAWEI devices, crypt1 QR codes may not yet be recognized; a scanning fix is in progress. Windows support is planned. The port to the new Mac version has not yet been published on the Mac App Store.

crypt1 encrypts an existing user's HTTPS link and produces a link in the form dodoapp://crypt1/<JWE>. When opened, DoDo asks for confirmation before contacting the subscription server. It can still contain your normal source: a URI list, Base64, one full Xray JSON or an array of profiles. DNS, routing and balancers are read by the same parser.

For standard crypt1 with response: "auto", you do not need to change your panel or subscription content. The link is encrypted locally — no encryption API, DoDo registration, premium access or mandatory providerid. Remnawave and custom panels work equally well. This is DoDo's own format, not a way to open proprietary Happ or INCY crypto links.

The generator runs in your browser using WebCrypto. The entered URL is not sent to the server; cookies and browser storage are not used for links. For automated delivery, use Node.js 24+ and the same SDK from the archive. The public key manifest contains only public RSA keys and AGE recipients.

Quick start without panel changes

  1. Take the existing HTTPS subscription address for a specific user.
  2. Open the generator, paste the address and leave “Automatic” selected. A name is optional.
  3. Send the resulting crypt1 link to that user in a private message or bot button. Do not give one personal subscription to all subscribers.
  4. In iOS 2.2.0, open the link or add it via “+” from the clipboard, manually or by QR code. In Android APK 2.2.0, use the clipboard or manual entry; the known HUAWEI QR limitation is described above. Confirm the addition and test refresh and VPN.

When sharing a QR code or copying, DoDo uses the original crypt1 link rather than the decrypted URL. A very long link may not fit in a QR code — send it as text instead. Encrypting the same URL again produces a different string, but the app updates the existing subscription card.

Generation in a Telegram bot or on your server

Extract the tools archive. It contains cli/, generator/, keys/, instructions and a specification. The SDK requires no npm packages and does not fetch keys over the network. Store each user's URL securely in your service.

# Запускайте из папки распакованного архива; требуется Node.js 24+.
# subscription-url.txt содержит HTTPS-ссылку одного пользователя.
node cli/dodo-crypt1.mjs --name "Demo Provider" < subscription-url.txt

# Для полного payload из JSON-файла:
node cli/dodo-crypt1.mjs --input-json < payload.json

The CLI reads the source URL from stdin and outputs only the protected link. Do not put a real token in command arguments, terminal history or bot logs. The CLI output is also a secret link — share it only with the subscription owner.

import { readFile } from 'node:fs/promises';
import { createCrypt1Link } from './generator/crypt1.mjs';

const publicManifest = JSON.parse(
  await readFile(new URL('./keys/public-keys.json', import.meta.url), 'utf8')
);

const protectedLink = await createCrypt1Link({
  v: 1,
  type: 'subscription-url',
  url: 'https://primary.example/sub/demo-token?format=json',
  response: 'auto',
  name: 'Demo Provider',
}, publicManifest);

// Передайте protectedLink пользователю; не записывайте её в общий лог.

createCrypt1Link(payload, publicManifest) returns Promise<string>. The first argument describes the subscription; the second is the published manifest's contents. The SDK uses its activeKid; providers do not need the private key. Update your local copy of the public manifest when DoDo rotates keys, not for every user request.

Payload fields for createCrypt1Link
FieldRequiredWhat to provide
vYesThe number 1.
typeYesThe string subscription-url.
urlYesThe user's full HTTPS address, up to 4096 UTF-8 bytes. No username/password, fragment, spaces, IP literals or local addresses.
responseYesauto for a standard or AGE1 response; age1-required only for an AGE1 source that is already configured.
nameNoA non-empty name of up to 120 UTF-8 bytes after trimming whitespace. Control characters are forbidden. This is a name for the confirmation screen, not proof of the provider's identity.

Do not add custom fields to the payload. The URL is preserved without decoding again: %2F, %252F, the + sign, path and query must remain as issued by your panel. primary.example, backup.example and demo-token are examples only, not working addresses or keys.

crypt1 format for a custom implementation

If you use the ready-made SDK, it creates the header and random values itself. Other implementations require JWE Compact Serialization: five segments protected.encrypted_key.iv.ciphertext.tag, canonical base64url without =, spaces or extra encoding layers.

{"alg":"RSA-OAEP-256","enc":"A256GCM","typ":"dodo-subscription+jwe","kid":"dodo-crypt1-20261102"}

The kid value here is an example of the current key. In your implementation, select it from activeKid in the public manifest rather than permanently hard-coding it.

{"v":1,"type":"subscription-url","url":"https://primary.example/sub/demo-token","response":"auto","name":"Demo Provider"}
Exact crypt1 v1 parameters
ParameterValue
RSA3072 bits, exponent 65537; RSA-OAEP-256 with SHA-256 and MGF1 SHA-256, empty OAEP label.
AES-GCMA fresh random 32-byte CEK, 12-byte IV, 16-byte tag. AAD is the ASCII representation of the first encoded JWE segment.
HeaderOnly the required alg, enc, typ, kid. kid must be known to the app.
LimitsEntire crypt1 link: 16,384 UTF-8 bytes; JSON payload: 8192 bytes; source URL: 4096 bytes; name: 120 bytes.
Not allowedDuplicate JSON names, unknown fields/algorithms, zip, crit, jku, embedded keys and fetching keys from header URLs.

AGE1: server response encryption is a separate setup

crypt1 protects the link; AGE1 protects the HTTP response body at that link. AGE1 can also be used with a normal HTTPS address. The server must separately encrypt usable JSON, a URI list or Base64 for DoDo's published X25519 recipient.

age1-required does not enable server-side encryption. This parameter requires the app to reject unencrypted responses, including from a fallback address. Set up and test AGE1 on the server first, then issue links with this policy. With auto, a standard supported response or AGE1 is accepted; recognized but corrupt AGE is not reparsed as plain text.

The app does not send a header that enables AGE on your server: the request keeps the usual Accept: */*, User-Agent and device data. The response value from crypt1 is not a server command either. A reliable approach is a separate HTTPS address that always returns AGE1, while other clients keep the existing link. If you use User-Agent rules, note that DoDoApp alone does not indicate the user's build number.

The example below requires the official age CLI with X25519 and jq. Save the public manifest to keys/public-keys.json; providers receive no DoDo private keys. subscription.json must contain a valid profile for this specific user.

# В примере используется первый опубликованный AGE-получатель.
jq -er '.ageRecipients[0].recipient' keys/public-keys.json > age-recipients.txt

# Бинарное тело HTTP-ответа:
age --encrypt --recipients-file age-recipients.txt \
  --output subscription.json.age subscription.json

# Или ASCII armor вместо бинарного тела:
age --encrypt --armor --recipients-file age-recipients.txt \
  --output subscription.json.age.armor subscription.json

Return the created file's contents directly as the response body: binary age v1 usually with Content-Type: application/octet-stream, ASCII armor with text/plain. DoDo recognizes the format from the start of the body, not just Content-Type. Do not add a JSON wrapper, another Base64 layer, BOM or HTML. Password-based scrypt, SSH keys, plugins and AGE files for other recipients are not supported.

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Cache-Control: private, no-store
profile-title: Demo Provider
profile-update-interval: 2
subscription-userinfo: upload=0; download=0; total=107374182400; expire=1893456000
fallback-url: https://backup.example/sub/demo-token
providerid: demo-vpn

Name, expiry, traffic, refresh interval, support and fallback-url remain real HTTP headers outside the AGE body. Their usual precedence and validation rules still apply. providerid in the example is optional for crypt1/AGE; if saved with a fallback, the fallback must return the same ID. Fallback follows the general fallback rules, independently of link encryption. With age1-required, both the primary and fallback addresses must return AGE1.

Before issuing links to users

  1. Make sure iOS 2.2.0 or later is installed. Add one test subscription and verify that the request starts only after confirmation.
  2. Compare the profile count with the source JSON; test a full profile with a balancer, refresh, server selection and connection.
  3. For AGE, test the primary and fallback addresses. A wrong recipient, corrupt body or plaintext response under age1-required must result in an error, not a partial server import.
  4. Test copying/QR, re-adding and refreshing: the original crypt1 link, subscription order and settings must be preserved. Do not publish working tokens in screenshots.
If a link or response is rejected
CauseWhat to check
Unknown key or formatThe app version and build number, current public manifest and DoDo's own dodoapp://crypt1/ scheme. Happ keys and crypto links will not work.
Could not open the protected subscriptionCheck the entire link's integrity, five JWE segments, supported fields and absence of repeated URL/Base64 encoding. Previous servers are not deleted.
AGE response requiredThe server returned plaintext under age1-required. Change server delivery rather than disabling the app's checks.
Could not decrypt AGECheck the DoDo recipient, binary format or ASCII armor, absence of wrappers and complete file delivery. Do not try to extract individual URIs from a corrupt body.
HTTP, TLS, HWID or subscription expiryNormal server restrictions still apply. crypt1/AGE do not bypass access denial, device limits or certificate errors.

A protected link still grants access to the subscription. This is not DRM or proof of provider identity. The decryption key is embedded in the app and may be extracted through analysis. Store source and crypt1 links securely, keep them out of shared logs, and use HTTPS, authorization and your panel's limits. Do not put administrative API tokens or server passwords in the payload.

05 / METADATA

HTTP response headers

Implemented

Send these fields in the HTTP 200 response headers at the subscription link. Header names are case-insensitive. For ordinary metadata, DoDo first reads HTTP headers, then supported fields in body comments, decoded Base64 and JSON metadata. The first valid value is used. x-dodo-provider-id is an exception: only a real successful HTTPS response from the same exact host is accepted.

Subscription headers; feature availability depends on the app version
HeaderWhat to sendWhat users seeDetails
profile-titleA plain-text name or base64:… UTF-8.The subscription / service card name.If absent, subscription-name is used, followed by filename / filename* in Content-Disposition.
x-dodo-provider-idThe provider UUID from your own dashboard.Linking to public branding and stories in a compatible app version; this does not claim the feature is available in published versions.Requires the exact DNS-verified host and DoDo approval. Does not verify payment, grant access to a private audience or enable push. No signing module is needed.
x-dodo-provider-logo-urlA public HTTPS image URL.The service logo in the top section.Do not include a password or secret subscription link in the image URL. The app icon on the device does not change.
support-urlA support address, such as an HTTPS Telegram link.A “Support” button on the card.Without a value, the button is not created automatically.
profile-web-page-urlA public link to a dashboard, bot or subscription page.A website / “Buy / Renew” button.Alternative name: homepage. Payment takes place on your page, not in DoDo.
subscription-userinfoupload=…; download=…; total=…; expire=….Expiry, status and used / available traffic.Send volumes in bytes and expire as a Unix timestamp in seconds. HTTP 403 alone does not set an expiry date.
profile-update-intervalAn integer number of hours from 1 to 168. Not minutes or seconds.Automatic refresh when due and when the app receives execution time.Default: 1 hour. The operating system determines background execution time.
routingStatic JSON / Base64 / a DoDo routing link.Direct / Proxy / Block rules for this subscription.Use autorouting to update rules over the network. New rules apply on the next connection.
autoroutingAn HTTPS URL for a separate rules resource.Up-to-date rules for the subscription.The format, limits and check intervals are described under “Routing”.
announceText or supported base64:….An announcement block inside the card.The announcement is not sent as a push notification or published as a story.

If the subscription is a static text file

Supported fields may be provided as comment lines at the start of the body. For example:

#profile-title: Demo Provider
#profile-update-interval: 2
#support-url: https://example.invalid/support
#announce: Demo announcement
vless://00000000-0000-4000-8000-000000000001@example.invalid:443?security=tls#Demo

HTTP headers take precedence over comments. Provider identity fields, including x-dodo-provider-id, are accepted only from a successful HTTPS response on the same exact host, not body comments. The ID alone does not verify access to private content; public branding and stories are not a payment check.

profile-title: Demo Provider
profile-update-interval: 2
x-dodo-provider-logo-url: https://example.invalid/logo.png
support-url: https://example.invalid/support
profile-web-page-url: https://example.invalid/account
subscription-userinfo: upload=0; download=0; total=107374182400; expire=1893456000
autorouting: https://example.invalid/routing.json

How automatic refresh works. DoDo checks whether a refresh is due while running and when the user returns to the app. iOS schedules background execution, so refresh may occur later than the specified interval. If a network error occurs, the saved subscription remains on the device.

Headers update-always, profile-description, premium-url, fragmentation-*, noises-*, server-address-resolve-* are not supported, nor is provider control of Lite Mode, theme or button style. Send DNS and complex transport parameters in compatible full Xray JSON. Arbitrary external geofiles are not downloaded from headers.

fallback-url and its associated providerid are described under “Fallback subscription”. They are accepted only as real HTTP response headers, not body comments or JSON fields.

05.1 / FALLBACK ADDRESS

Fallback subscription: fallback-url

iOS and Android 2.2.0

If the primary subscription address is temporarily unavailable, DoDo can download an update from a previously saved fallback address. This works with server URI lists, Base64 and supported JSON, including full Xray profiles. A crypto link is not required.

Availability. Fallback addresses are supported in published iOS 2.2.0 and Android APK 2.2.0 (2107). The headers work with normal HTTPS links and JSON, independently of crypt1. The published Mac version does not yet have this mechanism.

Fallback downloads require no DoDo registration or premium access. Use Remnawave or your own panel: the important part is that the server returns the correct HTTP headers and the right user's subscription.

Fallback subscription headers
HeaderValueRequirements
fallback-urlThe full HTTPS fallback subscription link for a specific user.Not just a domain. The provider sets the path, token and query; the app does not copy them itself. Accepted from a usable successful response from the primary HTTPS source on the same origin.
provideridAn optional permanent ID for your VPN service, such as demo-vpn.Providers choose the ID themselves. It is not a Happ license, DoDo dashboard ID, HWID or payment check. If the primary response sends it with a fallback, the fallback must return the exact same value.

The header name is case-insensitive. The providerid value is case-sensitive: Demo-VPN and demo-vpn differ. It allows 1–128 ASCII characters: a letter or digit first, then letters, digits, periods, hyphens, underscores and colons. Do not use a secret API token. If your service already sends its own ID, you do not need to change it for DoDo.

If you already return fallback-url and providerid for Happ or INCY users, DoDo can read them in the format described here. Users only need a normal HTTPS subscription link; no separate DoDo ID is required. This does not add support for happ://crypto… or commands from other apps.

Do not confuse providerid with x-dodo-provider-id in the provider linking section. Fallback downloads do not grant access to stories, notifications or private data; those features are configured separately.

Primary and fallback response example

The primary subscription https://primary.example/sub/demo-token returns the user's configuration in the body and these headers:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
providerid: demo-vpn
fallback-url: https://backup.example/sub/demo-token

The fallback address must deliver the same user's subscription. If the primary response included providerid, add it to the fallback response too:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
providerid: demo-vpn

Fallback also works without providerid — using the exact HTTPS address received from the primary source. If an ID was saved and the fallback returns a different ID or none at all, the update is rejected and previous servers remain. A matching ID alone does not prove service ownership or subscriber membership.

How to configure Remnawave

  1. Open the subscription response headers section: Response Headers or Additional Response Headers. The section name depends on the panel version.
  2. Add fallback-url with a personal fallback URL and, if needed, a permanent providerid.
  3. In versions supporting header templates, use {{SHORT_UUID}} so the panel inserts the current subscription's identifier. Set a domain and path where the fallback actually serves that subscription.
  4. Configure headers for all required formats, including JSON, and relevant User-Agents. You can use Response Rules for individual clients without replacing other format rules.
providerid: demo-vpn
fallback-url: https://backup.example/sub/{{SHORT_UUID}}

Domains primary.example, backup.example and demo-token are examples, not working addresses or keys. Replace them with your own. Do not assign one personal link to all subscribers. The server response must already contain the specific user's full link, without an unexpanded {{SHORT_UUID}}.

Prepare the fallback service itself

  • Configure DNS, a valid HTTPS certificate and configuration delivery at the fallback address. A DNS record alone does not create a fallback service.
  • Return the configuration, not a website home page. Preserve subscription expiry, traffic, rules and device limits; DoDo uses the same HWID.
  • A backup domain on the same server may help if the name is blocked, but not if the server or its IP is unavailable. That case requires separate, reachable fallback infrastructure.

When the app uses fallback

After a network failure, timeout, HTTP 408 or 5xx error from the primary source, the app may contact the saved fallback within the overall time and attempt limits. Fallback does not bypass TLS errors, authorization denials, HWID limits, explicit disabling or expiry, HTTP 404/410 or 429. One fallback address is used, with no mirror chains or path guessing.

A successful download updates the same card: the original link, IDs and subscription order are preserved. If neither address responds or the fallback returns an unusable profile, the app does not delete previous servers or subscription settings.

The fallback address must be obtained first. DoDo remembers fallback-url after successfully adding or refreshing the primary subscription. If the primary address is already unavailable when first adding it, the app cannot discover a fallback from an unavailable response. providerid alone does not look up an address.

To test, first refresh the subscription successfully in a supporting DoDo build. Then check fallback availability for the same user and simulate a controlled failure of only the primary address. Turning off all internet access does not test fallback: the backup needs a network too. Do not publish real token-bearing links in screenshots or logs.

06 / DEVICE

HWID and device limits

Implemented

When downloading a subscription, DoDo sends your server the stored installation identifier, model and OS version. HWID is generated by the app; it is not the phone's serial number or IDFA. Use it to track devices alongside server-side access checks.

User-Agent: DoDoApp
Accept: */*
x-hwid: 00000000-0000-4000-8000-000000000001
x-device-os: iOS
x-ver-os: 18.5.0
x-device-model: iPhone 14 Pro

This is an example iOS request. Android sends the same technical header names with x-device-os: Android, its own OS version and model. Its User-Agent takes the form DoDoApp/2.2.0+2107 (Android 15; Demo Model); do not restrict the server rule to exact equality with DoDoApp.

  • The identifier is stored on the device, including in Keychain on iOS. Retrying a download after a denial does not create a new HWID.
  • Resetting app settings does not change the HWID or reset the provider's device limit.
  • HWID is sent in a header and is not appended to the subscription address.
  • On a redirect to another origin, iOS removes sensitive headers, while Android rejects the redirect entirely. HTTPS-to-HTTP redirects are forbidden.
  • The provider's server determines the number of allowed devices and subscription access.
Provider responseBehavior
x-hwid-max-devices-reached: trueDevice limit reached error.
x-hwid-limit: trueCompatible legacy indicator of the same restriction.
x-hwid-not-supported: true / explicit HWID_REQUIREDA clear download denial; the identifier is not replaced with a new one.

x-hwid and x-dodo-provider-id do not replace subscriber authorization. For private posts, the server must separately check that the subscription belongs to this user.

08 / RULES

Static and remotely updated routing

Supported fields below

Set which domains and IPs go directly (Direct), through the proxy (Proxy) or are blocked (Block). DoDo rules profiles have their own format; full Xray JSON cannot be supplied in these fields.

{
  "Name": "Demo rules",
  "GlobalProxy": true,
  "DomainStrategy": "IPIfNonMatch",
  "DirectSites": ["domain:example.invalid"],
  "DirectIp": [],
  "ProxySites": ["full:proxy.example.invalid"],
  "ProxyIp": [],
  "BlockSites": ["geosite:category-ads-all"],
  "BlockIp": []
}

Local routing link

Save the JSON as UTF-8, encode it in Base64 or Base64URL and put the result after /add/ or /onadd/. Base64URL without trailing = is more convenient for links. Standard Base64 can be percent-encoded once.

dodo://routing/add/{BASE64_UTF8_JSON}
dodo://routing/onadd/{BASE64_UTF8_JSON}
dodo://routing/off

Both commands save and enable the profile. off disables rules without deleting them. Do not add a username, password, port, query or fragment to the link. Rules apply on the next connection; the current VPN is not automatically reconnected.

autorouting: separate HTTPS JSON

Supply a public HTTPS rules file link in autorouting, such as https://example.invalid/routing.json. Replace the address with your domain: .invalid and local addresses are not accepted.

  • The response must be HTTP 200 with a UTF-8 JSON object. Base64, routing links and full Xray JSON are not accepted here.
  • Only fields from the example above and a string LastUpdated are allowed; their camelCase aliases are supported. Unknown fields and conflicting aliases are rejected.
  • Lists are arrays of strings: domains, domain:, full:, validated regexp:, geosite:; for IPs — IP/CIDR and geoip:. Categories are checked against the available geofiles.
  • For the remote format, DomainStrategy: AsIs, IPIfNonMatch or IPOnDemand. GlobalProxy is a JSON boolean or the string "true" / "false".
  • Limits: 256 KiB per file, up to 2048 entries total and up to 512 bytes per entry. iOS allows up to 12 seconds per request.
  • Use HTTPS on the standard port, without a username, password or fragment. Redirects are allowed only within the same origin and in limited numbers. HWID, cookies and subscription API tokens are not sent in this request.
  • Rules are stored separately for each subscription. A network error or invalid JSON leaves the last working version in place.
  • On iOS, a successful source is checked no more than once per hour; after an error, retries are delayed. Background execution depends on the system. New rules are used on the next connection.

dodo://autorouting/add/… and dodo://autorouting/onadd/… with an HTTPS source are also recognized inside the subscription body. Do not use them as app-opening links from a bot or browser.

Additional settings. DNS / FakeDNS, external Geoipurl / Geositeurl and routeOrder are not supported in this format. Use compatible full Xray JSON for complex routing and balancers.

In Android 2.2.0, the autorouting check interval is 24 hours and the request timeout is 8 seconds. Rules are also stored separately per subscription; the request contains no HWID, cookies or API tokens. The autorouting interval is unrelated to profile-update-interval, which controls subscription refresh itself.

09 / GEOIP AND GEOSITE

Geodata is bundled with the app

Implemented

iOS 2.2.0 and Android 2.2.0 include geoip.dat and geosite.dat. These files do not need to be downloaded with the subscription before the first connection.

Update source: Loyalsoldier/v2ray-rules-dat. SHA-256, file format and required categories are checked before installation. If validation fails, the last working pair remains.

On iOS, file versions and manual checks are available under “Settings → Advanced → Geodata”. The app also checks for updates automatically when it receives execution time and the source is reachable.

Use geosite: / geoip: categories included in the Loyalsoldier dataset. Categories from other datasets may be absent. Downloading arbitrary geofiles from provider links is not supported.

On Android, a running VPN keeps using the selected file version until disconnected. Updated files apply on the next connection; rollback to a working version is available.

10 / SERVER CHECK

Latency checks

On iOS, choose the mode under “Settings → Advanced → Ping”. TCP is the default. You can set a custom HTTPS test URL and a timeout from 1 to 10 seconds.

ModeWhat is checkedHow to read the number
TCPEstablishing a connection to the server. Hysteria uses a separate HTTP check through the profile because the protocol runs over UDP.The raw measured time, without division by 3.3. An open TCP port alone does not confirm authorization or internet access.
DoDo PingHTTP GET through a supported Xray server profile; some protocols use their own check.An estimated value: the measured result divided by 3.3.
HTTP GET / HTTP HEADA request using the corresponding method through the profile to the test HTTPS URL.The measured request time, without division by 3.3. Data transfer speed is not measured.
ICMPAn ICMP request to the server.Response time. A server may block ICMP while still serving VPN connections normally.

Raw measurements are saved without recalculation. When the check method changes, iOS runs the appropriate measurement and does not present another method's result as new. When a key is updated, matching servers retain their latest values. N/A means the check failed or is unavailable for this profile; an ellipsis means there is no result yet for the selected method.

Concurrent checks are limited. Measurements do not reconnect the current VPN. If the JSON contains a balancer, the check runs through the entire profile, using its server selection rules.

Android APK 2.2.0 (2107) offers the same five modes. Standard TCP shows measured connection time without division, including an unambiguous JSON profile with one TCP server. For Hysteria, balancers and complex or ambiguous profiles, TCP mode performs HTTP GET through the full profile. Auxiliary core startup and local authentication are excluded from the displayed HTTP time but count toward the overall timeout. Only DoDo Ping divides the HTTP GET result by 3.3.

10.1 / NETWORK SETTINGS

DNS, MTU and preferred IP

iOS 2.2.0

Open “Settings → Advanced → Network”. We recommend leaving the defaults for normal connections. Changes apply on the next connection and do not reconnect a running VPN on their own.

Additional iOS settings
ParameterAvailable optionsWhen useful
Tunnel MTUDefault, 1420, 1380, 1280 or an integer from 1280 to 1500 bytes.For investigating loading issues on particular networks. This is packet size, not a speed limit; there is no automatic search for the best MTU.
Preferred IP“As configured”, “Prefer IPv4” or “Prefer IPv6”.To choose the address family of a VPN server with a domain name. This does not disable IPv6 on the phone. For complex profiles, the setting may not apply in order to preserve the provider's rules.
Profile DNSAligning the system tunnel with Xray DNS when the configuration can be safely adapted.To preserve the provider's DNS rules. Ambiguous setups, FakeDNS and system DNS dependencies are not forcibly rewritten; universal conversion of every DNS profile is not claimed.
VPN resourcesA dedicated screen for extension memory, Go heap, connections and file descriptors.For diagnostics. Requires diagnostic logs to be enabled and a recent VPN session; if no data is available, the app says so instead of showing zero values.

Compatible full profiles preserve their own DNS, routes, balancers and transport parameters. IP and MTU choices do not change the saved key. A manual memory limit, No Limit Mode and a separate editor for all Xray parameters have not been added to the app.

Android APK 2.2.0 also offers MTU from 1280 to 1500 bytes and IPv4 / IPv6 preference. Settings apply to a new connection; the saved full profile and provider DNS are not rewritten. The VPN resources screen and DNS behavior may differ from iOS.

IOS / VERSION 2.2.2

Configuration compatibility and server checks

Uploaded to App Store Connect

iOS 2.2.2 (113) was uploaded to App Store Connect on November 12, 2026. The release is still in preparation; App Store availability will be announced separately. The changes below apply only to this iOS build, not to the published Android or macOS versions.

Full JSON profiles

Import keeps a complete profile even when env and version are its only additional fields. Environment variable names retain their case, and core version requirements remain in effect. An array of independent profiles remains a list of choices; a balancer is not split into independent servers.

HTTP checks and Hysteria2

Connections and HTTP GET / HEAD share the same profile preparation: routing rules, DNS, transport settings and the provider's geodata scope. The check sends a request through the selected proxy or balancer without reconnecting the current VPN. The test core applies env variables in isolation and restores the environment when finished. The app's own service variables are protected against replacement.

Geodata preparation for Hysteria2 HTTP checks has been fixed. In TCP mode these UDP servers are still checked through HTTP, while regular TCP shows the measured connection time without division. Only the estimated DoDo Ping divides HTTP GET by 3.3. This is not a speed test or a complete check of TUN or every destination.

DNS and limited FakeDNS

We improved alignment between Xray DNS and the system tunnel, split DoH and local DNS aliases with cycle protection. Compatible, explicitly configured FakeDNS profiles with standard pools are supported; arbitrary mixed DNS schemes are not adapted automatically. A separate HTTP check is unavailable for a FakeDNS profile; this alone does not mean its VPN connection cannot work. Lua scripts are not supported.

FinalMask and fragmentation

Compatible URI parameters fm, fragment and fragmentPackets / fragmentLength / fragmentInterval are supported, along with the HTTP headers fragmentation-enable, fragmentation-type, fragmentation-packets, fragmentation-length, fragmentation-delay and fragmentation-maxsplit. A header mask is enabled only with fragmentation-enable: true and type xray; fragmentation-interval is accepted as an alternative delay header.

Priority is given to a complete JSON profile, then an explicit URI mask, then settings from the successful HTTP response. Two masks are not combined automatically, and complete JSON is not silently repaired. An incompatible active requirement is rejected rather than replaced with another method. Automatic TCP fragmentation is not applied to UDP-only / Hysteria. TLS verification is not weakened.

Interface and local protection

We improved the notification list and the VPN card on the Lock Screen and in Dynamic Island. The main app supports iOS 15 and later; Live Activity requires iOS 16.1 and a compatible device.

  • Local SOCKS protection. The internal connection between the VPN tunnel and Xray on the device uses a separate service username and password for each connection. They are not carried into the next session when switching providers.
  • Provider passwords are preserved. If a full profile already requires authentication on the local SOCKS inbound and contains a usable account, its credentials are used without replacing them with a service password or disabling security requirements.
  • Remote servers are not reconfigured. The protection applies to the app's local inbound, not the provider's SOCKS server. Its address, username and password remain unchanged; no node reconfiguration is required.
  • Clearer failure reasons. The voluntary technical report gains a limited import error summary: stage, reason, up to four latest download attempts, HTTP status, an allowed system network code and time. The summary is up to 1024 bytes; URLs, keys, HTTP headers and response bodies are not sent. Sending still requires user consent.

Partial imports remain strictly rejected: an unsupported profile does not become a successful import of only its usable part, and failed updates preserve previous servers. Compatibility still depends on the profile, transport and core version; TLS checks and download limits are not weakened.

The update is not published yet. Send new parameters after the client has been updated. Compatibility depends on the configuration and core version; test your service with its keys and the user's network. We will announce the release in Updates and on our Telegram channel.

11 / SUPPORT

Logs and voluntary reports

Implemented

On iOS, open “Settings → Advanced → Logs” to enable recording, view live events, pause viewing, copy or clear the log. Review its contents before sharing: technical server addresses may remain in it.

After an error, DoDo may offer to send technical reports to the developer automatically. Sending begins only after the user consents. In settings, users can disable it, withdraw consent and delete submitted data.

  • A report contains the error code and stage, device model, OS version and app version.
  • Technical reports do not include subscription links, HWID, full VPN configurations or traffic content.
  • If there is no network, the report waits in a limited queue on the device.
  • Reports are received by the DoDo developer. Providers do not gain access through subscription headers.

Automatic reports cover key import and VPN errors handled by the app. iOS 2.2.0 also integrates Apple MetricKit: after diagnostic consent, DoDo may send an indication that a main-app crash or hang report was received. This is not a full crash file, a stack trace or guaranteed coverage of all VPN extension failures. Apple may deliver it later, after the next launch.

Diagnostics on iOS and Android
PlatformFeaturesLimitations
iOS 2.2.0Consent to sending, report queue, delivery, consent withdrawal and data deletion. Limited crash / hang indicators from MetricKit.No full stacks; does not cover all system crashes, memory terminations or hangs. Notification permission does not replace diagnostic consent.
Android APK 2.2.0Consent, protected report queue, sending while the app runs, consent withdrawal and data deletion. Download reports help distinguish network, response and import errors.Not all system crashes and hangs appear in reports. There is no continuous sending while the app is closed; keys and configuration bodies are not sent.
ProviderMay receive a log the user chooses to share directly.No access to DoDo's shared diagnostics, other services or traffic content.

Do not confuse device details in subscription requests with diagnostics: your server receives HWID and technical headers, while the DoDo developer receives voluntary reports. Users share local logs separately.

11.1 / STATISTICS

Usage tracking by provider

iOS 2.2.0

DoDo groups the public service name from profile-title and the sanitized support-url contact to track app usage with different providers' keys. An additional providerid is not required for these statistics. Token-bearing links, VPN keys and full configurations are not needed for this tracking.

What statistics include and how to interpret them
DataPurpose and limitations
Service name and supportFor grouping. Matching names do not prove common ownership; personal or secret-looking values may be omitted.
Model, OS, app versionFor reports by iPhone and Android device models, OS versions and DoDo builds. Android APK 2.2.0 also participates in this tracking. macOS and Windows are not yet connected.
Installations and configuration countReports for 1 / 7 / 30 days. This is not an exact number of people, active VPN sessions or an online counter; one installation may use multiple providers.
What is not sentSecret key URLs, VPN passwords, subscription HWID, phone names and browsing history. This tracking does not build a geolocation map from source IPs.

In iOS 2.2.0, statistics are enabled by default for eligible public service groups. A previously saved opt-out is respected. Under “Settings → Privacy Policy”, users can disable sending and request data deletion. This is a separate setting, not consent to technical error reports.

Android APK 2.2.0 also supports statistics by public name and support contact. Previous consent or opt-out choices are preserved; controls are in the privacy policy. Separate statistics tied to a verified provider ID for the provider dashboard are not yet connected on Android.

The app makes no more than two sending attempts per 24 hours, at least 12 hours apart. An unavailable statistics server does not block DoDo launch, key import or VPN operation. Detailed statistics are retained for up to 30 days. Temporary markers for deduplicating reports within a calendar month are retained until that month closes, for no more than 31 days; then the markers and separate monthly key are deleted.

Since November 9, 2026, the server has kept monthly history: each installation is counted once per month, and one installation with keys from multiple services may appear in several provider groups. Closed aggregate reports are retained without automatic deletion. They contain no installation identifiers, IP addresses, keys or full configurations; small groups are hidden. History before this tracking began is not reconstructed. Withdrawing consent deletes individual records and recalculates the open month; a specific installation cannot be isolated from a closed anonymized aggregate.

Report access Reports are currently available to the DoDo owner in a private admin panel. Dashboards with reports for each provider's own service are being prepared separately. A name, support contact or public ID does not grant rights to other services' data, stories or mailings.

12 / AVAILABILITY

Features by platform

Available — usable in the specified version. Limited — read the details in the relevant section. In development — not yet available for general integration.

Availability by platform

The table covers iOS 2.2.0 and Android APK 2.2.0 (2107). The Android update on Google Play will be announced separately. For macOS, version 2.0.8 remains in the store on the shared iOS App Store page. A new native Mac version with Xray 26.10.31 is being prepared separately and is not yet published; its features should not be considered available on the Mac App Store. A Windows version is in preparation.

Features in iOS 2.2.0 and Android APK 2.2.0 (2107)
FeatureiOS 2.2.0Android APK 2.2.0
URI / Base64 / full Xray JSONAvailableAvailable The entire profile is preserved.
DoDo crypt1 and AGE1Available in iOS 2.2.0 Setup and limitations.Available with a QR limitation Use the clipboard or manual entry; crypt1 scanning on some HUAWEI devices needs improvement.
fallback-url backup addressAvailable Saved in advance from a successful response.Available The fallback must be obtained in advance.
Subscription details and refresh intervalAvailableAvailable
Routing / autorouting / geodataLimited See the rules format.Available with limitations Check intervals differ from iOS.
Five ping modes, logs, QR and resetAvailableAvailable with a QR limitation TCP without division; see ping methods and crypt1 QR.
MTU, IPv4 / IPv6 preference, VPN resourcesAvailable In the advanced settings section.MTU and IPv4 / IPv6 available Resource diagnostics differ from iOS.
Usage tracking by providerAvailable Controls in the privacy policy; reports go to the DoDo owner.Available By name and support contact, with consent and deletion settings. Provider ID is not yet sent for the dashboard.
Error reports with user consentAvailable Sending can be disabled and data deleted.Available The same consent and deletion settings.
Provider storiesClosed testing Only on devices enrolled in testing.Not yet available
Subscriber linking, targeted push and server-side AutoIn developmentIn development

Versions differ. New iOS 2.2.0 features do not appear automatically on Android or macOS. Before issuing new formats, make sure the user's client supports them; store links are on the home page.

Additional features

FeatureStatusWhat this means
Import, refresh, subscription details, QRAvailableFor formats described in this reference. The QR scanner requires camera permission.
Full Xray JSON and balancersLimitedThe entire profile is preserved with related outbounds. Accepted formats and limitations are described under “Subscription formats”.
Protected DoDo crypt1 linksAvailable with limitationsiOS 2.2.0 from the App Store and Android APK 2.2.0. Local generator and SDK with no registration or encryption API. On some HUAWEI devices, use the clipboard or manual entry instead of QR for crypt1. Documentation.
Fallback subscription: fallback-urlAvailableiOS 2.2.0 and Android APK 2.2.0. For normal HTTPS links, JSON and crypt1; fallback must be obtained in advance. Not yet available in the published Mac version. Headers and fallback setup.
DoDo “Auto-select” buttonTemporarily hidden on iOSUsers select a profile manually. A balancer inside full JSON keeps working independently of this button.
Live Activity / Dynamic IslandOn compatible devicesVPN indication for iPhone with iOS 16.1+. Requires a supported model, Live Activities permission and the setting enabled in DoDo.
Appearance and resetImplementedLight/dark theme and app settings. A full reset asks for confirmation and removes subscriptions and user settings; save your keys before resetting.
Updated rules and geodataLimitedDownloaded data is validated. If an error occurs, the working version remains; the system schedules background execution.
Provider storiesClosed testingViewing is available only on devices enrolled in testing. General provider onboarding will open later.
Dashboard registration and DNS TXTEarly accessGoogle sign-in, free service creation and exact domain verification. Full production launch coming soon. Start integration.
Public branding and storiesIntegration preparationA dashboard, exact host with DNS TXT, DoDo approval and x-dodo-provider-id in the HTTPS subscription response. No module or signing key. This is not a private audience; a compatible client is required, and publication of a new version is not confirmed here.
Signed subscriber verificationOptional pilotA separate advanced protocol with a server signature. Not required for public content; a public ID does not replace its checks.
Push to your subscribersNot yet availableTargeted campaigns for individual providers are not yet connected.
Server-side Auto through the panel APIIn developmentWill differ from local auto-selection and Xray balancers. Secret API tokens must not be placed in subscriptions or user apps.
Happ crypto / Happ deeplinkNot supportedOnly the JSON response compatibility described above is available.
Lite Mode, Premium API and forced appearanceNot supportedProviders cannot enable Lite Mode or change the app's theme and button style through these fields.

Start with a subscription. Configure an HTTPS response using the examples above, add it to DoDo and test the connection. You do not need a DoDo dashboard or to share a private API token with us.