> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/docs/api/v1/klarna/category/guide/get>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/api/v1/klarna/category/guide/get.mdx>

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** <https://www.socialfetch.dev/openapi.json>

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 1112 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# Get Klarna category guide (https://www.socialfetch.dev/docs/api/v1/klarna/category/guide/get)

## Summary

Get a Klarna category's buying guide: its description, frequently asked questions and the things to consider before buying, in the country's language.

**Tags:** `Klarna`

## HTTP

- **Method:** GET
- **Path:** `/v1/klarna/category/guide`
- **Base URL:** `https://api.socialfetch.dev`

## Capability summary

- **SDK mapping:** `client.klarna.getCategoryGuide({ category: "cl52" })`
- **Pagination:** none
- **Business outcome field:** `data.lookupStatus` with values `found`, `not_found`

## Credits

- 1 credit
- Failed requests are free
- Found, empty and not-found answers are all charged

## Authentication

- **`x-api-key`**: API key (`sfk_...`)

## Parameters

### `category` (query)

- **Required:** yes
- **Constraints:** type `string`; minLength: 1; maxLength: 500
- **Description:** Klarna product-list category: `cl52` (Game Consoles) or its page URL (`https://www.klarna.com/us/shopping/cl/cl52/Game-Consoles/`). A URL's country is used when `country` is not given.

### `country` (query)

- **Required:** no
- **Constraints:** type `string`
- **Description:** Two-letter country code of the Klarna shopping site, e.g. `US`, `GB`, `DE` or `SE`. Default: `US`. Prices are in that country's currency.

## Responses (status codes)

- **200**: A Klarna category's buying guide: description, FAQ and tips.
- **400**: Invalid request
- **401**: Missing or invalid API key
- **402**: Insufficient credits
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed.
- **503**: Service temporarily unavailable; safe to retry with backoff.

## Response body (200)

A Klarna category's buying guide: description, FAQ and tips.

### Field outline

- **data** (required) — type `object`. Endpoint-specific response payload.
  - **lookupStatus** (required) — type `string`; enum: found, not_found. `not_found` when Klarna has no category with this id in this country; a category without guide text is `found` with nulls.
  - **categoryId** (required) — type `string`. The category asked for, e.g. `cl52`.
  - **market** (required) — type `object`. The Klarna shopping site the answer is from.
    - **country** (required) — type `string`. Two-letter country code, e.g. `US`.
    - **siteUrl** (required) — type `string`. The country's Klarna shopping site, e.g. `https://www.klarna.com/us/shopping/`.
  - **description** (required) — type `object`; nullable. The category's buying guide text; null when the site has none in this country.
    - **intro** (required) — type `string`; nullable. The text above the category's products, in Markdown.
    - **body** (required) — type `string`; nullable. The longer guide below the products, in Markdown, with its own headings.
  - **faq** (required) — type `object`; nullable. Frequently asked questions; null when the site has none.
    - **title** (required) — type `string`; nullable. Heading the site shows.
    - **questions** (required) — type `array`. The questions.
      - _items:_
  - **buyingTips** (required) — type `object`; nullable. Things to consider before buying; null when the site has none.
    - **title** (required) — type `string`; nullable. Heading, e.g. `Game Consoles: 3 things to consider before buying`.
    - **description** (required) — type `string`; nullable. Text under it.
    - **tips** (required) — type `array`. The tips.
      - _items:_
- **meta** (required) — type `object`. Metadata describing the request and billing outcome.
  - **requestId** (required) — type `string`; minLength: 1. Unique request identifier for tracing this API call.
  - **creditsCharged** (required) — type `integer`; minimum: 0. Credits charged for this request.
  - **version** (required) — type `string`; enum: v1. Public API version that served the response.
  - **stale** (optional) — type `boolean`; enum: true. Present, and `true`, only when the source couldn't be reached and this is the last good answer for the same request instead, up to 24 hours old. Absent on every live answer.
  - **fetchedAt** (optional) — type `string`. When a stale answer (`stale: true`) was originally fetched (ISO 8601, UTC). Absent on every live answer.

