ureq

Send blocking HTTP requests with JSON support in Rust.

28|6|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/johnlindquist/script-kit-next --skill ureq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ureq
Source: https://github.com/johnlindquist/script-kit-next/tree/main/.opencode/skill/ureq
Command: npx skills add https://github.com/johnlindquist/script-kit-next --skill ureq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a straightforward, blocking HTTP client for making web requests in Rust, ideal for scenarios where simplicity and minimal dependencies are preferred over asynchronous operations.

Core Features & Use Cases

  • HTTP Requests: Easily send GET, POST, and other HTTP requests.
  • JSON Handling: Send and receive JSON data with built-in support.
  • Error Management: Robust error handling for network issues, status codes, and timeouts.
  • Use Case: Integrate with external APIs for data retrieval or submission within a Rust application without the complexity of async runtimes.

Quick Start

Use the ureq skill to make a GET request to 'https://api.example.com/data' and print the response status.

Frequently Asked Questions about ureq

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a blocking HTTP request in Rust without an async runtime?

To make a blocking HTTP request in Rust, you can use this Skill to send direct web requests for CLI tools or backend services where asynchronous programming is not required. It facilitates GET, POST, and other HTTP methods without async complexity.

Can I handle JSON serialization and custom headers with a simple Rust HTTP client?

Yes, this simple Rust HTTP client supports JSON serialization and deserialization alongside custom headers. You can send and receive JSON data directly while configuring headers for robust network communication.

When should I use a blocking HTTP client instead of an asynchronous one in Rust?

You should use a blocking HTTP client in Rust when simplicity and minimal dependencies are preferred over asynchronous operations. It is ideal for CLI tools and backend services that do not require concurrent async runtimes.

How do I manage network errors and timeouts for Rust API interactions?

You can manage network errors and timeouts using the configurable timeout and error management features of this Rust HTTP client. It provides robust handling for network issues and status codes during API interactions.

Does this minimal dependency Rust HTTP client support configurable timeouts?

Yes, this minimal dependency Rust HTTP client supports configurable timeouts. It is designed to offer robust network communication by allowing you to set timeout limits for your blocking web requests.