curl -X PUT \
-H "Authorization: {******}" \
-H "Content-Type: application/json" \
-d '{"Amount": "27.00"}' \
-v \
https://api.opendental.com/api/v1/fees/2971
* Host api.opendental.com:443 was resolved.
* IPv6: (none)
* IPv4:
* Trying {IP}
* Connected to api.opendental.com (50.206.249.204) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / [blank] / UNDEF
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
* subject: CN=api.opendental.com
* start date: Nov 12 23:00:46 2024 GMT
* expire date: Dec 14 23:00:46 2025 GMT
* subjectAltName: host "api.opendental.com" matched cert's "api.opendental.com"
* issuer: C=US; ST=Arizona; L=Scottsdale; O=Starfield Technologies, Inc.; OU=http://certs.starfieldtech.com/repository/; CN=Starfield Secure Certificate Authority - G2
* SSL certificate verify ok.
* using HTTP/1.x
> PUT /api/v1/fees/2971 HTTP/1.1
> Host: api.opendental.com
> User-Agent: curl/8.7.1
> Accept: */*
> Authorization: {******}
> Content-Type: application/json
> Content-Length: 19
>
* upload completely sent off: 19 bytes
< HTTP/1.1 200 OK
< Cache-Control: no-cache
< Pragma: no-cache
< Expires: -1
< Server: Microsoft-IIS/10.0
< X-AspNet-Version: 4.0.30319
< X-Powered-By: ASP.NET
< Access-Control-Allow-Headers: *
< Date: Fri, 16 May 2025 17:58:29 GMT
< Content-Length: 0
<
* Connection #0 to host api.opendental.com left intact
Is this an API bug where a Fees PUT request returns no response?
Empty Response for PUT Fees
Re: Empty Response for PUT Fees
Hello aearl23,aearl23 wrote: ↑Fri May 16, 2025 11:05 amcurl -X PUT \
-H "Authorization: {******}" \
-H "Content-Type: application/json" \
-d '{"Amount": "27.00"}' \
-v \
https://api.opendental.com/api/v1/fees/2971
* Host api.opendental.com:443 was resolved.
* IPv6: (none)
* IPv4:
* Trying {IP}
* Connected to api.opendental.com (50.206.249.204) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 / [blank] / UNDEF
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
* subject: CN=api.opendental.com
* start date: Nov 12 23:00:46 2024 GMT
* expire date: Dec 14 23:00:46 2025 GMT
* subjectAltName: host "api.opendental.com" matched cert's "api.opendental.com"
* issuer: C=US; ST=Arizona; L=Scottsdale; O=Starfield Technologies, Inc.; OU=http://certs.starfieldtech.com/repository/; CN=Starfield Secure Certificate Authority - G2
* SSL certificate verify ok.
* using HTTP/1.x
> PUT /api/v1/fees/2971 HTTP/1.1
> Host: api.opendental.com
> User-Agent: curl/8.7.1
> Accept: */*
> Authorization: {******}
> Content-Type: application/json
> Content-Length: 19
>
* upload completely sent off: 19 bytes
< HTTP/1.1 200 OK
< Cache-Control: no-cache
< Pragma: no-cache
< Expires: -1
< Server: Microsoft-IIS/10.0
< X-AspNet-Version: 4.0.30319
< X-Powered-By: ASP.NET
< Access-Control-Allow-Headers: *
< Date: Fri, 16 May 2025 17:58:29 GMT
< Content-Length: 0
<
* Connection #0 to host api.opendental.com left intact
Is this an API bug where a Fees PUT request returns no response?
This is expected behavior. The PUT fees endpoint is used to update the Amount of an existing fee. If the value you send is identical to the current one (in this case, "27.00"), no actual update occurs, so the API returns a 200 OK with an empty response body.
This doesn't indicate an error; it's just letting you know the request was valid, but no changes were made.
Thanks!