# Examples

Canonical: https://monsterapi.co/docs/examples

Each operation has an explicit example state in the [API reference](https://monsterapi.co/docs/api).
The catalog has 225 recorded success examples, two recorded refusals, 19 illustrations, and nine operations unavailable through the guest API.
The Full feed operation has documented inputs but no recorded response.
These states cover all 256 operations. They do not establish current availability.
Recorded examples show saved public responses. Illustrative examples show contract structure without claiming a recorded success.
Guest-unavailable operations show their documented refusal. A recorded `404` or `501` remains a refusal example.

## Inputs and responses

Select a public example preset to fill stable inputs. Selection does not send a request or spend credits.
Examples preserve string identifiers, integer values, and `null`. The compact preview omits raw objects and shortens lists and long text.
Open the complete sanitized sample to inspect more fields. This loads a local documentation asset, not a platform request.
Credential fields and signed URL permissions are removed from downloadable samples.

Capture dates describe historical evidence. They do not promise that an object, cursor, or media URL still works.
An operation without a reviewed public input keeps its preset disabled. It does not receive an invented identifier.
There are 234 complete static presets and 12 fresh preparation recipes.
The Facebook group-post operation has no reviewed public post ID, so its preset remains disabled.

## Prepare a fresh example

Some operations require a cursor or permission from another response. **Prepare example** shows prerequisite requests and their credit prices.
Preparation starts only after an explicit click. It keeps the public target and filters unchanged and stops after three prerequisite requests.
If a prerequisite refuses or lacks a required value, preparation stops. Send the final operation only after its inputs are ready.

## Profile to posts to comments

These recipes describe separate requests. Check each operation’s price before starting.

### Instagram

1. Request `/instagram/api/profile/nasa` and read `user.id`.
2. Request `/instagram/api/user/528817151/posts`. For another account, use its returned `user.id`.
3. Use a returned `posts[].shortcode` with `/instagram/api/media/{shortcode}` for details.
4. Request `/instagram/api/media/{shortcode}/comments` for comments without reply contents.

NASA’s ID comes from a saved public profile response. A post’s numeric ID is not its shortcode.

### YouTube

1. Request `/youtube/api/video/dQw4w9WgXcQ` and read `comments_cursor`.
2. Pass that fresh value as `cursor` to `/youtube/api/comments`.
3. For replies, use the selected comment’s `items[].replies_cursor` with the same comments operation.

Stop when the required cursor is `null`. Keep each cursor with its video and comment context.

### LinkedIn

1. Request `/linkedin/api/school?name=stanford-university`.
2. Read its numeric `id` and `next_cursor` from the same response.
3. Use both values with `/linkedin/api/organization/{id}/posts`.

A cursor older than 55 minutes receives `400`; rejection can occur sooner. Request the organization again for a fresh cursor.

### Twitch

1. Request `/twitch/api/channel/xqc` for public channel details.
2. Request `/twitch/api/stream/xqc/playback/token` for a fresh playback token and signature.
3. Pass both values to `/twitch/api/stream/xqc/playback` for the same channel.

An offline channel can return `404`. Token expiry does not establish whether the channel or recording exists.

### TikTok

1. Request `/tiktok/api/mobile/feed?count=1`.
2. Use one returned `named.posts[].id` as `itemId` with `/tiktok/api/web/item/detail`.
3. Use the publication ID as `aweme_id` with `/tiktok/api/mobile/comment/list`.
4. Use a returned comment ID and the same publication ID with `/tiktok/api/mobile/comment/reply/list`.

Web and mobile operations have separate contracts. One operation’s refusal does not prove that another source has the requested data.

## Continue and stop

Pass a cursor unchanged to its documented path with the same target and filters.
Stop on an absent or `null` cursor, or the operation’s documented terminal `404`.
Keep following an empty page only when it contains a cursor. A `429`, `500`, or `503` does not prove completeness.
Records can repeat. Use the returned object ID for deduplication when the application requires one record per object.

Exact numeric counts and rounded text have different meanings. Keep published text as text.
Relative date text does not establish an exact timestamp. Missing counts remain distinct from zero.