Skip to content

Commit e1a213a

Browse files
author
Sentio Bot
committed
chore: update
1 parent f583315 commit e1a213a

File tree

3 files changed

+14
-14
lines changed

3 files changed

+14
-14
lines changed

doc/index.html

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9482,7 +9482,7 @@ <h1>executeSQL</h1>
94829482
<p></p>
94839483
<p class="marked">Execute SQL in a project. Go to &quot;Data Studio&quot; -&gt; &quot;SQL Editor&quot;, write your query and then click &quot;Export as cURL&quot;
94849484

9485-
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(102).png)
9485+
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(102).png)
94869486

94879487
Find more: https://docs.sentio.xyz/reference/data#sql-api</p>
94889488
<p></p>
@@ -14923,7 +14923,7 @@ <h1>queryRange</h1>
1492314923
<p></p>
1492414924
<p class="marked">The easiest way to build query is through UI, you could first create an insight chart, and then **Export as cURL**.
1492514925

14926-
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(101).png)</p>
14926+
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(101).png)</p>
1492714927
<p></p>
1492814928
<br />
1492914929
<pre class="prettyprint language-html prettyprinted" data-type="post"><code><span class="pln">/api/v1/metrics/{owner}/{slug}/query_range</span></code></pre>
@@ -18997,11 +18997,11 @@ <h1>getCallTraceByTransaction</h1>
1899718997
<p></p>
1899818998
<p class="marked">API to get Sentio call trace. It takes &#x60;txId.txHash&#x60; and &#x60;chainSpec.chainId&#x60; arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.
1899918999

19000-
The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional &#x60;startIndex&#x60; and &#x60;startIndex&#x60; on each trace entry even for the LOG, representing the execution order in the trace.
19000+
The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional &#x60;startIndex&#x60; and &#x60;startIndex&#x60; on each trace entry even for the LOG, representing the execution order in the trace.
1900119001

1900219002
This allows you to build chart that marks the order of fund flow.
1900319003

19004-
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)</p>
19004+
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png)</p>
1900519005
<p></p>
1900619006
<br />
1900719007
<pre class="prettyprint language-html prettyprinted" data-type="get"><code><span class="pln">/api/v1/solidity/{owner}/{slug}/{chainId}/transaction/{txHash}/call_trace</span></code></pre>
@@ -29844,7 +29844,7 @@ <h1>addCoinByGecko</h1>
2984429844

2984529845
please AWARE that the coingecko id is NOT the same as the symbol of the coin.
2984629846

29847-
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/coingecko_apiid.png)</p>
29847+
![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/coingecko_apiid.png)</p>
2984829848
<p></p>
2984929849
<br />
2985029850
<pre class="prettyprint language-html prettyprinted" data-type="post"><code><span class="pln">/api/v1/prices/add_coin_by_gecko</span></code></pre>

openapi.json

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -225,7 +225,7 @@
225225
"/api/v1/analytics/{owner}/{slug}/sql/execute": {
226226
"post": {
227227
"summary": "Execute SQL",
228-
"description": "Execute SQL in a project. Go to \"Data Studio\" -\u003e \"SQL Editor\", write your query and then click \"Export as cURL\"\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(102).png)\n\nFind more: https://docs.sentio.xyz/reference/data#sql-api",
228+
"description": "Execute SQL in a project. Go to \"Data Studio\" -\u003e \"SQL Editor\", write your query and then click \"Export as cURL\"\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(102).png)\n\nFind more: https://docs.sentio.xyz/reference/data#sql-api",
229229
"operationId": "ExecuteSQL",
230230
"responses": {
231231
"200": {
@@ -1128,7 +1128,7 @@
11281128
"/api/v1/metrics/{owner}/{slug}/query_range": {
11291129
"post": {
11301130
"summary": "Metric range queries",
1131-
"description": "The easiest way to build query is through UI, you could first create an insight chart, and then **Export as cURL**.\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(101).png)",
1131+
"description": "The easiest way to build query is through UI, you could first create an insight chart, and then **Export as cURL**.\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(101).png)",
11321132
"operationId": "QueryRange",
11331133
"responses": {
11341134
"200": {
@@ -1222,7 +1222,7 @@
12221222
"/api/v1/prices/add_coin_by_gecko": {
12231223
"post": {
12241224
"summary": "Add coin by Gecko",
1225-
"description": "adds a coin by its coingecko id.\n\ncoingecko id the API ID of the coin in coingecko web page.\n\nplease AWARE that the coingecko id is NOT the same as the symbol of the coin.\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/coingecko_apiid.png)",
1225+
"description": "adds a coin by its coingecko id.\n\ncoingecko id the API ID of the coin in coingecko web page.\n\nplease AWARE that the coingecko id is NOT the same as the symbol of the coin.\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/coingecko_apiid.png)",
12261226
"operationId": "AddCoinByGecko",
12271227
"responses": {
12281228
"200": {
@@ -2574,7 +2574,7 @@
25742574
"/api/v1/solidity/{owner}/{slug}/{chainId}/transaction/{txHash}/call_trace": {
25752575
"get": {
25762576
"summary": "Get trace by transaction",
2577-
"description": "API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.\n\nThe results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.\n\nThis allows you to build chart that marks the order of fund flow.\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)",
2577+
"description": "API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.\n\nThe results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.\n\nThis allows you to build chart that marks the order of fund flow.\n\n![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png)",
25782578
"operationId": "GetCallTraceByTransaction",
25792579
"responses": {
25802580
"200": {

src/sdk.gen.ts

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ export class DataService {
161161
* Execute SQL
162162
* Execute SQL in a project. Go to "Data Studio" -> "SQL Editor", write your query and then click "Export as cURL"
163163
*
164-
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(102).png)
164+
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(102).png)
165165
*
166166
* Find more: https://docs.sentio.xyz/reference/data#sql-api
167167
*/
@@ -475,7 +475,7 @@ export class DataService {
475475
* Metric range queries
476476
* The easiest way to build query is through UI, you could first create an insight chart, and then **Export as cURL**.
477477
*
478-
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(101).png)
478+
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(101).png)
479479
*/
480480
public static queryRange<ThrowOnError extends boolean = false>(options: Options<QueryRangeData, ThrowOnError>) {
481481
return (options.client ?? _heyApiClient).post<QueryRangeResponse, unknown, ThrowOnError>({
@@ -752,7 +752,7 @@ export class PriceService {
752752
*
753753
* please AWARE that the coingecko id is NOT the same as the symbol of the coin.
754754
*
755-
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/coingecko_apiid.png)
755+
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/coingecko_apiid.png)
756756
*/
757757
public static addCoinByGecko<ThrowOnError extends boolean = false>(options: Options<AddCoinByGeckoData, ThrowOnError>) {
758758
return (options.client ?? _heyApiClient).post<AddCoinByGeckoResponse, unknown, ThrowOnError>({
@@ -1074,11 +1074,11 @@ export class DebugAndSimulationService {
10741074
* Get trace by transaction
10751075
* API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.
10761076
*
1077-
* The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.
1077+
* The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.
10781078
*
10791079
* This allows you to build chart that marks the order of fund flow.
10801080
*
1081-
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png)
1081+
* ![screenshot](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png)
10821082
*/
10831083
public static getCallTraceByTransaction<ThrowOnError extends boolean = false>(options: Options<GetCallTraceByTransactionData, ThrowOnError>) {
10841084
return (options.client ?? _heyApiClient).get<GetCallTraceByTransactionResponse, unknown, ThrowOnError>({

0 commit comments

Comments
 (0)