API Filtering Guide
The API supports filtering by tag, country, and remote status. These filters can be combined to build highly targeted job searches. This guide covers every available filter value and strategies for getting the most out of them.
Tag Filtering
The tag parameter is the most powerful filter. It accepts a single slug per request — you cannot combine multiple tags in one call.
How Tags Work
Tags are exact-match slugs:
"solidity"works,"Solidity"or"solidity developer"does notOne tag per request — to search across multiple tags, make separate API calls
Invalid tags return empty results with no error, so always validate against the known list
Tags cover roles, technologies, languages, ecosystems, and Web3-specific concepts
Complete Tag Reference
Roles & Seniority
analyst
Data analysts, business analysts, research analysts
community-manager
Community managers, community leads
cto
CTO and senior technical leadership positions
customer-support
Support engineers, customer success roles
data-science
Data scientists, ML engineers in Web3
design
UI/UX designers, product designers, graphic designers
developer-relations
DevRel, developer advocates, ecosystem leads
devops
DevOps engineers, SRE, infrastructure roles
economy-designer
Tokenomics designers, game economy architects
entry-level
Junior roles, associate positions, no experience required
intern
Internship positions
marketing
Marketing managers, growth leads, content marketers
moderator
Discord/community moderators
non-tech
Non-technical roles across all categories
product-manager
Product managers, product owners
project-manager
Project managers, program managers
research
Researchers — cryptography, protocol, market research
sales
Sales representatives, business development
Engineering Disciplines
backend
Backend engineers, API developers, server-side roles
front-end
Frontend engineers, UI developers
full-stack
Full-stack developers
mobile
iOS, Android, React Native developers
smart-contract
Smart contract developers, auditors
cryptography
Cryptographers, zero-knowledge engineers
gaming
Game developers, metaverse engineers
security
Security engineers, auditors, pen testers
Languages & Frameworks
golang
Go/Golang developer positions
java
Java developer positions
javascript
JavaScript developer positions
node
Node.js backend positions
python
Python developer positions
react
React/React Native frontend positions
ruby
Ruby developer positions
rust
Rust developer positions (very common in Web3)
solidity
Solidity smart contract positions (Ethereum ecosystem)
typescript
TypeScript developer positions
web3js
Positions requiring Web3.js library experience
web3-py
Positions requiring Web3.py (Python) experience
Blockchain Ecosystems
bitcoin
Bitcoin-focused roles (Lightning, Ordinals, mining)
blockchain
General blockchain roles (not ecosystem-specific)
ethereum
Ethereum ecosystem roles
evm
EVM-compatible chain roles (broader than just Ethereum)
solana
Solana ecosystem roles
polkadot
Polkadot/Substrate ecosystem roles
layer-2
L2 scaling solutions (Arbitrum, Optimism, zkSync, etc.)
Web3-Specific Concepts
ai
AI/ML roles within Web3 companies
crypto
General cryptocurrency roles
dao
DAO governance, operations, tooling roles
defi
Decentralised finance roles (protocols, yield, lending)
discord
Discord-focused roles (bot dev, community)
erc
ERC standard-related development
erc-20
ERC-20 token-specific roles
ganache
Roles requiring Ganache (Truffle suite)
hardhat
Roles requiring Hardhat development framework
nft
NFT-related roles (marketplaces, collections, tooling)
open-source
Open-source focused positions
openzeppelin
Roles requiring OpenZeppelin library knowledge
pay-in-crypto
Positions that offer cryptocurrency compensation
refi
Regenerative finance roles
truffle
Roles requiring Truffle development framework
zero-knowledge
Zero-knowledge proof roles (zkSNARKs, zkSTARKs, circuits)
Country Filtering
The country parameter uses lowercase, hyphenated slugs — not country names, ISO codes, or abbreviations.
Format Rules
united-states
Yes
Correct slug format
United States
No
Must be lowercase and hyphenated
USA
No
ISO codes not supported
us
No
Two-letter codes not supported
germany
Yes
Single-word countries are just lowercase
united-kingdom
Yes
Multi-word countries use hyphens
Common Country Slugs
Tip: If you're unsure of the exact slug for a country, try the lowercase, hyphenated version of the English country name. Invalid slugs return empty results — they won't cause errors.
Remote Filtering
The remote parameter filters for remote-only positions.
There is no remote=false for on-site-only filtering. Omitting the parameter returns all positions.
Combining Filters
All filters can be used together. Each additional filter narrows the results.
Combination Examples
Filter Interaction
tag + country: Returns jobs matching the tag AND located in that country
tag + remote: Returns jobs matching the tag AND flagged as remote
country + remote: Returns remote jobs based in that country (some remote roles are geo-restricted)
All three: Most specific — e.g., remote Solidity jobs based in the US
Search Strategies
Since the API only supports one tag per request, here are practical strategies for common use cases.
"Find me a Solidity developer role"
Single call — the tag does the work:
"Find me any engineering role"
Make parallel calls across engineering tags:
Deduplicate results by job id or url on the client side.
"What jobs pay in crypto?"
"Show me non-technical Web3 jobs"
Or search specific non-tech roles:
"Find remote jobs in a specific ecosystem"
"What AI roles exist in Web3?"
"Find me entry-level positions to break into Web3"
Reducing Response Size for Browsing
When building a listing/browse UI or doing an initial scan, disable descriptions:
Then fetch full details (with descriptions) only for jobs the user clicks on. This dramatically reduces payload size and response time.
Last updated