Apifreaks Rust SDK

The Apifreaks Rust library provides convenient access to the Apifreaks APIs from Rust.

Table of Contents

• Installation
• Reference
• Usage
• Environments
• Errors
• Request Types
• Advanced
  • Retries
  • Timeouts
  • Additional Headers
  • Additional Query String Parameters
• Contributing

Installation

Add this to your Cargo.toml:

[dependencies]
apifreaks = "1.0.3"

Or install via cargo:

cargo add apifreaks

Reference

A full reference for this library is available here.

Usage

Instantiate and use the client with the following:

use apifreaks::prelude::*;

#[tokio::main]
async fn main() {
    let config = ClientConfig {
        ..Default::default()
    };
    let client = ApiFreaks::new(config).expect("Failed to build client");
    client
        .bulk_geolocation_lookup(
            &BulkGeolocationLookupRequest {
                api_key: "apiKey".to_string(),
                ips: vec!["ips".to_string()],
                format: None,
                lang: None,
                fields: None,
                excludes: None,
                include: None,
            },
            None,
        )
        .await;
}

Environments

This SDK allows you to configure different environments for API requests.

use apifreaks::prelude::{*};

let config = ClientConfig {
    base_url: Environment::Default.url().to_string(),
    ..Default::default()
};
let client = Client::new(config).expect("Failed to build client");

Errors

When the API returns a non-success status code (4xx or 5xx response), an error will be returned.

match client.bulk_geolocation_lookup(None)?.await {
    Ok(response) => {
        println!("Success: {:?}", response);
    },
    Err(ApiError::HTTP { status, message }) => {
        println!("API Error {}: {:?}", status, message);
    },
    Err(e) => {
        println!("Other error: {:?}", e);
    }
}

Request Types

The SDK exports all request types as Rust structs. Simply import them from the crate to access them:

use apifreaks::prelude::{*};

let request = BulkGeolocationLookupRequest {
    ...
};

Advanced

Retries

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).

A request is deemed retryable when any of the following HTTP status codes is returned:

• 408 (Timeout)
• 429 (Too Many Requests)
• 5XX (Internal Server Error)

The retryStatusCodes configuration controls which 5XX status codes are retried:

• legacy (default): Retries 408, 429, and all >= 500
• recommended: Retries 408, 429, 502, 503, 504 only (excludes 500 Internal Server Error to avoid retrying non-idempotent failures)

Use the max_retries method to configure this behavior.

let response = client.bulk_geolocation_lookup(
    Some(RequestOptions::new().max_retries(3))
)?.await;

Timeouts

The SDK defaults to a 30 second timeout. Use the timeout method to configure this behavior.

let response = client.bulk_geolocation_lookup(
    Some(RequestOptions::new().timeout_seconds(30))
)?.await;

Additional Headers

You can add custom headers to requests using RequestOptions.

let response = client.bulk_geolocation_lookup(
    Some(
        RequestOptions::new()
            .additional_header("X-Custom-Header", "custom-value")
            .additional_header("X-Another-Header", "another-value")
    )
)?
.await;

Additional Query String Parameters

You can add custom query parameters to requests using RequestOptions.

let response = client.bulk_geolocation_lookup(
    Some(
        RequestOptions::new()
            .additional_query_param("filter", "active")
            .additional_query_param("sort", "desc")
    )
)?
.await;

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!

On the other hand, contributions to the README are always very welcome!