<!-- The markdown copy of https://oppalerts.com/docs/api/types_content_types . All pages: https://oppalerts.com/docs/llms.txt -->

[Documentation](https://oppalerts.com/docs/) / [API](https://oppalerts.com/docs/api/) / types_content_types

# types_content_types

`POST https://api.oppalerts.com/v1/types/content_types`

The catalogue of content types: every type with its label.

## What it does

The route returns the catalogue of content types. Each content type has a `content_type` value and a `label`.

Use the `content_type` values in the `type_scores` field of the index routes. Each item of `type_scores` is an object with a `content_type` and its `type_score_min`, the minimum type score, a whole number from 1 to 100. For example, `{"content_type": "blogs", "type_score_min": 60}`. The tools `campaigns_saved_opportunity_add` and `campaigns_saved_opportunity_update` take these values in `content_type` too.

This route needs no campaign. It is not an index search. It has its own daily count, and the count depends on your plan.

## Authentication

Send your token in the `Authorization` header. See [the API overview](https://oppalerts.com/docs/api/).

## Parameters

This tool has no parameters. Send an empty object.

## Strict Rules

- This tool takes no field. A field that you send is refused. The answer is HTTP 400 with the error code `bad_param`. The error names the field: "<field> is not a field of this tool."
- An error about the format of a call, such as a refused field, names the field. Its message ends with one sentence: "Read the documentation at https://oppalerts.com/docs for the correct format." Every other error has only its own sentence.

## Response fields

**`types`list**

Every content type. Each item has the two fields below.

**`types[].content_type`string**

The content type value, for example `blogs`.

**`types[].label`string**

The name of the type, for example `Blogs`.

## Example

### Request

```bash
curl -X POST https://api.oppalerts.com/v1/types/content_types \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

### Response

The full sample answer.

```json
{
  "types": [
    {
      "content_type": "blogs",
      "label": "Blogs"
    },
    {
      "content_type": "case-studies",
      "label": "Case Studies"
    }
  ]
}
```

## Errors

- `bad_param` (HTTP 400): the request has a field. This route takes no field, and the error names the field that you sent.
- `backend_error` (HTTP 502): the data server did not answer, or its answer could not be read. Try again in a few minutes.
- `daily_limit` (HTTP 429): the account used all its calls of this tool today. [account_calls_left](https://oppalerts.com/docs/api/account_calls_left) shows when the count resets.

This tool has its own daily count. Calls through the API, MCP, and the web app use this count. It is not an index search, so it does not use the shared count of the `news_` and `prospects_` tools, and the error `one_at_a_time` does not apply to it.

## Same tool in MCP

The MCP tool is `types_content_types`. See [types_content_types in MCP](https://oppalerts.com/docs/mcp/types_content_types).

## Related pages

- [Content Types in the web app](https://oppalerts.com/docs/app/content/types)
- [types_content_types in MCP](https://oppalerts.com/docs/mcp/types_content_types)
- [news_search: News Index pages, with `type_scores`](https://oppalerts.com/docs/api/news_search)
- [prospects_search: Prospect Index pages, with `type_scores`](https://oppalerts.com/docs/api/prospects_search)
- [types_opportunity_types: the catalogue of opportunity types](https://oppalerts.com/docs/mcp/types_opportunity_types)
