Check if context generation is needed
Check whether the Project needs translation context generated. This deprecated endpoint is retained for backward compatibility and is no longer called by current clients.
Headers
API contract version. Defaults to the oldest supported version.
API contract version. Defaults to the oldest supported version.
Target project ID. Required when authenticating with an organization API key; ignored with project-scoped API keys (the project is resolved from the key).
Target project ID. Required when authenticating with an organization API key; ignored with project-scoped API keys (the project is resolved from the key).
Response
Whether project context should be generated
Changes
Changed in 1 of the 3 revisions of this API.11
- ○
api operation id
shouldGenerateContextremoved and replaced withshouldGenerateProjectContextapi-operation-id-removed
- ○
the endpoint scheme security
BearerAuthwas added to the APIapi-security-added
- ○
added the media type
text/htmlfor the response with the status401response-media-type-added
- ○
added the media type
text/htmlfor the response with the status403response-media-type-added
- ○
added the non-success response with the status
400response-non-success-status-added
- ○
added the non-success response with the status
404response-non-success-status-added
- ○
added the non-success response with the status
429response-non-success-status-added
- ○
added the non-success response with the status
500response-non-success-status-added
- ○
the response property
errorbecame required for the status401response-property-became-required
- ○
the response property
errorbecame required for the status403response-property-became-required
- ○
the response property
shouldSetupProjectbecame required for the status200response-property-became-required
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○