Help center

Submit credentials you own or have explicit authorization to supply. Check your provider’s terms and the channel’s eligibility before submitting. Never upload a key you found online or received without permission.

Create an account, verify your email, and sign in. Open Add key, choose an available channel and format, check the published rate, and fill in the required fields.

Available formats depend on the channel you choose. The upload form supports a standalone API key, an HTTPS endpoint and key, an access key pair, or service account JSON when the selected channel permits it.

Pricing is the published rate catalog. Add key only shows channels with a published rate that are open for submission right now. If a channel is missing, it is not accepting submissions at the moment. Check back later or contact support.

Each listed channel has one Api4sale.si rate in USDT per $1 of accepted usage. For example, compare rates in Pricing, then confirm the selected rate in Add key before submitting. The rate alone does not predict usage or what will be credited to your balance.

An administrator sets the published rate. You see the current rate when adding a key. A rate edit applies to new submissions, while previously recorded rates stay in submission history. If the rate changes while the form is open, review the updated rate and submit again.

Key monitor shows cumulative usage measured for your keys, in USD. Total credited earnings is the sum of positive USDT ledger entries. Current balance reflects ledger credits and debits. Available to cash out also subtracts pending reservations. Usage and the published rate do not automatically create ledger credits.

There is no guaranteed daily usage or income. A key may show little or no activity during a period. Use Key monitor to check its status and measurement time, and Balance to see what has actually been credited.

An accepted submission gets a key reference and starts as pending. Allow about 10–15 minutes for initial verification and startup. That is an estimate. Open Key monitor and choose Refresh usage to check the latest status.

Usage can take 2–4 hours to update. Measured is when usage was last collected. Refreshed is when Api4sale.si last checked. Refreshing checks for a newer reading and can still return the same measurement.

Pending means validation is underway. Online is the latest online status reported for the key. Invalid, banned or attention indicate a problem with the key. Unavailable means the key record could not be retrieved. An online status does not guarantee new usage.

Open Recent submissions. Use Retry saved request to send the original attempt again, or Check mapping to look for a key reference. If the mapping is missing, the outcome may still be unresolved. Keep using the saved attempt instead of starting a new upload for the same credential.

Compare the same key and time period, and check the measured timestamp before drawing a conclusion. If you need to report a mismatch, keep the key reference, timestamps and figures, with any secrets removed. The monitor shows the cumulative measured reading.

Submit a TRON (TRC20) receiving address. Once the team records a 0.10 USDT test transfer, check that it reached your wallet and confirm receipt in the portal. A new address goes through verification again.

After your address is approved, open Cash out and enter an amount within your available balance. The portal reserves the amount while the request is pending. An administrator records payment after an external transfer, and the transfer reference appears in Cashout history. Rejection releases the reservation.

Cashouts currently require manual processing. The planned automatic tier covers requests below 5,000 USDT once a payment integration is connected. Check Cashout history for your request status and recorded transfer reference.

There is no referral rewards feature in this portal. Your balance is based on recorded USDT ledger entries.

Check your spam folder, then use Request a new code on the Verify your email page. Enter the email you registered with and the newest six-digit code. Codes and verification links expire after 30 minutes. A verification email also carries a sign-in link as a backup.

Open Account security and start setup. Add the displayed setup key to your authenticator app, then enter its six-digit code to enable 2FA. You’ll need a fresh code at sign-in. Keep access to your authenticator because self-service recovery is unavailable.

Use Add key for individual API credentials. Keep passwords, API keys, authenticator setup keys and wallet recovery phrases out of chat and screenshots. Key monitor displays references and status.

For a key issue, note the channel, key reference, status, and measurement time. For a cashout, note its date, amount, network, and transfer reference if shown. Share only these non-secret details with your administrator.