I was going out of my mind.
https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/bill#delete-a-bill
says
POST /v3/company/<realmID>/bill?operation=delete
Now, I've already implemented invoice#send which says
```
POST (Using email address supplied in Invoice.BillEmail.EmailAddress) /v3/company/<realmID>/invoice/<invoiceId>/send
POST(Specifying an explicit email address) /v3/company/<realmID>/invoice/<invoiceId>/send?sendTo=<emailAddr>
Content type: application/octet-stream
```
and I specified the Accept header as 'application/json;charset=UTF-8'. Been working for over a year just fine.
I was also implementing invoice#void which specified a content type as well
https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/invoice#void-an-invo...
```
POST /v3/company/<realmID>/invoice?operation=void
Content type: application/json
```
I implemented bill#delete using the same accept header ('application/json;charset=UTF-8'), and even though it didn't specify a content type, I assumed it was like invoice#void which specified application/json, which is what I'm posting per the docs.
First I get
>"Operation Could not find resource for relative : /v3/company/realmID/bill of full path: https://c10.qbo.intuit.com/qbo10/v3/company/realmID/bill?minorversion=12&operation=delete is not supported.
> ValidationFault
> error code 500
Ok, maybe it's being overly strict about the minor version in the url params.
Nope
>"Operation Could not find resource for relative : /v3/company/realmID/bill of full path: https://c10.qbo.intuit.com/qbo10/v3/company/realmID/bill?operation=delete is not supported.
> ValidationFault
> error code 500
Ah, ok, the docs don't specify headers, let's remove 'em all
>"Operation Cannot consume content type is not supported.is not supported.
> ValidationFault
> error code 500
Ok, let's just use the 'Content-Type' header and no 'Accept'
and.. it worked.
So, here are the bugs
1. The bill docs don't specify the content-type header
2. The bill API rejects a valid request when it sees the request 'Accept' has application/json, which is nonsense for so many reasons, and now I'm getting XML back! Maybe you'd prefer a plain old 'Accept: 'application/json''? I just tested it in the sandbox, and yep, 'Accept: application/json' returns JSON, but not with the charset extension
