Understanding Our Support Scope: We'd Love to Help, But There Are Limits!

We genuinely want to help you succeed with our API – that's why we're here! However, as a headless service provider, we've learned that setting some friendly boundaries helps us give you the best possible support while keeping things sustainable for everyone. Think of this as our "helpful but realistic" guide to what we can tackle together.

What We're Happy to Help With

API Technical Assistance

We love diving into the technical stuff! We're great at:

• Parameter guidance: "Oh, you need that parameter – here's exactly where to find it!"
• API request examples: Showing you sample requests when you have a specific technical goal in mind
• Documentation clarification: Making our docs clearer when something's genuinely confusing
• Bug hunting: Investigating real API issues (we actually enjoy this detective work!)

Example of Appropriate Support Requests

✅ "How do I find properties listed in the past 24 hours using your API?"

✅ "I'm getting a 400 error when using the standardStatus parameter - here's my request..."

✅ "Can you clarify what the radius parameter accepts as valid input?"

Where We Have to Draw the Line (Sorry!)

Design and Creative Decisions

Much as we'd love to be your design consultants, we just can't be your:

• UI/UX brainstorming partners
• Feature idea generators
• User experience gurus
• Creative visionaries

Why? Because you're the expert on your users and your vision – plus, if we designed everyone's apps, they'd all look the same!

Custom Development Work

We're flattered when you think we could build your app for you, but we have to resist the temptation to:

• Write your application code
• Debug your custom implementations
• Become your programming tutors
• Turn into a development agency

The reality? We'd go out of business pretty quickly if we coded everyone's projects for free!

Example of Requests Outside Our Scope

❌ "Can you recommend some things to make our site more user-friendly?"

❌ "What's the best way to display search results to our users?"

❌ "Can you provide the code to implement this feature?"

How to Be Our Favorite Subscriber (And Get Faster Help!)

Be a Documentation Detective First

We know reading docs isn't always fun, but we promise it'll save you time:

1. Check the API reference – seriously, it's pretty comprehensive!
2. Browse our help center for step-by-step guides
3. Try our AI helpdesk assistant – it's surprisingly good at finding answers
4. Try our developer playgrounds - you can even fork them on GitHub
5. Give it a genuine attempt before reaching out

When You Do Contact Us, Help Us Help You

Make our day by:

• Following our context guidelines – detailed reports = faster solutions
• Being specific about your technical goals
• Including the good stuff: endpoints, parameters, error messages, what you tried
• Communicating clearly (Google Translate is your friend if needed!)

We Assume You're Pretty Technical

Since we're a headless service, we're betting that you:

• Know your way around APIs and HTTP requests
• Can read technical docs without crying
• Have the skills to build something awesome
• Take ownership of your implementation (because it's your vision!)

Why We're Not Just Being Difficult

These boundaries aren't us being mean – they actually help us:

• Give you better support on the technical stuff we're actually good at
• Keep our docs and tools top-notch instead of spread too thin
• Stay fair to everyone – nobody wants to wait behind someone asking us to design their entire app
• Keep the service affordable for everyone (unlimited consulting would get expensive fast!)

The truth is: you're the creative genius here. We provide the rock-solid API foundation, and you bring the vision, innovation, and technical chops to build something incredible. It's actually a pretty great partnership when it works right!

The Sweet Spot: How to Get Amazing Support

Want to make both our days better?

1. Be resourceful – check those docs like the treasure maps they are
2. Be specific – "how do I X?" beats "what should I do?" every time
3. Be prepared – context is king (and screenshots are pretty great too)
4. Be realistic – we're API experts, not mind readers or app designers

When you follow this approach, we can usually turn around answers super quickly, and you'll spend more time building cool stuff instead of waiting on support tickets. Win-win!

Updated on: 07/08/2025