The API takes your HTML/CSS and runs it inside a real instance of Google Chrome to convert your html into an image. Use Ruby to send the API your HTML/CSS. You’ll get back the URL to your generated image.
require"htmlcsstoimage"# Retrieve your user id and api key from https://htmlcsstoimage.com/dashboardclient=HTMLCSSToImage.new(user_id: "user-id",api_key: "api-key")
Alternatively, you can set ENV["HCTI_USER_ID"] and ENV["HCTI_API_KEY"]. These will be loaded automatically.
Custom headers used with generate_create_and_render_url are visible in the generated URL. Do not include long-lived credentials.
Template signature change in 0.2.0
Ruby client 0.1.x URL-decoded the template query string before generating its HMAC. Version 0.2.0 signs the encoded query string exactly as it appears after ?, as required by the current API.
Regenerating a template URL with the same inputs after upgrading produces a different token. Existing URLs generated by 0.1.x continue to work.
To see additional methods available with the Ruby gem, see the documentation here.
Example with HTTParty
This example uses the HTTParty gem. Install with gem install httparty, or add it to your Gemfile.
require"httparty"# Retrieve your user id and api key from the Dashboardauth={username: 'user_id',password: 'api_key'}html="<div class='ping'>Pong ✅</div>"css=".ping { padding: 20px; font-family: 'sans-serif'; }"image=HTTParty.post("https://hcti.io/v1/image",body: {html: html,css: css},basic_auth: auth)# => {"url"=>"https://hcti.io/v1/image/bde7d5bf-f7bb-49d9-b931-74e5512b8738"}
Ruby on Rails example with caching
This example uses Rails built in caching.
The cache key is a SHA of your html/css and google fonts.
You’ll only generate a unique image once.
If your HTML changes at all, a new image will be created. Subsequent calls using the same HTML/CSS parameters will return the cached URL rather than creating a new image.