Delete batch in Apispot Bulk WHOIS

What this operation does

Delete batch

• DELETEChanges datalocalhost:5000/batch/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Apispot Bulk WHOIS operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Apispot Bulk WHOIS operations

• Create batch. Batch is then being processed until all providedPOST · changes data
• Query domain databaseGET · reads data
• Get your batchesGET · reads data
• WHOIS query for a domainGET · reads data
• Check domain rank (authority)GET · reads data
• Check domain availabilityGET · reads data

All 8 Apispot Bulk WHOIS operations

Questions

Can HumDay delete batch in Apispot Bulk WHOIS?

Yes. This operation is published in Apispot Bulk WHOIS's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Apispot Bulk WHOIS data?

Yes — this is a DELETE operation, so it changes something in Apispot Bulk WHOIS. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Apispot Bulk WHOIS account.

Where this came from

Read from a published API description for Apispot Bulk WHOIS at apispot.io/static/whois.yml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.