Skip to main content
Partner-restricted. Only returned by the Sponsorship API, which requires a sponsorship program.

​
What it means

You called POST /v1/partners/sponsorships and we got as far as reserving a seat, but the final step — switching the crew member’s DSS account to Premium — did not land against any member record. No seat has been billed to you. We credit the reserved seat back before returning this error, so your Stripe subscription is left exactly as it was. This should not happen. It means our two systems disagreed about the member’s account mid-request, which is a bug on our side rather than anything wrong with your request.
Before this error existed, that write could fail silently: you were billed £3.99/month for a member who stayed on the Free plan and kept seeing an upgrade prompt in DSS. We now fail the request, credit the seat, and alert on it.

​
What to do

  • Retry the same request. It is idempotent — a replay reuses the same seat rather than creating a second one, and the transient cause usually clears.
  • Keep your Idempotency-Key if you send one; reusing it on the retry is correct and safe.
  • Don’t mark the member as sponsored on your side until you get a 200 or 201. There is no partially-created seat to reconcile.
  • If it repeats for the same member, that member’s DSS account likely needs attention. Contact us with the instance request ID and the member’s email and we will resolve it.