10 replies · 484 views · thread synced · 4 days ago
· View on torn.com
About this thread
Posts archived:11 / 11 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
Archived posts
11
Discussion span
→
People posting
6
Likes on archived posts
12
Posts by staff, officers and moderators
1
Authority score
56 / 100
Historical score
20 / 100
Story score
33 / 100
Engagement score
60 / 100
Most-liked replies
DeKleineKobini[2114440]Committee
· 1 likes · Let's be honest, the official 'docs' only provide error codes and the api key limit. The try it is nice to use, but it doesn't provide actual documentation.
I have noticed that very few people know the term OpenAPI. So here is the description of what OpenAPI is.
The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.
In the next days I will maintain examples of the API's responses and record the structure of the responses. If someone wants to join in, I can move the project to github.
Let's be honest, the official 'docs' only provide error codes and the api key limit. The try it is nice to use, but it doesn't provide actual documentation.
It's still a work in progress. But I have already published it now, so that you can get a first impression and to get helpers on board. My previous attempts to use the description language as a possible documentation base have failed due to subsequent tool discussions in the Discord API channel.
The documentation is not complete. In addition, there are no examples or structure descriptions for the responses. As I said, I will maintain this in the next few days.
For quick deployment, having no documentation on how anything works, with a trial and error interpretation from every community developer makes things easy. But that means that every developer goes through asking the same questions.
IE how to and from works, what kind of Strings to expect as the attack status, what each icon on the profile means, why can't we use to and from with events logs, what type of data is to be expected in a certain portion of the JSON object...