Information
- OpenAPI version:
3.1.0
The DevSecure REST API. Every request is scoped to one workspace: the one the credential was created in.
Authentication. Send Authorization: Bearer <API key or access token>.
API keys start with devsk_. OAuth clients exchange their credentials at
POST /oauth/token for a short-lived access token (devsat_). Each operation
lists the scopes it needs.
Pagination. Lists return {"data": [...], "pagination": {"next_cursor", "has_more"}} and an X-Has-Next-Page header. Pass cursor to get the next
page; limit is 1-200 (default 50).
Errors. Every error has the same body:
{"error": {"code", "message", "request_id", "details"}}.
Rate limits. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining
and X-RateLimit-Reset; a 429 adds Retry-After.
Idempotency. Operations that create or start something accept an
Idempotency-Key header and replay the first response for 24 hours.
Rolling out. Operations marked x-devsecure-availability: rolling-out
(starting scans, requesting autofixes, PDF reports) answer
501 not_implemented until they are enabled for your deployment.
An API key, or an access token from POST /oauth/token.
Security scheme type: http
Bearer format: devsk_ API key or devsat_ access token
Client credentials grant. A token carries the client’s scopes or a subset.
Security scheme type: oauth2
Flow type: clientCredentials
Token URL: https://api.devsecure.io/oauth/token
Scopes:
Client_id and client_secret, for POST /oauth/token only.
Security scheme type: http