Save
Save promotes the program behind an already-rendered reporting surface into a report. The caller identifies the surface; the server resolves which program produced it. There is no create-from-prompt: the prompt has already been answered by the time a report is worth keeping.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
Body
The ReportingServiceSaveRequest message.
The conversation and surface are both required to address a rendered surface; neither identifies one alone.
The displayName field.
The question this surface answered. The surface records its program but not the words behind it, so the caller supplies them; without it the report has nothing to compare against when deciding its program has gone stale.
The surfaceId field.
Response
Successful response
The ReportingServiceSaveResponse message.
Report is a saved report: the question, the program that answers it, and the parameters a re-run may vary.