Drift between PDFServices Extract schema and server response

Question

I have tried to report this issue several times and been completely ignored both in the github issues and via email to your published author address.

https://github.com/adobe/pdfservices-python-sdk-samples/issues/30

https://github.com/adobe/pdftools-sdk-docs/issues/65

The documentation for this service is published in several places. All published schemas are out-of-date and have inconsistencies with the actual server responses.

Is there a single source of truth for the PDF Services Extract API schema anywhere that users can rely on?

Will this service continue to make unnotified and backwards-incompatible changes to its data structures?

Raymond Camden · Accepted Answer

Hi, sorry, you haven't been ignored, but those repos aren't generally used for reporting issues, the forums are. (I'm attempting to get issues turned off there. It looks like the schema example in the sample is out of date. I agree it should be updated.)

I'm filing a bug report internally to:

A) Check the schema we've published on the docs - I agree that is_signed seemed to have replaced is_digitally_signed.

B) Update all sample downloads to include the latest versions.

Also, if this change was made and not documented, I'll ruffle some feathers.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.