Discussions

Hi everyone,
I’m currently working on an integration (slope) using the Zuper API and wanted to start a discussion around best practices for structuring efficient API calls, especially as projects grow in complexity and scale.
I’m fetching and syncing data (such as jobs, customers, and related entities) between Zuper and an external system. While the API works well, I want to make sure I’m designing my calls in a way that is
Performant
Scalable
Easy to maintain
Friendly to rate limits
What’s the best way to use filters and pagination to avoid over-fetching data?
Any tips for efficiently handling large datasets (e.g., jobs or customers)?
Thanks in advance!

Pls provide pricing model for API calls and all other possible cost for us as a third party using your developer services.

is their an endpoint to get the information that a tech entered into a service task form for a given job?

I am reading the documentation for creating a property, and it says that a Property Object must be sent, and inside it there must be a property_customer property, which is an array of objects. In the example, it shows property_customer: [{customer: ‘string’}].

Hi Team,
I am trying to create a zuper job using the api call. I am getting this error even if I am passing the property "job_category" and "job_title" in the payload.

In Cursor, it is stating "No tools or prompts" when connected to the MCP server. Is it currently down?

When using the GET All Properties endpoint, we are hoping to filter on multiple custom fields in a single call using filter.custom_field. Is this possible?

FYI, the Update Quote API reference 'Try It' tool is not using the 'estimate_uid' that I put in the form.

Hi Zuper team,