πŸ‡¬πŸ‡§
BOZON API
www.fintech.gov.pl
ENG
ENG
  • 🏒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
    • 🧾PROCESS WORKFLOW OF THE LOP API SERVICE
  • πŸ”§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. TECHNICAL SPECIFICATION

TECHNICAL SETUP

bozon-api.fintech.gov.pl

The API is available at the Domain Name System address:

bozon-api.fintech.gov.pl

An entity that wants to obtain data from the List of Public Warnings and the Database of Warnings from Foreign Supervisory Authorities will have to establish a connection with the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) cryptographic protocol. The entity is required to communicate through a valid communication session. A valid response from the server providing the JSON object, i.e. a response with the status β€˜200’ , can be obtained if all the above-mentioned requirements are fulfilled.

Access under the LOP API service is provided through a separate dedicated communication session. A single communication session may be used multiple times when sending requests to the interface service, until the expiration of the session’s validity period , after which the UKNF will automatically cancel the session.

PreviousPROCESS WORKFLOW OF THE LOP API SERVICENextNAMING CONVENTION

Last updated 1 year ago

πŸ”§
πŸ“–
Page cover image