Search · Shortcodes · Emoji data

Emoji API

Put the right emoji
in your app.

Find emoji for your chat, editor or picker by character, shortcode or name.

Try it

Character, :shortcode:, name, or Unicode code.

Options

Missing translations keep the English name. The character and shortcode stay the same.

Loading the picker.

Use arrow keys to move between emoji. Press Enter or Space to select.

Many tasks. One API.

Emoji data.
Ready for your app.

Look up emoji, search the catalog and add Unicode detail. Complete JSON for every request.

One record, ready to use.

Resolve a name to its character, shortcodes and category.

Request

curl "https://api.parseapi.com/emoji/rocket" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Parse-Version: 2.0.0"

Example response

JSON200 OK
{
  "emoji": "🚀",
  "name": "Rocket",
  "shortcodes": [":rocket:", "rocket"],
  "category": "Travel & Places"
}
Explore every response field

Response fields

emojistring
Emoji character
namestring or null
Official name
shortcodesarray
Shortcodes with and without colons
categorystring or null
Category

Deep fields

deep.codepointsarray
Unicode codepoints (U+…)
deep.hexstring or null
Hex form
deep.statusstring or null
Qualification status
deep.versionstring or null
Emoji version that introduced this sequence
deep.keywordsarray
Related keywords
deep.skinsarray
Skin-tone variants (when available)
deep.subcategorystring or null
Emoji subgroup, such as hand-fingers-closed
deep.basestring
Canonical parent of a variant, omitted when there is no parent
deep.variantsarray
Additional mixed-tone choices beyond skins. Each has emoji and tones
deep.artworkobject
SVG/PNG URLs keyed by style, e.g. artwork.openmoji.svg and artwork.openmoji.png["72"]. Missing styles and formats are omitted. Shared credits, licenses and notices are in /emoji/metadata

Meet people where they type

Different inputs.
One emoji.

Someone pastes a character. Your bot gets a shortcode. Your editor has a name. Resolve them to the same record and keep your product moving.

Search translated names and keywords in their language. Keep characters and shortcodes consistent.

🔥
:fire:
Fire
U+1F525

Fire

Character, name, shortcodes and category.

The details belong together

Keep the whole emoji.

A family, a flag or a handshake can contain several Unicode characters. Get the complete sequence, with the tone choices that belong to it.

A whole family
One complete joined sequence.
Every tone together
Mixed-tone handshake variants.
One flag
A country flag, kept intact.

Add deep=true for Unicode detail, parent records and complete skin-tone families. Included in the same request.

Inside the conversation

Find the emoji
in the message.

Count reactions, group repeated emoji and find their positions without splitting families or skin tones.

Find emoji in text

Loading the text parser…

Official at the source

Unicode at the core.

Use the official Unicode emoji catalog. Return real characters for chat, editors and reactions. Let each device give them its familiar look.

🚀
Rocket · U+1F680

Appearance and support depend on the device. Choose optional image artwork when you need it.

Choose image artwork

From the first request to your app

One integration.
Room to do more.

Start with an emoji lookup. Use the same API key for search and message processing, alongside the other ParseAPI products your app needs.

HTTP, SDKs and MCP

Copy a request above, then follow the reference for parameters, complete responses and errors. Choose a supported SDK or connect your agent through MCP.

  • JavaScript
  • Python
  • Go
  • Ruby
  • PHP
  • Rust
  • Swift
  • Kotlin

Before you build.

Where does the emoji catalog come from?

The catalog follows the official Unicode emoji characters and sequences. Unicode defines the character; your device supplies its familiar drawing. Optional image artwork is separate from the Unicode standard.

Can I build my own emoji picker?

Yes. Search translated names and keywords, browse categories, and load more results as people scroll. Filter by emoji version for your app. You keep your own interface.

Can I accept platform shortcodes?

Yes. Look up individual shortcodes or convert them inside a message. Choose the CLDR, GitHub, Slack or Discord preset when your integration needs one. Unknown or ambiguous codes stay unchanged during conversion, with a reason in the response.

How do families and skin tones work?

A family, flag or joined handshake is returned as a complete emoji sequence. Optional Deep detail includes the parent and available skin-tone family, including mixed tones. Text parsing counts each complete recognized sequence once per occurrence.

Can I use the artwork in my product?

Choose available original artwork from Noto, Twemoji or OpenMoji. Each source has its own license and attribution requirements. Read and retain those notices. Formats, sizes and coverage vary by source.

How are requests priced?

Emoji is included in every plan. Lookup, search, parsing and downloads use your shared API request allowance. Optional Deep detail is included in the same request. Working with downloaded data in your own application makes no API requests.

Just need a character? Use the emoji copy and paste tool.

Emoji API pricing

Start building.

Your API request allowance is shared across ParseAPI products. Emoji lookup, search and text parsing are included on every plan.

Free

Start free

Try Emoji with a free API key.

Room to grow

See plans

Choose the volume your app needs.