Skip to main content
Scaleway Instances, Object Storage, and managed services often sit outside your main cloud bill. Connect with an IAM secret key and Organization ID so consumption lands in Explorer next to AWS, GCP, Azure, and other billing datasources.
1

Create an IAM application

In the Scaleway console, create an IAM application. Attach the BillingReadOnly policy at Organization scope. See Scaleway IAM API keys.
2

Create an API key

Create an API key for that application. Copy the secret key immediately. It is shown once. The access key is optional in Costory. Costory can store it, but the billing API authenticates with the secret key only.
3

Copy the Organization ID

Copy the Organization ID from the Organization dashboard.
4

Connect in Costory

Go to Integrations, click + Add integration, then choose Scaleway under Billing. The connect URL is /integration/new/scaleway/billing.
5

Enter connection details

Fill Connection name (default Scaleway), Secret key, and Organization ID. Access key and Start date are optional. Leave Start date empty to use Costory’s default lookback.
6

Validate, then save

Click Validate. Costory calls GET /billing/v2beta1/consumptions with X-Auth-Token set to the secret key. Save stays disabled until validation succeeds. If this is the only billing source and it is demo data, Costory asks you to confirm before replacing it.
On first sync, Costory backfills up to 12 months of consumption, depending on what Scaleway retains. New data then follows the usual data refresh cadence. SaaS sources typically appear in about 10 minutes.

Field reference

What Costory includes

Costory pulls monthly consumption from the Scaleway Consumption API and maps it into Standard Columns. Typical lines include:
  • Categories such as Compute, Storage, Network, Object Storage, Serverless, and Observability
  • Product name and SKU (for example a VPC Public Gateway size)
  • Project and resource names when Scaleway returns them
  • Billed quantity, unit, and monetary value
How to analyze Scaleway costs
  • Spend by product: group by Service name or SKU
  • Spend by project: group by Billing account id or Sub account id when those fields carry the Scaleway project
  • Spend by invoice category: group by Category
What Costory does not include
  • Credits, promotional discounts, or tax lines that never appear on the consumption API
  • Support or marketplace fees billed outside consumption
  • Write access to your Scaleway organization. Costory only calls the billing read endpoint
Rotate the secret key from Integrations when you need a new credential. The Organization ID stays the same.

Troubleshooting

Billing Data

All billing providers and shared setup notes.

Explorer

Filter and group Scaleway spend with the rest of your stack.

Standard Columns

Normalized cost fields across providers.

Cloudflare billing

Import Cloudflare PayGo usage the same way.
Last modified on August 24, 2026