So the Adobe documentation or the lack of it has me perplexed. I am trying to understand the sequence of calls needing to be made to initiate an interactive proof in Workfront. (Use case: Web URLs will be provided as part of an input for Review & Approval of a web Page)
Based on article - https://experienceleague.adobe.com/docs/workfront/using/adobe-workfront-api/tips-troubleshooting-apis/api-create-proof-options-json.html?lang=en
it appears that i need to first use JWT exchanged OAuth token (This works) to call a createProof action on the DOCU API followed by using a ProofHQ token i am anticipating the above call to return and to be used further with ProofHQ SOAP/REST APIs for updating the proof.
My questions are:
There is no swagger definition and/or the API explorer doesnt make it easy to understand how Workfront expects the /DOCU call to be Posted for a "CreateProof" action, when interactive & otherwise. I understand there are many APIs for managing/setting stage(s), reading/completing stages etc but i am at this point just trying to initiate a proof and set the project owner as the actor for the First stage.
Any pointers or samples would be grately helpful.
PS: On V16.0 of the Workfront REST API.
There is no clear documentation for how to initiate proofs in Workfront nor a Swagger/OpenAPI Spec.
You only have to use the Workfront API to create a proof, you will need to create an api key for a user or users.
Everything is available Adobe Workfront Objects And Endpoints
The only thing that it doesn't explain well is the advanced proofing options, so this is what you are going to need.
This is the json key (advancedProofingOptions) so this is what you will need for the payload, just remember that this is a json payload.
Heres the integer values associated.
If you need anymore help let me know.