Skip to content

429 responses should carry more information #624

Description

@Siderite

Very hard to determine how you overloaded the server when you get a 429.

My suggestion is that the content or headers of the response should carry the expected rate of consumption for that API. At least add the limits to the documentation for each API.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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