I will review and fix your openapi or swagger spec


About this gig
Is your OpenAPI file failing validation, confusing your API consumers or breaking code generation? I review it line by line and fix it.
WHAT I CHECK
Validity against Swagger 2.0 and OpenAPI 3.0
Schemas, required fields, types, enums, examples
Security declarations (OAuth 2.0, JWT bearer, API keys)
Error model, status codes, pagination
Naming, operationId, tags, descriptions
WHAT YOU GET
Findings report (PDF): severity, exact location, how to fix
Corrected spec that passes lint with 0 errors (Standard, Premium)
Postman collection with tests, run on a mock of your spec (Premium)
HOW I COUNT
1 operation = 1 method on 1 path. GET /users and POST /users = 2 operations.
NOT INCLUDED
Backend coding, tests on production systems, penetration testing.
Please message me before ordering if your file has more than 25 operations.
Get to know Emiliano C
API Integration Specialist for OpenAPI and Postman
- FromItaly
- Member sinceJan 2021
- Avg. response time1 hour
Languages
English
FAQ
Which formats do you accept?
YAML or JSON files in Swagger 2.0 or OpenAPI 3.0.x. For OpenAPI 3.1, please message me before ordering.
Do you need access to my API or servers?
No. I only need the specification file. Please never send production credentials.
Will you test my real API?
Premium tests run on a mock generated from your spec. Tests on your sandbox are possible as a custom offer, with a test URL and a test token you provide.
How do you count operations?
One HTTP method on one path is one operation. GET /users and POST /users are two.
My file has more than 25 operations. What should I do?
Add the "10 extra operations" option, or message me for a custom offer.
Do you write backend code?
No. I work on the API contract: the specification, its documentation and its tests.

