πŸ‡¬πŸ‡§
EURO-BOZON
www.fintech.gov.pl
ENG
ENG
  • 🏒EURO-BOZON API
  • πŸ“–MAIN ASSUMPTIONS
    • βœ…DATA ACCESSIBILITY
    • βœ…TYPES OF SERVICES PROVIDED THROUGH THE API
    • βœ…GENERAL COMMUNICATION DIAGRAM
  • βš™οΈDATA STRUCTURE IN THE API
    • 🧾DATA STRUCTURE
    • 🧾DATA TYPES
    • 🧾DEFINITIONS AND DESCRIPTION OF JSON FILE PROPERTIES
  • πŸ”§TECHNICAL SPECIFICATION
    • πŸ“–TECHNICAL SETUP
    • πŸ“–NAMING CONVENTION
    • πŸ“–OPERATIONS
    • πŸ“–RESPONSE STATUSES
    • πŸ“–HTTP HEADINGS
    • πŸ“–FORMAT OF THE MESSAGE RECEIVED
  • πŸ”SECURITY
    • πŸ”’HTTPS PROTOCOL
    • πŸ”’CROSS-ORIGIN RESOURCE SHARING
    • πŸ”’PROTECTION AGAINST MISUSE
Powered by GitBook
On this page
  1. SECURITY

PROTECTION AGAINST MISUSE

PreviousCROSS-ORIGIN RESOURCE SHARING

Last updated 1 year ago

When implementing the API, it is necessary to include safeguards against excessive number of requests from users, in particular DDoS/DoS attacks, by using mechanisms limiting the number of requests processed per unit of time. The values of those limits should be adapted to specific operating requirements and be subject to parametrisation. The number of requests for access to resources should be monitored using the mechanisms and meters available on the server’s part. If a limit is exceeded, the server should return HTTP communication No 429 (Too Many Requests).

πŸ”
πŸ”’
Page cover image