You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloudthread provides a powerful and flexible REST Developer API to help you get the most out of your data.
3
+
Cloudthread provides a powerful and flexible **REST Developer API** to help you get the most out of your data.
4
4
5
-
This page shows how to use the API, and what features are currently available.
5
+
These docs show how to use the API, and what features are currently available.
6
+
7
+
{% hint style="info" %}
8
+
**Good to know:** All the API methods referenced in the docs are synced to a Swagger file URL (**OpenAPI v3**) and are kept up to date **automatically** with changes to the API.
Cloudthread requires an **API Token** to process incoming developer API requests. 
12
19
13
-
Cloudthread requires an API Token to process incoming developer API requests. Admin's have the ability to generate API Tokens on the Cloudthread platform within the **Settings** tab.
20
+
Admin's have the ability to generate API Tokens on the Cloudthread platform within the [Settings](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/settings"mention") tab.
21
+
{% endhint %}
14
22
15
23
This API Token should be included in the headers for all Developer API requests as follows:
16
24
17
25
`x-api-key: {API_TOKEN}`
18
26
19
-
Any request without a valid token will be rejected.
27
+
{% hint style="danger" %}
28
+
Any request without a valid token will be **rejected**.
29
+
{% endhint %}
20
30
21
-
## Custom Data Ingestion
31
+
## Custom Data ingestion
22
32
23
33
Cloudthread provides the ability to send custom data to our systems that can then be used in your Cost Views and Unit Metrics.
24
34
25
-
In order to send custom data, you must provision a **Custom Data - Data Stream Token** on the Cloudthread platform within the **Settings** tab.
35
+
In order to send custom data, you must provision a **Custom Data - Data Stream Token** on the Cloudthread platform within the [Settings](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/settings"mention") tab.
26
36
27
37
{% content-ref url="custom_data.md" %}
28
38
[custom\_data.md](custom\_data.md)
29
39
{% endcontent-ref %}
30
40
31
-
Data sent via this API will appear in **Costs Overview**and **Unit Metrics Lab** on Cloudthread's platform.
41
+
Data sent via this API will appear in [Costs Overview](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/costs-overview"mention")and [Unit Metrics Lab](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/unit-metrics-lab"mention") on Cloudthread's platform.
32
42
33
-
## Event Overlay Ingestion
43
+
## Event Overlay ingestion
34
44
35
-
Cloudthread provides the ability to send webhook Events that can be overlayed on top of your Cost Viewsand Unit Metrics.
45
+
Cloudthread provides the ability to send **webhook****events** that can be overlayed on top of your [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view"mention")and [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric"mention"). See [Events Overlay](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/events-overlay"mention") for more details.
36
46
37
47
{% content-ref url="events.md" %}
38
48
[events.md](events.md)
39
49
{% endcontent-ref %}
40
50
41
-
Data sent via this API will appear in **Costs Overview**and **Unit Metrics Lab** on Cloudthread's platform.
51
+
Data sent via this API will appear in [Costs Overview](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/costs-overview"mention")and [Unit Metrics Lab](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/unit-metrics-lab"mention") on Cloudthread's platform.
42
52
43
-
## Tag Catalog Fetch
53
+
## Tag Catalog fetch
44
54
45
-
Cloudthread provides the ability to fetch a Tag Catalog entry via catalog key.
55
+
Cloudthread provides the ability to fetch a [Tags Catalog](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/tag-assistant/tag-catalogs"mention") entry via catalog key.
46
56
47
57
{% content-ref url="tag_catalog.md" %}
48
58
[tag\_catalog.md](tag\_catalog.md)
49
59
{% endcontent-ref %}
50
60
51
-
## Cost View and Unit Metric Data Fetch
61
+
## Cost View and Unit Metric Data fetch
52
62
53
-
Cloudthread provides the ability to fetch a Cost View and Unit Metric data.
63
+
Cloudthread provides the ability to fetch [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view"mention")and [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric"mention") data.
54
64
55
65
{% content-ref url="metrics.md" %}
56
66
[metrics.md](metrics.md)
57
67
{% endcontent-ref %}
58
68
59
69
## Users and Teams setup
60
70
61
-
API can be used to set up UsersandTeams.
71
+
API can be used to set up and change **Users** (see [User Management](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/settings/account-and-team-management"mention")) and [Teams](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/settings/teams"mention").
62
72
63
73
{% content-ref url="users.md" %}
64
74
[users.md](users.md)
@@ -67,3 +77,11 @@ API can be used to set up Users and Teams.
67
77
{% content-ref url="teams.md" %}
68
78
[teams.md](teams.md)
69
79
{% endcontent-ref %}
80
+
81
+
## Savings Hub manipulation
82
+
83
+
API to retrive and setup [Savings Opportunities](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-savings/key-concepts/optimization-opportunities"mention") and [Savings Threads](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-savings/key-concepts/savings-threads"mention").
Copy file name to clipboardExpand all lines: reference/api-reference/custom_data.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,18 @@
1
1
# Data Ingestion
2
2
3
-
Cloudthread can process custom data for generating Cost Viewsand Unit Metrics.
3
+
Cloudthread can process custom data for generating [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view"mention")and [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric"mention").
4
4
5
-
In order to send custom data, you must provision a **Custom Data - Data Stream Token** on the Cloudthread platform within the **Settings** tab.
5
+
In order to send custom data, you must provision a **Custom Data - Data Stream Token** on the Cloudthread platform within the [Settings](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/settings"mention") tab.
6
+
7
+
{% hint style="info" %}
8
+
See more in [Ingesting Custom Data](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/guides/monitoring-cloud-costs/ingesting-custom-data"mention") guide.
To send custom data to Cloudthread, use the endpoint above with the provisioned Data Stream Token and the following payload
15
+
To send custom data to Cloudthread, use the endpoint above with the provisioned **Data Stream Token** and the following payload:
12
16
13
17
```json
14
18
{
@@ -35,10 +39,10 @@ To send custom data to Cloudthread, use the endpoint above with the provisioned
35
39
*`mertic_value`: float convertiable value of the metric.
36
40
*`custom_dimensions`: map of **up to 10** key value pairs that you will be able to segment the data by on the Cloudthread platform.
37
41
38
-
If the data pass validation and successfully save you'll receive a `201` status code.
39
-
40
-
Cloudthread creates a record ID for each data point by hashing the metric name, metric aggreation function, and the custom dimensions into a single key. To update a data point that's already been sent, the incoming data point must match along these fields -- otherwise a new data point will be generated. You can then update a given timestamp and metric value pair by sending in the matching timestamp with a new metric value.
41
-
42
-
{% hint style="info" %}
43
-
**Good to know:** All the methods shown below are synced to an example Swagger file URL and are kept up to date automatically with changes to the API.
42
+
{% hint style="success" %}
43
+
If the data pass **validation** and successfully save you'll receive a `201` status code.
44
44
{% endhint %}
45
+
46
+
* Cloudthread creates a record ID for each data point by hashing the metric name, metric aggregation function, and the custom dimensions into a single key.
47
+
* To update a data point that's already been sent, the incoming data point must match along these fields -- otherwise a new data point will be generated.
48
+
* You can then update a given timestamp and metric value pair by sending in the matching timestamp with a new metric value.
Copy file name to clipboardExpand all lines: reference/api-reference/events.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
3
3
## Event Overlay Ingestion
4
4
5
-
Cloudthread can process webhook events that can be overlayed on top of your Cost Viewsand Unit Metrics.
5
+
Cloudthread can process **webhook events** that can be overlayed on top of your [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view"mention")and [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric"mention").
To send events data to Cloudthread, use the endpoint above and the following payload
11
+
To send events data to Cloudthread, use the endpoint above and the following payload:
12
12
13
13
```json
14
14
{
@@ -28,15 +28,13 @@ To send events data to Cloudthread, use the endpoint above and the following pay
28
28
```
29
29
30
30
*`timestamp`: datetime with **hourly** granularity. Any timestamp with minutes, seconds, etc. will be rejected. E.g. `'2022-10-01 00:00:00'`. To send daily data, send data with the timepart = `00:00:00`.
31
-
*`team_id`: OPITIONAL - integer ID of the team for which the event is tied. If this value is set, only users on this team (and admins) will be able to see this event on the platform. Invalid team IDs will be rejected.
31
+
*`team_id`: OPITIONAL – integer ID of the team for which the event is tied. If this value is set, only users on this team (and admins) will be able to see this event on the platform. Invalid team IDs will be rejected.
32
32
*`decscription`: text describing event.
33
-
*`type`: event type to help organize and filter events on the platform - please ensure types are consistent across events to create easy filtering.
34
-
*`event_url`: OPTIONAL - link to get more information about the sent event.
33
+
*`type`: event type to help organize and filter events on the platform – please ensure types are consistent across events to create easy filtering.
34
+
*`event_url`: OPTIONAL – link to get more information about the sent event.
35
35
36
-
If the data pass validation and successfully save you'll receive a `201` status code.
37
-
38
-
Data sent via this API will appear in **Costs Overview** and **Unit Metrics Lab** on Cloudthread's platform.
39
-
40
-
{% hint style="info" %}
41
-
**Good to know:** All the methods shown below are synced to an example Swagger file URL and are kept up to date automatically with changes to the API.
36
+
{% hint style="success" %}
37
+
If the data pass **validation** and successfully save you'll receive a `201` status code.
42
38
{% endhint %}
39
+
40
+
Data sent via this API will appear in [Costs Overview](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/costs-overview"mention") and [Unit Metrics Lab](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/unit-metrics-lab"mention") on Cloudthread's platform.
Copy file name to clipboardExpand all lines: reference/api-reference/metrics.md
+30-16Lines changed: 30 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,38 +2,52 @@
2
2
3
3
## Cost View Fetch
4
4
5
-
Cloudthread provides the ability to query your [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view).
5
+
Cloudthread provides the ability to query your [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view"mention").
*`metric_id`: the ID of the Cost View you wish to query.
11
+
To query [Cost Views](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-transparency/key-concepts/cost-view"mention"), use the endpoint above and the following query parameters:
12
12
13
-
To query Cost Views, use the endpoint above and the following query parameters
13
+
* Path (go after `/` in the URL)
14
+
*`metric_id`: the ID of the Cost View you wish to query
15
+
* Query (go after `?` in the URL)
16
+
*`start_date`: start date of the timeframe you wish to query – formatted as YYYY-MM-DD, required
17
+
*`end_date`: inclusive end date of the timeframe you wish to query – formatted as YYYY-MM-DD
18
+
*`cost_type`: OPTIONAL – specifies the cost type (Unblended, Public, etc.)
19
+
*`amortization`: OPTIONAL – specifies if to include amortization
20
+
*`exclude`: OPTIONAL – specifies if to exclude taxes, refunds, etc.
21
+
*`granularity`: OPTIONAL – specifies the data granularity (hour, day, week, quarter, year)
14
22
15
-
*`start_date`: start date of the timeframe you wish to query - formatted as YYYY-MM-DD
16
-
*`end_date`: inclusive end date of the timeframe you wish to query - formatted as YYYY-MM-DD
17
-
18
-
If the data pass validation a `200` status code.
23
+
{% hint style="info" %}
24
+
If the data pass **validation** a `200` status code.
25
+
{% endhint %}
19
26
20
27
## Unit Metric Fetch
21
28
22
-
Cloudthread provides the ability to query your [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric).
29
+
Cloudthread provides the ability to query your [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric"mention").
*`metric_id`: the ID of the Unit Metric you wish to query.
29
-
30
-
To query Unit Metrics, use the endpoint above and the following query parameters
35
+
To query [Unit Metrics](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/unit-metrics/key-concepts/unit-metric"mention") use the endpoint above and the following query parameters:
31
36
32
-
*`start_date`: start date of the timeframe you wish to query - formatted as YYYY-MM-DD
33
-
*`end_date`: inclusive end date of the timeframe you wish to query - formatted as YYYY-MM-DD
34
-
35
-
If the data pass validation a `200` status code.
37
+
* Path (go after `/` in the URL)
38
+
*`metric_id`: the ID of the Unit Metric you wish to query.
39
+
* Query (go after `?` in the URL)
40
+
*`start_date`: start date of the timeframe you wish to query - formatted as YYYY-MM-DD
41
+
*`end_date`: inclusive end date of the timeframe you wish to query - formatted as YYYY-MM-DD
42
+
*`cost_type`: OPTIONAL – specifies the cost type (Unblended, Public, etc.)
43
+
*`amortization`: OPTIONAL – specifies if to include amortization
44
+
*`exclude`: OPTIONAL – specifies if to exclude taxes, refunds, etc.
45
+
*`granularity`: OPTIONAL – specifies the data granularity (hour, day, week, quarter, year)
36
46
37
47
{% hint style="info" %}
38
-
**Good to know:** All the methods shown below are synced to an example Swagger file URL and are kept up to date automatically with changes to the API.
48
+
If the data pass **validation** a `200` status code.
49
+
{% endhint %}
50
+
51
+
{% hint style="success" %}
52
+
See the response data **schema** at the method description above.
This API allows to work with [Savings Opportunities](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/cost-savings/key-concepts/optimization-opportunities"mention").
Copy file name to clipboardExpand all lines: reference/api-reference/tag_catalog.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,16 @@
2
2
3
3
## Tag Catalog Fetch
4
4
5
-
Cloudthread provides the ability to fetch a Tag Catalog entry via catalog key.
5
+
Cloudthread provides the ability to fetch a [Tags Catalog](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/tag-assistant/tag-catalogs"mention") entry via catalog key.
6
+
7
+
{% hint style="info" %}
8
+
See [Setting up Tag Catalog](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/guides/tagging-cloud-resources/setting-up-tag-catalog"mention") guide for more details.
To query Tag Catalog, use the endpoint above and the following query parameters
15
+
To query [Tags Catalog](http://127.0.0.1:5000/s/XCkDKj2xeiQhlyRGF6Wr/fundamentals/tag-assistant/tag-catalogs"mention"), use the endpoint above and the following query parameters
12
16
13
17
*`catalog_key`: the ID of the Catalog entry you wish to query
14
-
15
-
{% hint style="info" %}
16
-
**Good to know:** All the methods shown below are synced to an example Swagger file URL and are kept up to date automatically with changes to the API.
0 commit comments