Make your first request
- Create a Sandbox API key with the access your integration needs.
- Verify API access from your integration’s network.
- Try a read operation before submitting service actions. See Sandbox Mode for simulated behavior and limitations.
Base URL and requests
/services, to this URL. For example:
- Use HTTPS and Bearer authentication on every request.
- Send
Content-Type: application/jsonfor JSON request bodies. - Put filters and pagination in the query string, and public service numbers or request IDs in the path.
- Use
GETfor reads andPOSTfor the actions specified in the reference.
Pagination
List endpoints takelimit (rows per response, default 20, maximum 100) and offset (matching rows to skip, default 0). The API changes a limit above 100 to 100, a negative limit to 1, a missing, 0, or non-numeric limit to 20, and a negative offset to 0.
The pagination object in the response maps these values to pages: perPage is limit, page is floor(offset / limit) + 1, total is the number of matching rows, and totalPages is ceil(total / limit).
You are on the last page when
page is equal to or greater than totalPages. When total is 0, totalPages is 0 and data is empty. Use an offset that is a multiple of limit to get predictable page numbers.
Responses
Success responses containsuccess: true and data. List responses also include pagination:
200. Some service and request actions return 202 for processing, manual approval, or NYCServers review. Check the endpoint’s response fields to distinguish acceptance from completion.
Errors contain success: false and an error object. Read Errors and Retries for error handling, tracking accepted work, and using idempotency keys before retrying writes.