### Example JSON (found)

```json
{
  "data": {
    "lookupStatus": "found",
    "categoryId": "cl52",
    "market": {
      "country": "US",
      "siteUrl": "https://www.klarna.com/us/shopping/"
    },
    "description": {
      "intro": "Looking for the right game console? Klarna helps you find the best fit. We list a wide range of game consoles from popular brands and retailers. Use our category filters to easily narrow down your choices—whether it's based on brand, price, or features like storage capacity and graphics quality. Compare prices and mod…",
      "body": "## Level up your gaming experience\n\nGaming consoles offer a wide array of entertainment options, from immersive gameplay to streaming your favorite shows. Klarna helps you find the right console by allowing you to compare prices, read user reviews, and explore price history. Whether you're a seasoned gamer or just sta…"
    },
    "faq": {
      "title": "Game Consoles",
      "questions": [
        {
          "question": "What are the best game consoles available in 2023?",
          "answer": "Game consoles are devices designed for playing video games on a television or monitor. In 2023, popular options include PlayStation 5, Xbox Series X, and Nintendo Switch OLED. Each offers unique features like exclusive games, performance capabilities, and portability. Consider your gaming preferences and budget when c…"
        }
      ]
    },
    "buyingTips": {
      "title": "Game Consoles: 3 things to consider before buying",
      "description": null,
      "tips": [
        {
          "title": "Consider your gaming preferences",
          "text": "When choosing a game console, it's essential to consider the types of games you enjoy. Are you a fan of exclusive titles like *The Legend of Zelda* or *Uncharted*? If so, you might prefer consoles like the Nintendo Switch or PlayStation. For those who love multiplayer experiences and online gaming, the Xbox Series X c…"
        }
      ]
    }
  },
  "meta": {
    "requestId": "req_01example_klarna_category_guide",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Machine-readable error codes

When an error JSON body is returned, it may include one of these `error.code` values (derived from the OpenAPI schemas for this operation; additional codes may exist at runtime):

- `bad_request`

## Error handling & retries

Interpret HTTP status codes using the descriptions below. Do not assume a JSON body unless the OpenAPI schema defines one for that status.

- **400**: Invalid request **Retry:** Fix the request; retrying the same invalid payload will not help.
- **401**: Missing or invalid API key **Retry:** Fix the API key first; retrying without changes will not help.
- **402**: Insufficient credits **Retry:** Do not retry without resolving billing/credits (retrying the same request will not help).
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed. **Retry:** May be transient; a few retries with backoff are reasonable.
- **503**: Service temporarily unavailable; safe to retry with backoff. **Retry:** Usually safe to retry with exponential backoff and jitter.

### Suggested client defaults

- Send the API key using the `x-api-key` header on every request.
- On `503` (and sometimes `502`), retry with backoff; cap retries and surface a clear error to the user.
- On `402`, surface an actionable billing message rather than blind retries.

## Examples

### TypeScript SDK

```typescript
import { SocialFetchClient } from "@socialfetch/sdk";

const client = new SocialFetchClient({
  apiKey: process.env.SOCIALFETCH_API_KEY!,
});

const result = await client.klarna.getCategoryGuide({
  category: "cl52",
});

if (!result.ok) {
  console.error(result.error);
} else {
  console.log(result.value.data);
}
```

### Node.js

```javascript
const response = await fetch(
  "https://api.socialfetch.dev/v1/klarna/category/guide?category=cl52",
  {
    headers: {
      "x-api-key": "YOUR_API_KEY"
    }
  }
);

const data = await response.json();
console.log(data);
```

### cURL

```bash
curl "https://api.socialfetch.dev/v1/klarna/category/guide?category=cl52" \
  -H "x-api-key: YOUR_API_KEY"
```

### Python

```python
import requests

response = requests.get(
    "https://api.socialfetch.dev/v1/klarna/category/guide?category=cl52",
    headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()
print(data)
```