This is an interesting hidden feature of BlueSnap's API - the inventory management. For some strange reason you cannot find it in their online documentation but it exists and it is working.
In order to create a SKU that has a specific inventory count, you need to use the create SKU API: https://developers.bluesnap.com/v8976-Extended/docs/create-sku, and add two lines to the request:
<catalog-sku xmlns="http://ws.plimus.com">
<contract-name>Seats for Show example</contract-name>
<product-id>307634</product-id>
<sku-type>DIGITAL</sku-type>
<enable-inventory-mgt>true</enable-inventory-mgt>
<inventory>1000</inventory>
<pricing-settings>
<charge-policy-type>ONE TIME PAYMENT</charge-policy-type>
<charge-policy>
<one-time-charge>
<catalog-prices>
<catalog-price>
<base-price>true</base-price>
<currency>USD</currency>
<amount>7.00</amount>
</catalog-price>
</catalog-prices>
</one-time-charge>
</charge-policy>
</pricing-settings>
</catalog-sku>
The two added lines enable-inventory-mgt and inventory dictate if the SKU will have inventory management, and if how many units the SKU has.
You can set the inventory management arbitrarily at any given time - but once the numbers are set, any purchase of this SKU will lower the inventory count, and any refund will recoup the inventory items automatically. Once you are out of inventory, no more sales will be allowed - and you can either stop there, or replenish the inventory by setting a new amount, or simply remove the inventory restriction if you so choose (using update SKU - https://developers.bluesnap.com/v8976-Extended/docs/update-sku)
In the scenario you describe, once the seats are all sold - you and your colleagues will not be able to sell any more tickets of that SKU, and you don't have to coordinate your sales - it's all done automatically.