swagger.yaml bugs

[tomale69]

Hello Support, I am developing an interface to Lens Scholarly (we have recently purchased a licence for this) and I have used the swagger.yaml file to automate the creation of java classes needed to wrap your api. However, I noticed there are some bugs in the file (see attached file). Would it be possible to fix these those errors? Thank you very much and have a nice day. Best Regards. Alessandro Tomasini Saes Getters S.p.A. Swagger.yaml.Errors.txt

[rosharma9]

Hi Alessandro, Here is a fixed schema, we will publish it soon. Also, I recommend to find the response schema from following endpoint as we are constantly evolving and this endpoint is always consistent with what you receive in response. GET https://api.lens.org/schema/scholarly?token=YOUR_TOKEN Let us know if you have more issues. Cheers, Roshan

[tomale69]

Hi Roshan, First of all, thank you for your quick reply. The new swagger.yaml seems to be correct except for the "post" reply patterns that are still missing. See below for details. I tried using https://api-dev.api.lens.org instead of https://api.lens.org (I used the same pkey I created earlier) but it returns an unauthorized access error. Thank you. Regards Alessandro

Line 47 Actually '200': description: Valid response from the server Should be '200': description: Valid response from the server schema: $ref: '#/definitions/ScholarApiResponse'

Line 134 Actually '200': description: Valid response from the server Should be '200': description: Valid response from the server schema: $ref: '#/definitions/PatentApiResponse'

Line 226 Actually '200': description: Valid response from the server Should be '200': description: Valid response from the server schema: $ref: '#/definitions/ScholarApiResponse'

From: rosharma9 @.> Sent: martedì 3 maggio 2022 02:03 To: cambialens/lens-api-doc @.> Cc: Alessandro Tomasini @.>; Author @.> Subject: Re: [cambialens/lens-api-doc] swagger.yaml bugs (Issue #53)

Hi Alessandro, Here is a fixed schemahttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcambialens%2Flens-api-doc%2Ffiles%2F8606642%2Fswagger.yaml.txt&data=05%7C01%7Calessandro_tomasini%40saes-group.com%7Cacb52baf0aae42486a6c08da2c9849ce%7Cf7fa85da33c94923bc841c15adef14f4%7C1%7C0%7C637871329847806558%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2qr1YXr87J0kXJbeAeuWAph84dKuTokFLqTwRYwGebo%3D&reserved=0, we will publish it soon. Also, I recommend to find the response schema from following endpoint as we are constantly evolving and this endpoint is always consistent with what you receive in response. GET https://api-dev.api.lens.org/schema/scholarly?token=YOUR_TOKEN Let us know if you have more issues. Cheers, Roshan

- Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcambialens%2Flens-api-doc%2Fissues%2F53%23issuecomment-1115480370&data=05%7C01%7Calessandro_tomasini%40saes-group.com%7Cacb52baf0aae42486a6c08da2c9849ce%7Cf7fa85da33c94923bc841c15adef14f4%7C1%7C0%7C637871329847806558%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rFSx4CVfMtQX7sC0cb0TtyCI%2BdrfPV57cqSGc%2BrTC8E%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAY7LMK2ANT7XYHGIBWPVBNDVIBULHANCNFSM5U375XYA&data=05%7C01%7Calessandro_tomasini%40saes-group.com%7Cacb52baf0aae42486a6c08da2c9849ce%7Cf7fa85da33c94923bc841c15adef14f4%7C1%7C0%7C637871329847806558%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=yUKSR8nC4yuyogr3x%2FiOKcaRC2go24vnoOgb7HJwNC8%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

This message and any attachments are confidential and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any unauthorized use, reproduction, disclosure, modification and/or dissemination is strictly prohibited. If you are not the intended recipient, please notify the sender by replying immediately to this message. Do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.If this mail is in response to mail containing ideas or proposals, it cannot be considered acceptance or commitment thereto; unsolicited mail - failing written confidentiality agreements in place - will not be processed on confidential basis until such time as confidentiality agreements may be executed by duly authorized representatives.

[rosharma9]

Thank you Alessandro, I have fixed the url for the schema. GET https://api.lens.org/schema/scholarly?token=YOUR_TOKEN I will attach the schema in the responses like you've suggested. Thanks, Roshan

[poldham]

I think this is related to the above. I think there may be a bug with the swagger page authentication. When I enter my key in authorise (I know it is valid because I can run queries to the API without an issue) the POST sections for scholar and patents remain locked. I have tried several times with no success. As our queries are constructed using POST this is proving to be a bit frustrating. If this could be investigated that would be much appreciated.

[rosharma9]

If you click on the lock icon at the right of the POST method (after entering the access key and get authorised), you will see the status as authorised as in the screenshot attached. You can then click on Try it out and execute the query successfully.

[poldham]

Thanks, I have no idea what was going on as that is precisely what I was doing yesterday (hence the issue). However, it is indeed working. Many thanks for the rapid support.

On 10 Jul 2022, at 10:40, rosharma9 @.***> wrote:

If you click on the lock icon at the right of the POST method (after entering the access key and get authorised), you will see the status as authorised as in the screenshot attached. You can then click on Try it out and execute the query successfully. https://user-images.githubusercontent.com/47509149/178139326-1277a703-99fb-4bbe-86ff-9b72e95c7a0d.png — Reply to this email directly, view it on GitHub https://github.com/cambialens/lens-api-doc/issues/53#issuecomment-1179693449, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTUB4BOVROBPLPR64WPZPDVTKLAPANCNFSM5U375XYA. You are receiving this because you commented.