Skip to content

Better API docs #129

@jimaek

Description

@jimaek

I'm not very happy with our API docs, most other projects have much nicer ones. Here are some relatively simple ideas to improve them

  1. Switch to something like https://github.com/scalar/scalar
  2. Link to the demo page, the Slack chat was not the first time it helped, I often email it to devs working on an integration and they all find it very useful. Mention it in an obvious way
  3. Update limits table to include missing data
  4. Consider improving the content itself to make things more clear

Issues people had that are worth addressing e.g. making more obvious:

  • How long it is expected for a measurement to be available
  • Are they public for everyone
  • Not clear how to separate probe failures from target failures
  • Unclear why some probes return DNS resolvers and others not
  • Too many questions about the 500 tests per hour limit. Some thing it's a hard limit of testing in general, like an anti-abuse system. Others think their donated credits are used first and the free ones after that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions