Skip to main content
GET
Check Name Availability

Overview

Check if a desired ZKS ID name is available before attempting to mint. This endpoint validates the name format and checks if it’s already taken. If unavailable, it provides alternative suggestions.
Always check availability before minting to avoid errors and provide a better user experience with name suggestions.

Parameters

string
required
The desired ZKS ID name to check (without .zks suffix). Must be 3-32 characters, lowercase letters, numbers, and hyphens only.

Response

boolean
Indicates if the request was successful
string
The name that was checked
boolean
Whether the name is available for minting
boolean
Whether the name meets format requirements
string
If unavailable or invalid, explains why
array
Array of alternative name suggestions if the requested name is unavailable

Examples

Response Examples

Available Name

Unavailable Name (Taken)

Invalid Name Format

Invalid Characters

Validation Rules

Valid Name Requirements

  • Length: 3-32 characters (excluding .zks suffix)
  • Characters: Lowercase letters (a-z), numbers (0-9), hyphens (-)
  • Start/End: Must start and end with a letter or number (not hyphen)
  • No consecutive hyphens: Cannot have multiple hyphens in a row

Examples

Use Cases

1. Real-time Name Validation

Check availability as user types:

2. Name Suggestion Flow

Provide alternatives if name is taken:

3. Batch Name Checking

Check multiple names at once:

4. Smart Suggestions

Generate intelligent name suggestions:

Best Practices

1. Debounce API Calls

Avoid excessive API calls during typing:

2. Cache Results

Cache availability checks to reduce API calls:

3. Validate Locally First

Check format locally before API call:

4. Show Real-time Feedback

Provide immediate visual feedback:

Error Responses

Integration Example

Complete name selection flow:

Troubleshooting

”Too many requests”

Cause: Exceeded rate limits for availability checks. Solution:
  • Implement debouncing (wait 500ms after user stops typing)
  • Cache results locally
  • Reduce frequency of checks

”Invalid name format”

Cause: Name doesn’t meet validation requirements. Solution:
  • Validate locally before API call
  • Show clear validation rules to users
  • Provide real-time format feedback

Rate Limits

Name availability checks are subject to rate limits:
  • Free tier: 100 checks per minute
  • Starter tier: 500 checks per minute
  • Professional tier: 2,000 checks per minute
  • Enterprise tier: Custom limits
Implement debouncing and caching to stay within limits.