mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2025-03-14 04:51:42 +01:00
Update content of files
This commit is contained in:
GitHub Action
parent
df39c2ac45
commit
712cd49882
5 changed files with 24 additions and 52 deletions
|
|
@ -4,40 +4,10 @@
|
|||
<meta charset="utf-8">
|
||||
<title>payments.refundStarsCharge</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta property="description" content="Parameters
|
||||
Name
|
||||
Type
|
||||
Description
|
||||
user_id
|
||||
InputUser
|
||||
|
||||
charge_id
|
||||
string
|
||||
|
||||
Result
|
||||
Updates
|
||||
Possible errors
|
||||
Code
|
||||
Type
|
||||
Description…">
|
||||
<meta property="description" content="Refund a Telegram Stars transaction, see here » for more info.">
|
||||
<meta property="og:title" content="payments.refundStarsCharge">
|
||||
<meta property="og:image" content="">
|
||||
<meta property="og:description" content="Parameters
|
||||
Name
|
||||
Type
|
||||
Description
|
||||
user_id
|
||||
InputUser
|
||||
|
||||
charge_id
|
||||
string
|
||||
|
||||
Result
|
||||
Updates
|
||||
Possible errors
|
||||
Code
|
||||
Type
|
||||
Description…">
|
||||
<meta property="og:description" content="Refund a Telegram Stars transaction, see here » for more info.">
|
||||
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
|
||||
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
|
||||
|
|
@ -72,7 +42,8 @@ Description…">
|
|||
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/methods" >All Methods</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/method/payments.refundStarsCharge" >payments.refundStarsCharge</a></li></ul></div>
|
||||
<h1 id="dev_page_title">payments.refundStarsCharge</h1>
|
||||
|
||||
<div id="dev_page_content"><p><div class="clearfix">
|
||||
<div id="dev_page_content"><p>Refund a <a href="/api/stars">Telegram Stars</a> transaction, see <a href="/api/payments#6-refunds">here »</a> for more info.</p>
|
||||
<p><div class="clearfix">
|
||||
<ul class="dev_layer_select slightly-pull-right nav nav-pills">
|
||||
<li class="dropdown">
|
||||
<a class="dropdown-toggle" onclick="return dropdownClick(this, event)" href="#">Layer 181 <b class="caret"></b></a>
|
||||
|
|
@ -106,12 +77,12 @@ Description…">
|
|||
<tr>
|
||||
<td><strong>user_id</strong></td>
|
||||
<td style="text-align: center;"><a href="/type/InputUser">InputUser</a></td>
|
||||
<td> </td>
|
||||
<td>User to refund.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>charge_id</strong></td>
|
||||
<td style="text-align: center;"><a href="/type/string">string</a></td>
|
||||
<td> </td>
|
||||
<td>Transaction ID.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -139,7 +110,12 @@ Description…">
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3></div>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3>
|
||||
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
|
||||
<h4><a class="anchor" href="#telegram-stars" id="telegram-stars" name="telegram-stars"><i class="anchor-icon"></i></a><a href="/api/stars">Telegram Stars</a></h4>
|
||||
<p>Telegram Stars are an in-app currency that allows the user to pay for digital goods and services offered by <a href="https://telegram.org/blog/telegram-stars">Telegram bots</a> or <a href="https://telegram.org/blog/mini-app-bar-paid-media-and-more#pay-for-content-with-telegram-stars">Telegram channels</a>.</p>
|
||||
<h4><a class="anchor" href="#payments-api" id="payments-api" name="payments-api"><i class="anchor-icon"></i></a><a href="/api/payments">Payments API</a></h4>
|
||||
<p>You can accept payments from Telegram users via Telegram Bots.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,10 +4,10 @@
|
|||
<meta charset="utf-8">
|
||||
<title>users.getIsPremiumRequiredToContact</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta property="description" content="Check whether we can write to the specified user (non-Premium users only). If a user enables their new_noncontact_peers_require_premium global privacy setting, represented in userFull.contact_require_premium, only users that have a premium account, are in our contact list, or already have a private chat with them can write to them in private. To easily check whether we can write to a user with this flag enabled, if we haven't yet cached all the required information (for example we don't have the userFull or history of all users while displaying the chat list in the sharing UI) this method may be invoked, passing the list of users currently visible in the UI, returning a list of booleans that directly specify whether we can or cannot write to each user. This list may then be used, for example, to display a lock near the avatar of each user that we cannot write to, with an appropriate tooltip to purchase a Premium subscription. Note that this method should only be invoked if we don't have a Premium subscription, only for users whose full info (userFull + message history information) is not cached yet, as the same info can be computed locally if all the mentioned information is available, and updated automatically using the usual updates.">
|
||||
<meta property="description" content="Check whether we can write to the specified user (non-Premium users only), see here » for more info on the full flow.">
|
||||
<meta property="og:title" content="users.getIsPremiumRequiredToContact">
|
||||
<meta property="og:image" content="">
|
||||
<meta property="og:description" content="Check whether we can write to the specified user (non-Premium users only). If a user enables their new_noncontact_peers_require_premium global privacy setting, represented in userFull.contact_require_premium, only users that have a premium account, are in our contact list, or already have a private chat with them can write to them in private. To easily check whether we can write to a user with this flag enabled, if we haven't yet cached all the required information (for example we don't have the userFull or history of all users while displaying the chat list in the sharing UI) this method may be invoked, passing the list of users currently visible in the UI, returning a list of booleans that directly specify whether we can or cannot write to each user. This list may then be used, for example, to display a lock near the avatar of each user that we cannot write to, with an appropriate tooltip to purchase a Premium subscription. Note that this method should only be invoked if we don't have a Premium subscription, only for users whose full info (userFull + message history information) is not cached yet, as the same info can be computed locally if all the mentioned information is available, and updated automatically using the usual updates.">
|
||||
<meta property="og:description" content="Check whether we can write to the specified user (non-Premium users only), see here » for more info on the full flow.">
|
||||
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
|
||||
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
|
||||
|
|
@ -80,11 +80,7 @@
|
|||
<h4><a class="anchor" href="#telegram-premium" id="telegram-premium" name="telegram-premium"><i class="anchor-icon"></i></a><a href="/api/premium">Telegram Premium</a></h4>
|
||||
<p>Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.</p>
|
||||
<h4><a class="anchor" href="#privacy" id="privacy" name="privacy"><i class="anchor-icon"></i></a><a href="/api/privacy">Privacy</a></h4>
|
||||
<p>Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.</p>
|
||||
<h4><a class="anchor" href="#userfull" id="userfull" name="userfull"><i class="anchor-icon"></i></a><a href="/constructor/userFull">userFull</a></h4>
|
||||
<p>Extended user info</p>
|
||||
<h4><a class="anchor" href="#working-with-updates" id="working-with-updates" name="working-with-updates"><i class="anchor-icon"></i></a><a href="/api/updates">Working with Updates</a></h4>
|
||||
<p>How to subscribe to updates and handle them properly.</p></div>
|
||||
<p>Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -3366,7 +3366,7 @@ Look for updates of telegram's terms of service…">
|
|||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/users.getIsPremiumRequiredToContact">users.getIsPremiumRequiredToContact</a></td>
|
||||
<td>Check whether we can write to the specified user (non-<a href="/api/premium">Premium</a> users only).<br><br>If a user enables their <strong>new_noncontact_peers_require_premium</strong> <a href="/api/privacy#global-privacy-settings">global privacy setting</a>, represented in <a href="/constructor/userFull">userFull</a>.<code>contact_require_premium</code>, only users that have a premium account, are in our contact list, or already have a private chat with them can write to them in private.<br><br>To easily check whether we can write to a user with this flag enabled, if we haven't yet cached all the required information (for example we don't have the <a href="/constructor/userFull">userFull</a> or history of all users while displaying the chat list in the sharing UI) this method may be invoked, passing the list of users currently visible in the UI, returning a list of booleans that directly specify whether we can or cannot write to each user.<br><br>This list may then be used, for example, to display a lock near the avatar of each user that we cannot write to, with an appropriate tooltip to purchase a <a href="/api/premium">Premium</a> subscription.<br><br>Note that this method should <strong>only</strong> be invoked if we don't have a <a href="/api/premium">Premium</a> subscription, only for users whose full info (<a href="/constructor/userFull">userFull</a> + message history information) is not cached yet, as the same info can be computed locally if all the mentioned information is available, and updated automatically using the usual <a href="/api/updates">updates</a>.</td>
|
||||
<td>Check whether we can write to the specified user (non-<a href="/api/premium">Premium</a> users only), see <a href="/api/privacy#require-premium-for-new-non-contact-users">here »</a> for more info on the full flow.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/channels.setBoostsToUnblockRestrictions">channels.setBoostsToUnblockRestrictions</a></td>
|
||||
|
|
@ -3506,23 +3506,23 @@ Look for updates of telegram's terms of service…">
|
|||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.getStarsTopupOptions">payments.getStarsTopupOptions</a></td>
|
||||
<td> </td>
|
||||
<td>Obtain a list of <a href="/api/stars#buying-stars">Telegram Stars topup options »</a> as <a href="/constructor/starsTopupOption">starsTopupOption</a> constructors.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.getStarsStatus">payments.getStarsStatus</a></td>
|
||||
<td> </td>
|
||||
<td>Get the current <a href="/api/stars">Telegram Stars balance</a> of the current account (with peer=<a href="/constructor/inputPeerSelf">inputPeerSelf</a>), or the stars balance of the bot specified in <code>peer</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.getStarsTransactions">payments.getStarsTransactions</a></td>
|
||||
<td> </td>
|
||||
<td>Fetch <a href="/api/stars#balance-and-transaction-history">Telegram Stars transactions</a>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.sendStarsForm">payments.sendStarsForm</a></td>
|
||||
<td> </td>
|
||||
<td>Make a payment using <a href="/api/stars#using-stars">Telegram Stars, see here »</a> for more info.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.refundStarsCharge">payments.refundStarsCharge</a></td>
|
||||
<td> </td>
|
||||
<td>Refund a <a href="/api/stars">Telegram Stars</a> transaction, see <a href="/api/payments#6-refunds">here »</a> for more info.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table></div>
|
||||
|
|
|
|||
|
|
@ -635,7 +635,7 @@
|
|||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.refundStarsCharge">payments.refundStarsCharge</a></td>
|
||||
<td> </td>
|
||||
<td>Refund a <a href="/api/stars">Telegram Stars</a> transaction, see <a href="/api/payments#6-refunds">here »</a> for more info.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table></div>
|
||||
|
|
|
|||
|
|
@ -87,11 +87,11 @@
|
|||
<tbody>
|
||||
<tr>
|
||||
<td><a href="/method/payments.getStarsStatus">payments.getStarsStatus</a></td>
|
||||
<td> </td>
|
||||
<td>Get the current <a href="/api/stars">Telegram Stars balance</a> of the current account (with peer=<a href="/constructor/inputPeerSelf">inputPeerSelf</a>), or the stars balance of the bot specified in <code>peer</code>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="/method/payments.getStarsTransactions">payments.getStarsTransactions</a></td>
|
||||
<td> </td>
|
||||
<td>Fetch <a href="/api/stars#balance-and-transaction-history">Telegram Stars transactions</a>.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue