Inline Hashes API parses your HTML to find out which hashes you need to whitelist in your CSP, when you don't allow "unsafe-inline".
This is specially helpful when you don't have complete control over the generated HTML, but you want to implement web security best practices (for example, you use a web framework that insists on using inline styles and scripts).
The API can be used in 2 ways:
Currently, it detects all relevant "inlines" for "style-src" and "script-src". Support for other directives will be added soon.
Get all inline hashes for a given public webpage.
In this endpoint, you provide the URL and the hash type you need. You get a list with the hashes of all "inlines" in it.
Required request data:
Note: Currently the API only supports `style-src` and `script-src` "inlines".
Fetch - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
[
{
"directive": "script-src",
"line": 67,
"position": 0,
"inline_hash": "sha256-5b0LEPcFqvw935AmQ9uCS1LeaBIbAZaVpOd43sbJsgI="
},
{
"directive": "script-src",
"line": 82,
"position": 0,
"inline_hash": "sha256-pYERp1GFTQcj76yK8huGHJtriZpv9dsW7AdV7O+VrcQ="
},
{
"directive": "script-src",
"line": 169,
"position": 0,
"inline_hash": "sha256-JVVDOwRpMQvCZqoDwpZ1OUJ81UoJpBxumeEHC89A9PU="
},
{
"directive": "script-src",
"line": 198,
"position": 0,
"inline_hash": "sha256-P04sv6Gx4G2SNlC/BLire6NlKJJRrW+WA3R+vPzVvxk="
},
{
"directive": "script-src",
"line": 211,
"position": 0,
"inline_hash": "sha256-RK7LdSEhpwvmYMT+Jix2uBLUXxlWBpHbN6lasgC6hv8="
},
{
"directive": "style-src",
"line": 24,
"position": 4,
"inline_hash": "sha256-FkEXDP5KKSHX3NsiC7GTZPWooqOq+PWhRnOgr48PXTI="
},
{
"directive": "style-src",
"line": 31,
"position": 4,
"inline_hash": "sha256-Lhv+ra57rss0OLQnIUfbs2b64zOZselOiHlKjuyf4+o="
}
]
curl --location --request POST 'https://zylalabs.com/api/2947/inline+hashes+api/3090/fetch' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"url": "https://arraialepico.com",
"alg": "sha256"
}'
Get all inline hashes for a given HTML document.
In this endpoint, you provide the content and the hash type you need. You get a list with the hashes of all "inlines" in the document.
Required request data:
Note: Currently the API only supports `style-src` and `script-src` "inlines".
Extract - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
[
{
"directive": "script-src",
"inline_hash": "sha256-+dZ6udsWxNVoGfScAq7t5IIF5UJb4F6RhjbN6oe1p4w=",
"line": 1,
"position": 55
},
{
"directive": "style-src",
"inline_hash": "sha256-L0KESkAS3Sl/7JaxyYAsy7PaN1uCtBWR56D2Mu98w0M=",
"line": 1,
"position": 12
}
]
curl --location --request POST 'https://zylalabs.com/api/2947/inline+hashes+api/3091/extract' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"content": "",
"alg": "sha256"
}'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Both the Fetch and Extract endpoints return a list of inline hashes for "style-src" and "script-src" directives. Each entry includes the directive type, the inline hash, the line number, and the position of the inline element within the line.
The key fields in the response data include "directive" (indicating the CSP directive), "inline_hash" (the computed hash), "line" (the line number in the HTML), and "position" (the character position of the inline element).
The response data is organized as an array of objects, each representing an inline element. Each object contains fields for the directive type, inline hash, line number, and position, allowing for easy parsing and usage in CSP whitelisting.
Each endpoint accepts two parameters: "url" or "content" (depending on the endpoint) for the HTML source, and "alg" to specify the hash algorithm, which can be "sha256", "sha384", or "sha512".
Typical use cases include enhancing web security by generating hashes for inline scripts and styles when implementing a Content Security Policy (CSP) without allowing "unsafe-inline". This is particularly useful for developers using frameworks that generate inline code.
Users can utilize the returned data by incorporating the inline hashes into their CSP headers. This allows them to whitelist specific inline scripts and styles, thereby improving security while maintaining functionality.
Data accuracy is maintained by parsing the provided HTML or fetching the public webpage directly, ensuring that the inline elements are accurately identified and hashed according to the specified algorithm.
If the response contains partial or empty results, users should check the provided HTML or URL for inline elements. An empty result may indicate no inline scripts or styles were found, which could be intentional or due to an error in the input.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
160ms
Service Level:
100%
Response Time:
9,350ms
Service Level:
100%
Response Time:
748ms
Service Level:
100%
Response Time:
137ms
Service Level:
100%
Response Time:
1,405ms
Service Level:
100%
Response Time:
104ms
Service Level:
100%
Response Time:
1,327ms
Service Level:
100%
Response Time:
1,287ms
Service Level:
100%
Response Time:
1,512ms
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
3,081ms
Service Level:
100%
Response Time:
2,936ms
Service Level:
100%
Response Time:
272ms
Service Level:
100%
Response Time:
471ms
Service Level:
100%
Response Time:
10,597ms
Service Level:
100%
Response Time:
566ms
Service Level:
100%
Response Time:
3,579ms
Service Level:
90%
Response Time:
690ms
Service Level:
100%
Response Time:
3,693ms
Service Level:
100%
Response Time:
4,395ms