Overview

Fuck Off as a Service (FOAAS) is a humorous REST API that returns creative dismissal messages in various formats. It is completely free with no authentication required, making it a great practice API for learning HTTP requests. You can request responses as plain text, JSON, or HTML.

Beginner Tip

This API is perfect for practicing HTTP requests — no sign-up, no API key needed. Try requesting different content types by setting the Accept header to application/json to get a structured response.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

Use case: Integrate asks someone to fuck off data into web and mobile applications
Fuck Off as a Service data via REST API

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "status": "success",
  "data": {
    "result": "Data from Fuck Off as a Service",
    "description": "Asks someone to fuck off",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

message The main humorous dismissal message with the target name inserted
subtitle A secondary line, typically indicating who the message is from

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://www.foaas.com/off/World/Developer";
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

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

Receiving HTML instead of JSON Missing Accept: application/json header
✓ Add -H 'Accept: application/json' to your curl command or set the Accept header in your HTTP client
404 Not Found Incorrect URL path or missing required name parameters
✓ Check the FOAAS documentation at foaas.com for the correct endpoint path; most endpoints require a name and from parameter in the URL
CORS error in browser FOAAS may restrict cross-origin requests from certain origins
✓ Use the API from a server-side environment or a backend proxy rather than directly from a browser frontend

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 Social
Difficulty Beginner
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →