Contracts
Delete a contract
Starts deleting one contract owned by the authenticated team and answers 202 with no body once the deletion is queued. A contract that is still processing answers validation_failed. Contracts on other teams or sub-teams, or above the token's classification ceiling, are reported as not found. For example, DELETE /v1/contracts/{id} with the header Authorization: Bearer <token> answers 202 with an empty body.
deletehttps://api.govdash.us/v1/contracts/{id}
Authorization
Your API key as a bearer token, for example Bearer gd_live_....
See Authentication for how to create a key.
Path parameters
Contract identifier.
Headers
The dated API version this request is written against. Responses keep that version's shape after newer versions ship.
One of:
Response
202<No Content> The response has no body.
Errors
Every error returns a stable error.code to branch on and an error.message that says what went wrong, like the examples below. See Errors for how to handle each one.
A path or query parameter is malformed.
Invalid request path parameters: Expected a non-empty string
The key's service account doesn't have the permission this needs, or your team's access has ended.
You do not have permission to perform this action.
The record doesn't exist, belongs to another team, or is above the key's classification.
The requested resource was not found.
The request is well formed, but GovDash won't make this change. The message says why, when it can.
The request failed validation.
You sent too many requests. Wait the seconds in the retry-after header, then retry.
This access token exceeded its write rate limit.
Something went wrong on GovDash's side, usually a bug. Retry with backoff, and check before retrying a create.
An unexpected error occurred.
GovDash is briefly unavailable and didn't run the request. Retry after retry-after.
The service is temporarily unavailable. Try again later.