docs(openapi): add 402 response to Actor execution endpoints#2412
docs(openapi): add 402 response to Actor execution endpoints#2412
Conversation
Actor execution endpoints now return 402 Payment Required with X402 payment info when a request has no auth token and no payment headers. See apify/apify-core#26917. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Preview for this PR was built for commit |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The |
|
Preview for this PR was built for commit |
|
A PR to update the Python client models has been created: apify/apify-client-python#711 This was automatically triggered by OpenAPI specification changes in this PR. |
| content: | ||
| application/json: | ||
| schema: | ||
| $ref: ../schemas/common/ErrorResponse.yaml |
There was a problem hiding this comment.
You should use allOf here to make sure that type is set to the one true allowed value
There was a problem hiding this comment.
It's following the same pattern as all other responses 🤔 Should it be changed everywhere? If so, then I'd do it in a separate PR.
There was a problem hiding this comment.
Well, in https://github.com/apify/apify-docs/blob/3b28c7aeebbb3f77c51a6a89f7fc017e7a689eac/apify-api/openapi/components/schemas/common/errors/ActorErrors.yaml, it is correct already... I thought that PR changed every error response. @vdusek can you share you opinion please?
Updates API schema to match changes from apify/apify-core#26917: unauthenticated Actor execution requests now return 402 with X402 payment info instead of 401.
I have also updated the
PamentRequiredexample to be more realistic.