Rate Limiting Explained

Types of Rate Limits

Weather Source APIs apply 3 distinct rate limits:

If you require modification to your account permissions, please contact support@weathersource.com.

Credits Per Day

Each Weather Source APIs account is granted an allowance of credits per day. The count of utilized credits is reset daily at midnight UTC. This rate limit is applied collectively across all Weather Source APIs the account has permission to access. The “Credits Per Day” rate limit exists to provide an allowance of value to each client account.

A “credit” is defined as the returned rows of data multiplied by the weight associated with that request. You can view the weights associated with each API in the account section of this developer portal.

For example, if a request is made for 15 days of forecast and the account’s credit weight for daily forecast is 0.5, the credits used by that request would be 7.5 credits (15 returned rows * 0.5 credit weight). Similarly, if a full year of hourly history was requested and the account’s credit weight for hourly history is 0.1, the credits used by that request would be 876 credits (8,760 returned rows * 0.1 credit weight). The credit weights used in these examples are arbitrary and for demonstrative purposes only. Please reference your account summary to determine the actual credit weights for each resource.

The Weather Source Lightning API has one distinction in behavior as it calculates credit utilization. Because in this context a response of zero rows has value in meaning, the Lightning API will calculate credits used with a minimum row count of 1, even if no rows are returned.

Requests Per Second

Each Weather Source APIs account is granted an allowance of requests per second. This rate limit is applied collectively across all Weather Source APIs the account has permission to access. The “Requests Per Second” rate limit exists to protect Weather Source network infrastructure and provide reliable service to all our clients.

A “request” is defined as an HTTP request to a Weather Source API.

Requested Rows Per Second

Each Weather Source APIs account is granted an allowance of requested rows per second. This rate limit is applied collectively across all Weather Source APIs the account has permission to access. The “Requested Rows Per Second” rate limit exists to protect Weather Source network infrastructure and provide reliable service to all our clients.

“Requested rows” is defined as a the number of rows requested from a Weather Source API. If the number of rows that an API may return is unknown (as with the Lightning API), a value of 1 requested row is used.

For example, if a full year of hourly history is requested, the number of requested rows would be 8,760 rows (365 days * 24 hours).

NOTE: “Requested rows” is distinct from the “returned rows”. For example, if you request a full hourly forecast, this resource may return up to 240 rows of data. However, depending on the age of the last model run, the number of rows returned may be 235 rows (hypothetically). In this case, the “requested rows” used for the calculation of the “requested rows per second” rate limit is 240 rows. The “returned rows” used to calculate the “credits per day” rate limit is 235 rows.