It’s hard to say without diving into their docs, and I’m afraid I don’t have time for that right now.
You basically need to define a model for the payload and define it as a body parameter. I’d suggest using our online editor for that, take a look at the examples, and it should be fairly simple. If you have specific questions, report back and we’ll try to answer. From: 'Jnr' via Swagger <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, 22 February 2017 at 1:52 To: Swagger <[email protected]> Subject: Swagger Specification for PayPal Payment Using a basic JSON Swagger format, I would like to create a PayPal payment. I need to include the following types: intent, sale, and transaction (as stipulated in PayPal API docs) in a payment request - But I need help doing so. Could anybody assist me on how to structure a basic swagger spec file for a PayPal payment? NOTE: OAuth is already configured in our platform that uses the access tokens and headers. Below is my swagger file: { "swagger": "2.0", "info": { "description": "this is a payment request to through PayPal", "title": "Swagger PayPal Payment", "version": "1.0.0" }, "host": "api.sandbox.paypal.com", "basePath": "/v1/payments", "schemes": [ "https" ], "paths": { "/payment": { "post": { "summary": "Creates a payment" "description": "Creates a payment request to Paypal", "responses": { "200": { "description": "OK" } } } } } } -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
