Render Services - Headers API
Use HTTP headers to inject response headers in static site responses. You can also use wildcards like /path/* to add headers to responses for all matching request paths.
Render Services - Headers API is one of 26 APIs that Render publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
This API exposes 3 JSON Schema definitions.
Tagged areas include Services - Headers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, a JSON-LD context, and 3 JSON Schemas.
This API exposes 4 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.0.2, at version 1.0.0.
Requests are made against a single base URL, https://api.render.com/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Render Services - Headers API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
By default, every request must be authenticated.
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Use HTTP headers to inject response headers in static site responses. You can also use wildcards like /path/ to add headers to responses for all matching request paths.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are header (4 properties), headerInput (3 properties), error (2 properties), headerWithCursor (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Render 12
Other APIs Render publishes across the network.