Skip to main content

Infrastructure as Code

Updated on
Oct 06, 2026

Quicknode lets you manage infrastructure as code with Terraform or OpenTofu. Define RPC endpoints, access controls, Streams, and Key-Value Store in configuration files. Keep those files in version control, review planned changes before applying them, and reuse the same setup across environments. Both CLIs use the same Quicknode provider, which is listed in the Terraform Registry and OpenTofu Registry.

For a longer walkthrough, read Manage Quicknode Infrastructure with Terraform.

Resources you can manage​

Use this list to find the resource you need. Each reference includes its fields and a configuration example. The RPC endpoint guide and KV-backed Stream guide show complete workflows.

RPC endpoints and access​

ResourceWhat it managesLearn more
quicknode_endpointAn RPC endpoint's chain, network, status, label, and security switches.Reference · Guide
quicknode_endpoint_tokenAn additional endpoint authentication token for one caller or application.Reference
quicknode_endpoint_jwtA public signing key whose JWTs can authenticate callers.Reference · Guide
quicknode_endpoint_domain_maskA custom hostname for an endpoint; the hostname also needs DNS configuration.Reference · Guide
quicknode_endpoint_ipAn IP address allowed to call an endpoint when IP restrictions are enabled.Reference
quicknode_endpoint_referrerAn allowed browser referrer when referrer restrictions are enabled.Reference
quicknode_endpoint_request_filterThe RPC methods an endpoint accepts.Reference
quicknode_endpoint_rate_limitsEndpoint-wide request limits, overriding selected plan defaults.Reference
quicknode_endpoint_method_rate_limitA separate rate limit for specified RPC methods.Reference

Security entries and enforcement switches are separate. For example, registering a JWT key does not enforce JWT authentication until security_options.jwts is enabled on the endpoint. See Create and secure an RPC endpoint for the order of operations.

Key-Value Store and Streams​

ResourceWhat it managesLearn more
quicknode_kv_listEvery item in a KV list. A later apply removes items added outside the configuration.Reference
quicknode_kv_list_itemsOnly specified items in a shared KV list; other writers' items remain.Reference · Guide
quicknode_kv_valueOne KV value, such as a filter threshold or a contract ABI.Reference · Guide
quicknode_streamA Stream's network, dataset, filter, destination, and lifecycle configuration.Reference · Guide

Before managing a KV list, see how whole-list and selected-item ownership differ.

Data sources you can read​

Data sources read existing Quicknode information. They do not create or change the resources they read.

Data sourceWhat it readsLearn more
quicknode_chainsSupported chains and network slugs.Reference
quicknode_endpointOne existing endpoint, by ID or label.Reference
quicknode_endpointsEndpoints on the account, optionally filtered.Reference
quicknode_endpoint_urlsCurrent endpoint URLs, including credential-bearing URLs. Treat them as sensitive.Reference
quicknode_kv_listItems currently in a KV list.Reference
quicknode_kv_valueThe current value of a KV key.Reference
quicknode_streamAn existing Stream by ID, including its destination configuration.Reference

Start with an RPC endpoint or a KV-backed Stream. If you already created resources in the dashboard, read Operations before importing or changing them.