We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://pan.dev/prisma-cloud/api/cspm/get-compliance-posture-for-standard-v-2/
Requests to this endpoint /v2/compliance/posture without "time" parameters, as described in the documentation will fail (400 bad request):
If you add time parameters as in v1, you have an 200 ok request:
Support team through Customer Case confirmed that time parameters are required for the GET method.
Add the correct requirements of "time fields" in the documentation page of /v2/posture/
timeType string REQUIRED Possible values: [relative] Time type
timeAmount string REQUIRED Number of time units
timeUnit string REQUIRED Possible values: [minute, hour, day, week, month, year] timeUnit
Check if these "time fields" are required in other GET /v2/posture/*
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Documentation link
https://pan.dev/prisma-cloud/api/cspm/get-compliance-posture-for-standard-v-2/
Describe the problem
Requests to this endpoint /v2/compliance/posture without "time" parameters, as described in the documentation will fail (400 bad request):
If you add time parameters as in v1, you have an 200 ok request:
Support team through Customer Case confirmed that time parameters are required for the GET method.
Suggested fix
Add the correct requirements of "time fields" in the documentation page of /v2/posture/
timeType string REQUIRED
Possible values: [relative]
Time type
timeAmount string REQUIRED
Number of time units
timeUnit string REQUIRED
Possible values: [minute, hour, day, week, month, year]
timeUnit
Check if these "time fields" are required in other GET /v2/posture/*
The text was updated successfully, but these errors were encountered: