Myinstants APImyinstants.com ↗
Search the Myinstants catalog via API. Get sound button titles, slugs, MP3 file URLs, and page URLs for up to 72 results per request.
What is the Myinstants API?
The Myinstants API exposes 1 endpoint — search_sounds — that queries the Myinstants sound-button catalog by keyword and returns up to 72 matching results per page, each carrying 4 fields: the sound's display title, its site slug, a direct MP3 file URL, and the canonical page URL. It is the straightforward way to integrate Myinstants content into bots, apps, or audio tooling without maintaining your own catalog index.
curl -X GET 'https://api.parse.bot/scraper/364abd0d-1fce-4be0-872c-2d1c718699cd/search_sounds?query=risada' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace myinstants-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: search Myinstants sound buttons and browse results."""
from parse_apis.myinstants_com_api import Myinstants, InputFormatInvalid
client = Myinstants()
# Search for sounds matching a keyword, capped at 10 total items.
for sound in client.sounds.search(query="risada", limit=10):
print(sound.title, sound.mp3_url)
# Drill into the first result of a different search.
hit = client.sounds.search(query="airhorn", limit=1).first()
if hit is not None:
print(hit.title, hit.slug, hit.page_url)
# Handle an invalid query gracefully.
try:
client.sounds.search(query="", limit=1).first()
except InputFormatInvalid as e:
print("Bad query:", e.message)
print("exercised: sounds.search")
Searches Myinstants sounds by keyword and returns one page of 72 matching sound buttons (two consecutive upstream result pages combined), each with title, slug, MP3 file URL and the sound's page URL, in the site's relevance order. Paging is controlled by `page` (1-based; omitted = 1). `has_more` is true when the page was completely filled, so the following page may occasionally be empty when the result set ends exactly on a page boundary. A keyword with no matches, or a page past the end of the results, returns a success with an empty `items` list and `count` 0.
| Param | Type | Description |
|---|---|---|
| page | integer | 1-based result page of 72 items. |
| queryrequired | string | Free-text search keyword matched against sound titles (e.g. a word such as a laugh or meme name). |
{
"type": "object",
"fields": {
"page": "integer page number returned",
"count": "integer number of items in this page",
"items": "array of sound records: title (display name), slug (site identifier of the sound), mp3_url (absolute URL of the MP3 file), page_url (absolute URL of the sound's page)",
"query": "the keyword that was searched",
"has_more": "boolean, true when this page was full and a next page should be requested",
"page_size": "integer, always 72 (maximum items per page)"
},
"sample": {
"data": {
"page": 1,
"count": 72,
"items": [
{
"slug": "risada-carlos-alberto-nobrega",
"title": "Risada Carlos Alberto Nobrega",
"mp3_url": "https://www.myinstants.com/media/sounds/risada_carlos_alberto_mp3cut.mp3",
"page_url": "https://www.myinstants.com/pt/instant/risada-carlos-alberto-nobrega/"
},
{
"slug": "risadinha-de-ladrao-8117",
"title": "Risadinha de ladrão",
"mp3_url": "https://www.myinstants.com/media/sounds/sabe-porque-as-meninas-dao-maior-valor-na-risada-de-ladrao-mp3cut.mp3",
"page_url": "https://www.myinstants.com/pt/instant/risadinha-de-ladrao-8117/"
}
],
"query": "risada",
"has_more": true,
"page_size": 72
},
"status": "success"
}
}About the Myinstants API
What the API Returns
The single search_sounds endpoint accepts a required query string and an optional 1-based page integer. Each response includes the query echoed back, the page number returned, a count of items on that page, a page_size (always 72), and a has_more boolean indicating whether additional pages exist. The items array contains one object per sound with four fields: title (the display name shown on the button), slug (the site's unique identifier for that sound), mp3_url (an absolute URL pointing directly to the audio file), and page_url (the canonical URL of the sound's page on Myinstants).
Pagination
Results are sorted in the site's own relevance order. Each page holds a maximum of 72 items. When has_more is true, increment page by 1 and repeat the request to retrieve the next batch. When has_more is false or count is less than 72, you have reached the end of the result set. There is no cursor or offset parameter — pagination is strictly page-number based.
Working with the MP3 URLs
The mp3_url field is an absolute URL you can stream or download directly. Combined with slug, it gives you enough to construct deep links or cache audio locally. The slug is stable and can serve as a deduplication key if you are aggregating results across multiple queries.
The Myinstants API is a managed, monitored endpoint for myinstants.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when myinstants.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official myinstants.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Discord or Slack bot that plays sound effects by keyword using the returned
mp3_url. - Index the Myinstants catalog for a custom audio search engine, using
slugas a stable deduplication key. - Power a soundboard web app that lets users search meme sounds and trigger playback via
mp3_url. - Automate content discovery by paging through results with
has_moreto collect all sounds matching a theme. - Enrich a meme database by mapping
titleandpage_urlto external metadata for each sound button. - Feed a recommendation engine with sound titles and slugs to suggest related audio clips to users.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Myinstants have an official developer API?+
What does the `search_sounds` endpoint return beyond the audio file URL?+
items array returns four fields: title (the display name of the sound button), slug (the site's unique identifier), mp3_url (direct link to the MP3 file), and page_url (the canonical page for that sound). The response also includes query, page, count, page_size, and has_more at the top level for pagination management.Can I retrieve trending, newest, or category-filtered sounds rather than keyword search results?+
Is there a limit to how many pages I can retrieve for a given query?+
has_more boolean to determine when the result set is exhausted. For very broad queries the result set may be large, so check has_more after each page rather than assuming a fixed total.Does the API return play counts, likes, or uploader information for each sound?+
title, slug, mp3_url, and page_url per sound — engagement metrics and uploader details are not included. You can fork it on Parse and revise it to add those fields if they are available on the sound's page.