HelloSalut API

Beginner's Pick Geocoding / No Auth Required Beginner HTTPS
Free to Use Varies (check documentation)

Overview

HelloSalut is a simple, free API that returns a greeting translation based on the user's IP address or a specified language code. It is great for personalizing web app welcome messages to match a visitor's locale. No API key is required — just make a GET request.

Beginner Tip

Pass a two-letter language code (like "fr" for French or "de" for German) to get a greeting in that language, or omit it to auto-detect based on the caller's IP. This is a great first API to practice with because it requires no authentication.

Available Data

translated text
source language
target language
confidence score

Example Response

JSON Response
{
  "translatedText": "Bonjour le monde",
  "detectedSourceLanguage": "en",
  "targetLanguage": "fr"
}

Field Reference

code The language code that was used for the greeting lookup.
hello The translated greeting word in the requested language.

Implementation Example

Request
const url = "https://fourtonfish.com/project/hellosalut-api/";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Empty or unexpected response The language code provided is not supported by the API.
Use a standard ISO 639-1 two-letter language code such as "en", "fr", "de", or "ja".
CORS error in browser The API may not support cross-origin requests from all domains.
Make the request from your server-side code instead of directly from a browser script.
404 Not Found Incorrect API URL or endpoint path.
Double-check the URL. The correct endpoint is https://hellosalut.stefanbohacek.dev/?lang=LANGCODE.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Geocoding
Difficulty Beginner
Verified: 2026-04-07

Similar APIs

View All →